Great!, I am going to do a little research and then put together some options / samples. Two other items I am going to look into (which are also suggested on the ez.css page) are html5 semantics and WAI ARIA landmark roles. Roles would require a code tweak or flag as some (most?) validation sites do not support it yet, html5 I need to look into a bit more. html 5 is semantic and I am wondering if this could conflict with our current naming conventions, validation and so forth.
Anyway it is a great opportunity to check all this stuff out and we could always we could offer some "unsupported" / "off label" options that give people more choice while maintaining our compatibility commitments first adopters in the main. For our organization WAI-ARIA landmarks is really important. Cheers, C. On 28 mar, 13:39, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > A few points I would make (as I write this, I am aware this probably > should be moved to the development list): > > - ez.css is no more than a layout / framing convention; > - staying compatible is easy (and it provides simple layout > control); > - it uses a useful convention of css class nameing, namely: <pkg>- > <class>, e.g.: "ez-wr" - > - we should stick with that, ie. something like "w2p" for all > web2py named css classes and id selectors; > - note: the major difference between > - class selectors (.something) and > - id selectors (#something) is id selectors can link to a > part of a page, and javascript uses id selectors; > > I'm not sure specifically what Massimo meant by "ez.css and jquery.ui > naming conventions"; we should get specific about this. > > ez has the concept of > - wrappers, (ez-wr, ez-mr) > - style containers (i.e. layout containers) > - content containers (i.e. ez-box) > - sizing elements; > > and more... > > jquery has at least these conventions: > -http://jqueryui.com/docs/Theming/API > -http://wiki.jqueryui.com/Position > > Note that ThemeRoller is a way to apply to PARTS of a user layout, > e.g.: > > - font settings; > - corner radius; > - header; > - toolbar; > - content; > - clicables; > - highlight; > - errors; > - modal; > - drop shadoes; > > By combining ez (positioning) and jquery-ui (and staying consistent w/ > themeroller), we should be able to build-up a web2py-unique packaging, > with potentially useful extensions (e.g. for form layout and theming). > > This seems, to me, to be a very promising direction. > > - Yarko > Noteab > > On Mar 27, 7:44 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > I like the idea. It would be ideal if you could do it using ez.css and > > jquery.ui naming conventions. > > > Massimo > > > On 27 Mar, 15:23, Christopher Steel <chris.st...@gmail.com> wrote: > > > > The Zengarden css code is not "open source" but we can easily create > > > our own. I am just finishing up a css based theme for a client that > > > uses div's and flow with a two columns (basically the same appearance > > > as the current web2py default layout). I would be more than happy to > > > create on using the current web2py names, images and so forth and can > > > license it as we like. > > > > We could include it as a documented option and give it a name like > > > base-2c-flow.css or base-tableless.css > > > Let me know soon cause I am moving on to non css stuff in the next few > > > days. > > > > Cheers, > > > > Christopher Steel. > > > > On Mar 25, 5:33 am, Benigno <bca...@albendas.com> wrote: > > > > > @mdmcginn: I do think that having a proven flexible div setup that > > > > allows for so many different options, is precisely what you need on > > > > the original layout. What Zengarden does, is prove the flexibility of > > > > CSS but that flexibility is nothing if your div structure is not > > > > correctly thought out and matured. > > > > > On the minus side, however, and this is my personal opinion, I think > > > > that most Zengarden designs, are mostly oriented towards blogging, > > > > news/magazine, or marketing presentations, and not so much about > > > > enterprise applications. (This might be that I have missed the correct > > > > layouts). However, I have the same opinion about the other layout > > > > plugin. > > > > > Cheers, > > > > Benigno. > > > > On Mar 24, 10:23 am, mdmcginn <michael.d.mcgin...@gmail.com> wrote:> > > > > CSS is great, much better than table-based web design, and > > > > > csszengarden deserves a lot of credit for demonstrating that. But it > > > > > is just a proof of concept. As you noted, their basic HTML is full of > > > > > empty divs into which designers can insert fancy images, so it's not a > > > > > good base for templates. > > > > > > On Mar 22, 9:14 am, Wes James <compte...@gmail.com> wrote: > > > > > > > On Sat, Mar 20, 2010 at 7:27 PM, mdipierro > > > > > > <mdipie...@cs.depaul.edu> wrote: > > > > > > > Just for fun: > > > > > > > > http://web2py.com/zengarden > > > > > > > > then click on the [zengarden] link under the menu, under the > > > > > > > "index" > > > > > > > link. You can change the skin per user, per session. > > > > > > > This is a bare bone welcome app with the layout > > > > > > > It says to click on link at top right - on firefox/mac os x.6.2 it > > > > > > shows up on top-left. > > > > > > > -wes -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
