[Zope3-Users] Re: [Zope3-dev] Re: CSS-Style-Guide / looking for help
Peter Simmons
pete at bcmpweb.com
Fri Feb 11 16:06:36 EST 2005
Does it somehow add some functionality because the css designer can
decide whether there are 2 classes for an element or something like that?
Otherwise it just sounds complicated when it probably doesn't need to
be, I mean what's the difference between saying an element name is
primary_section the way you have or simply adding a straight html class
element and having its value being primary element.
Cheers,
Pee
Tonico Strasser wrote:
> Roger Ineichen wrote:
>
>> The target whold be to use in all editforms, addforms and
>> other borwser pages/views allways the same CSS styles
>> for header, titles etc.
>
>
> I have experimented with dynamically generated CSS names in Z2. I
> wanted to allow an CSS author to define whatever class and id names he
> wants.
>
> The template author wouldn't need to care about class and id names.
> Consider the following example:
>
> <div tal:attributes="class elements/primary_section/class_name;"
> metal:define-macro="primary_section">
> Primary Section
> </div>
>
> * The code could be easily reused, and:
> * no discussions about the ultimate class and id names.
>
> In case of the ZMI that would mean, that somebody should start to
> define abstract elements of the UI.
>
> Imaginary example:
>
> - page
> - header
> - body
> - pre_section
> - primary_section
> - views
> - primary_content
> - header
> - body
> - secondary_section
> - menu_items
> - post_section
>
> Sorry for not beeing Zope 3 specific.
>
> Tonico
>
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> Unsub: http://mail.zope.org/mailman/options/zope3-dev/pete%40bcmpweb.com
>
More information about the Zope3-users
mailing list