From: Shaun M. <sh...@ae...> - 2005-01-04 10:34:26
|
That's a particularly well observed and informed article Michael. Some of the issues are being addressed in the new code the team are working on. I think we've beaten them on the head enough times in IRC about menus at least, and we've had long ranging discussions about CSS and how it should be implemented - which I don't entirely agree with. Ken noted two links to Xaraya and IMHO they've got the mix right there, enforcing some classes without making it overly complex. I just hope the 3-tier css method we've chose can largely be ignored at a module level and module developers don't try and cram fancy layout in their module css. Otherwise we're back to inconsistent look and feel across modules. I hope the team have a good look through the article, and the Xaraya ones, and think how they can be addressed. Personally, I'd like to see more support functions for module developers that let them produce menus, submenus, lists, links etc to a standard rather than having to build them up manually either in the code or in a template. That way there's a set method of doing it that can be styled globally. Ie. that we make more use of the box_style type of method and expand it to lists, menus, links, tabbed menus with appropriate css too... It just appears mad to me that I have to edit multiple templates to change the look of menus across a site, if I can at all. So, well done for putting it all together Michael. Shaun aegis design - http://www.aegisdesign.co.uk |