Re: [Phpwebsite-developers] Panel / Menu

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

On 7 Aug 2004, at 16:40, Mike Noyes wrote:

> On Fri, 2004-08-06 at 13:49, Shaun Murray wrote:
>> The point I was making was that there is currently no standard way of
>> building a CSS based menu so defining one, and specifying it as a
>> standard to be used and be available, lessens the likelihood of
>> developers creating their own, perhaps incompatible or badly styled,
>> method. In the same way we can all roll our own list/item managers but
>> they'd all look different to everyone else's. Standards are good. They
>> set a base line, even if it's only used a point to deviate from.
>
> Shaun,
> I think the main difference we have is in our point of view. You want
> standard classes available for module developers.

And for theme developers. I want theme developers to know that if they 
change the "menu" class in style.css that it affects the style of each 
and every one of the menus used. Just like they know that changing 
bg_light changes one of the alternate lines in tables.

I want module developers  to know that if they put in their template

<div id ="menu_id" class="navmenu">
{menu}
</div>

...or whatever we decide...

...they'll get a standard menu that looks just like the other menus as 
we specify a menu class in the provided style.css as a thing that theme 
developers must provide. I don't module developers  defining those 
classes in their own module code or in their own style sheets. The 
former is horrible and the second is a pain in the ass for theme 
developers who would now have to cope with extra style sheets.


> I'm looking at it from
> a theme developer/end user perspective. I want descendant selector divs
> defined so they can be easily modified for site specific use.

Those are useful for additional theme work but completely irrelevant to 
this discussion since there currently aren't any basics to descend 
from. ;-)

I really don't want to see

p.pagemaster
p.announce
p.article
p.linkman
ul.pagemaster

etc

clogging up a theme as the default situation. I'd really not like to 
see p redefined at all, or html, or body, or any of the type selectors. 
Not in a basic simple style sheet at least. If we're getting fancy then 
sure, redefine your H1's to HelveticaNeue-CondensedBlack with 75% 
text-shadows, which is what I usually do in my own themes. The base set 
you provided a link to yesterday implementing most of HTML4 is a good 
start if you're looking to define every type selector, but I'm not, and 
you shouldn't have to - that's up to the browser developers to define.

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