Hi
Am 28.03.2008 um 01:37 schrieb Andreas Hartmann:
Cleaning up the XHTML and CSS, removing tables etc. would already
help a lot since it would simplify creating GUI skins.
+1
Ripping out the layout table will make the whole gui much clearer and
more accessible too. For the gui forms, basic accessiblity features
would be good too (associating labels and form inputs etc.). Maybe we
can also provide access keys for the top menu.
One thing that could be important, is to give the content div relative
or absolute position property, to make shure, that absolute positioned
elements from the publication layout dont overlap with the lenya
toolbar.
Maybe there shouldn't be just "the" Lenya GUI, but a couple to
choose from.
I favour establishing one design that users and devs can identify
with, and that is functional and comfortable to work with.
Still we could provide the means for users to override the css.
I spent the last two nights on such an experiment. Actually the GUI
CSS isn't that bad, only the sitetree view is a bit complex.
Attached you find some screenshots. IMO very saturated colors should
be avoided, because otherwise the Lenya GUI would compete with the
website that is managed. I tried to put some colorful icons in the
toolbar, but they tend to distract too much from the page content.
Looks very nice! I like your approach, that the lenya gui does not put
itself in the center of attention and uses colours with care - but
maybe a colour scheme with low saturation would still follow that
concept.
One issue should IMO be addressed anyway: Currently, the toolbar
isn't shown on the "menu=false" usecase pages. On these pages, we
could just hide the menu and show the toolbar nevertheless. This
would be an important step towards a consistent GUI and branding.
+1
Jürgen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
