This looks like a CSS question, rather than web2py. Any level of cascade is acceptable, and the best place can be anywhere depending on what you want. Personally, I'd move everything into an external CSS and link from the layout.html (the way you'd usually link it).
I think web2py layouts are not considered supported web2py components, though (except the one from the default app, that is). On Tue, Nov 23, 2010 at 2:48 PM, Stef Mientki <stef.mien...@gmail.com> wrote: > hello, > > I just downloaded one of the layouts, > and I stumbled about the huge amounts of size / color definitions. > I realize that this is not a typical web2py question, > but with web2py and it's layout inheritance the problem becomes even bigger. > I wonder what's the best place to organize size (and other properties) of > objects. > > You can define size directly in pure html, where to place them in > generic.html / layout.html / > other.html ? > You can place them in a style tag in html, is that a good choice ? > You can place them in css, which can be heavily nested. What value of nesting > is acceptable ? > > Opening the page in Mozilla with firebug, > reveals that some components have 10 or more nested definitions of sizes / > colors etc. > (of which a lot are invalid) > I wonder how anyone can maintain such a complex hierarchy. > > Is there a way (other than firebug) to show this hierarchy ? > > thanks, > Stef Mientki > > > > -- Branko Vukelić bg.bra...@gmail.com stu...@brankovukelic.com Check out my blog: http://www.brankovukelic.com/ Check out my portfolio: http://www.flickr.com/photos/foxbunny/ Registered Linux user #438078 (http://counter.li.org/) I hang out on identi.ca: http://identi.ca/foxbunny Gimp Brushmakers Guild http://bit.ly/gbg-group
