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

Tom von Schwerdtner tomvons at gmail.com
Mon Feb 14 15:38:32 EST 2005


On Mon, 14 Feb 2005 20:41:33 +0100, Roger Ineichen <dev at projekt01.ch> wrote:
> Hi Jean Marc
> 
> > -----Original Message-----
> > From: zope3-dev-bounces+dev=projekt01.ch at zope.org
> >
> > Tonico Strasser wrote:
> >
> > > Peter Simmons wrote:
> > >
> > >> Does it somehow add some functionality because the css
> > designer can
> > >> decide whether there are 2 classes for an element or
> > something like
> > >> that?
> > >
> > >
> > Hi,
> >
> > > Don't understand your question, but it should be easily possible to
> > > put two names in the class attribute.
> > >
> >
> > indeed you can write:
> >
> > <div class="blueArea redFont orangeBox fancyFormStyle">
> > ...
> > </div>
> >
> > because usually you want to define font shapes, area colors, etc for
> > your entire site and re-use them inside many widgets, portlets. etc...
> >
> > This makes it possible to mix together CSS classes and avoid useless
> > duplications in case only the color of a widget changes and not the
> > fonts that it uses, CPSSkins uses that method of combining many CSS
> > class names together, (font shapes, colors, area shapes, colors, form
> > styles, etc...) to create composite styles for each object.
> > It is a bit
> > like impressionism in a sense...
> 
> I think that good ideas.
> 
> But don't understand me wrong, we don't need this concepts in the
> core widgets and forms. We just have to make sure that
> we can implement this concepts later without changes.
> 
> Actually we have to define simply styles for the core implementation.
> All other concepts are welcome but has to be optional and build on
> the exsisting part.
> 
> > Which makes me wonder why one would want to set widget names in CSS
> > class names...
> 
> You mean the proposal.
> 
> http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/CascadingSt
> yleSheetStyleGuide
> 
> I proposed useing CSS class names in widgets. Not widget names in
> class names.
> 
> This makes it possible to define default styles for input fields.
> like:
> 
> <input type="text" class="text" ... />
> 
> Or do you know another method to define CSS classes for:
> 
> <input type="text" ... /> or <input type="checkbox" ... />

I believe there is no ie6 or ie5/mac support, but:

input[type=text] {
    background: blue;
}

Using the type as the class seems like a good idea, at least the only
reliable solution I can think of.

Is discussion enabled in the wiki or would I have to edit the page? 
Is there a way to get access for this or should I just comment on the
list?

-Tom

-- 
Tom von Schwerdtner
Etria, LLP :: http://etria.com/
Baltimore, MD


More information about the Zope3-dev mailing list