Re: [Phpwebsite-developers] Panel / Menu

[Mike N. <mh...@us...>]

On Sat, 2004-08-07 at 11:44, Shaun Murray wrote:
> On 7 Aug 2004, at 16:40, Mike Noyes wrote:
> > 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.

Shaun,
I just put up another prof-of-concept. It shows descendant selectors,
cascade, and collision resolution in action. A cascade list is liked, so
you can understand the structure I'm proposing.

        http://phpwebsite-comm.sourceforge.net/temp/

Any comments and/or suggestions are welcome.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs