Re: [Phpwebsite-developers] Panel / Menu

[Shaun M. <sh...@ae...>]

On 6 Aug 2004, at 18:14, Matthew McNaney wrote:

>> The only way to do it, although I'm open to suggestions, is to specify
>> base classes for each element in style.css or perhaps even in a core
>> stylesheet as these elements don't often need tweaking across styles
>> provided you keep the colour styling out. Use descendent selectors to
>> override these but there still needs to be a base set usable across
>> modules.
>
> Actually I have no problem with that. What I was trying to avoid was 
> the
> insertion of "bg_light" in the code. Style sheets per module allowed
> developers to stay away from that.

I can see that.

 From a theme designers perspective though, having one module developer 
defining their table rows as alternating red/white and another as 
beige/pink never mind any other padding or style variances, in multiple 
style sheets is a pain. Especially if the style sheets are embedded in 
the /mod/ hierarchy instead of the theme hierarchy. It's a chore enough 
with making sure template changes in the module releases are reflected 
in updated themes.


>
> If someone wants to create a persistent style sheet as the foundation 
> of
> 0.9.4. go for it. I'll abide by it. I figured I would get into this 
> once
> 0.9.4 was completely functional but we can start now if you'd like.
>

OK, I'll have a bash later at defining a style sheet and set of UI 
guidelines for where they should be used. Hopefully I can come up with 
some standard elements of the UI so that module developers don't have 
to reinvent the wheel.

> I suggest we get a basic style sheet up, toss it around the developer
> list, and agree on the style names and definitions. Once approved by
> all, I (and later we) can code around it. As I have told others, I 
> would
> like 0.9.4 to ship with a strong foundation theme with really nice 
> style
> sheets (see Zen Garden for examples).
>

Yep, good example.

Shaun
aegis design - http://www.aegisdesign.co.uk