Re: Defining and implementing design standards in phpWebSite

On 4 Jan 2005, at 03:09, Ken Nordquist wrote:
> How many times has a module's "theme" clashed with that of the main
> theme?  Where colors were hard-coded in the module instead of 
> defaulting
> to the theme?

That's another area that peeves me. Error messages are often hardcoded 
colours in some modules. IIRC there's a function call for displaying 
errors in the core already but it's rarely used. And IIRC there's a 
PEAR error message system too.

> I would also like to add theme "columnization" to the list on Michael's
> page.  How many default columns "should" there be?  Can phpWebSite's
> Layout module seamlessly handle three / two / one column themes?  What
> methodology can be used for those columns?  (left - middle/center -
> right) or (left - main - right) or some other variation?

That's another one. I'd hope that the new layout engine just completely 
drops the column thing and allows completely arbitrary areas on the 
page in which blocks can be placed, with blocks that have no 'home' 
defaulting to the bottom of the page perhaps rather than disappearing 
into oblivion if your theme.tpl doesn't have that area defined. Instead 
of the left/right arrows in layout for moving the block between 
columns, you just have a pulldown list of the block names in which you 
want to move it.

> Again, count me in on CSS standardization and I am willing to do any
> grunt work necessary.

Ditto. Alas, I think this should be addressed mostly at the php/design 
level, not perhaps the css/.tpl level. But, usability design is 
something that can be done without any coding skills.

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



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt