A few random wishes from my side concerning css management:
- definition of css classes for more or less
all oacs elements
(including lists, actions, forms, calendar etc.);
this means analysis of css usage, design of class
names, ids etc., providing skins for the classes/ids. - reduction the number of different style files while
keeping modularization: some pages use 6 or more
different css files, each file is a separate request,
in most cases returning 304. For a user, this site
appears more sluggish than with e.g. on large style
file. There could be a tcl function "make" that checks dates
of style-files and composes a common style file out of
these when parts are modified. These requests could be
reduced to a few requests (maybe one) - selva does currently not show the title of the
resource, but instead something like Main Site.
For many packages the title is important (see e.g.
xowiki pages), i have made a local change to allow this) - As noted earlier, selva support for plain oacs.
In the best of all possible worlds, skin management
support for subsites similar to dotlrn.
