[web2py] Re: where to place sizes (and other properties) ?

[annet]

Hi Stef,

The problem with most layouts is that they are build in applications
like Adobe's Dreamweaver. I do have CS5 but I prefer to build a layout
in textedit, html and css in separate files using for instance ez_css
for sizing and positioning, which reduces the number of css selectors
significantly.

I only use the style tag for views that need customization on view
level, and inline styles to take care of small adjustments on element
level. However, when your views are well designed, you hardly need the
style tag and inline style attribute to style your views.


Kind regards,

Annet.

[web2py] Re: where to place sizes (and other properties) ?

[mdipierro]

Talking about the default layout.html or one of those from http://.../layouts?
Nobody is maintaining the latter. They were generated automatically
from free templates found online.

On Nov 23, 7:48 am, Stef Mientki  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