[Zope3-dev] Re: CSS-Style-Guide / looking for help

[Roger Ineichen]

Hi Pee

> -----Original Message-----
> From: zope3-dev-bounces+dev=projekt01.ch at zope.org 
> [mailto:zope3-dev-bounces+dev=projekt01.ch at zope.org] On 
> Behalf Of Peter Simmons
> Sent: Friday, February 11, 2005 10:07 PM
> To: Tonico Strasser
> Cc: zope3-users at zope.org; zope3-dev at zope.org
> Subject: Re: [Zope3-dev] Re: CSS-Style-Guide / looking for help
> 
> 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

This is out of scope right now. 
I like such ideas, but we are on a lower level right now.

Regards 
Roger Ineichen

> 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
> >
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> Unsub: 
> http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch
> 
>