On Mar 8, 4:44 pm, Albert Abril <albert.ab...@gmail.com> wrote: > As said by villas, I think this is the principal goal: > > 1. A clear goal of moving from table to divs.
Problem. web2py welcome was based on DIVs and them we moved BACK to tables. Why? Because with DIVs having multiple columns where some have fixed width (like the menu and sidebar) and some have are expandable (the main one) is a CSS nightmare. It can be done but the CSS is not readable. All the css frameworks like Blueprintcss and 960 solve they problem by having fixed column width. I do not like fixed widths. Moreover using DIV make the page structure very fragile because DIVs rely on each other to determine the position. For example you add padding to one div and all the following divs lose alignment. This does not happen with tables since they enforce the relative alignment of component rows and columns. To me it seems the pragmatic approach of using TABLE is better for newbies. Expert users are going to use their own advances layouts anyway. Anyway, I may be completely wrong on this one and if you can propose a DIV based example that is simple and readable > 2. A web2py list of semantic names to name certain sections of the page. This is a good idea. How about the jquery.ui convention? I have looked at it only superficially. > If in 2, we take references from wordpress or some cms, it would be easier > to import templates from them. > > On Sun, Mar 7, 2010 at 11:29 AM, villas <villa...@gmail.com> wrote: > > An example layout page I looked at had: > > > <div class="wrapper"> > > <table class="layout"> > > <td colspan="3" class="header"> > > <td colspan="3" class="statusbar"> > > <td class="width10em column1"> > > <td class="expandable column2"> > > <td class="width10em column3"> > > <td colspan="10" class="footer"> > > > Clearly it leaves much to be desired, but maybe it would help if we > > agreed: > > 1. A clear goal of moving from table to divs. > > 2. A Web2py list of semantic names to name certain sections of the > > page. > > 3. Perhaps longer term, move forms towards fieldsets and definition > > lists (well, let's leave that for now!). > > > If we achieved 1. and 2. we could all build layouts to a similar > > standard. I wonder whether Wordpress has standard div names we could > > adopt? Or maybe one of the other popular CMSs or frameworks which has > > lots of template writers (Joomla, Drupal). With CSS it helps if we > > could all sing off the same 'sheet'. > > > -David > > > -- > > 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<web2py%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/web2py?hl=en. -- 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.
