Fri 09 Nov 2007 10:36:23 PM UTC, comment #3:
i agree that we don't want to disrupt existing users.
On the other hand, IMHO we need to also make things easier,
more intuitive, conceptually natural for new users.
Is a solution to satisfy both possible?
How about a rename + a soft link so that old configs
remain valid, as in the following?
i have no idea if the debian install would copy the soft link
correctly - i haven't tried working on the debian package
yet.
> It is easy enough to click on different themes...
One reasonably experienced web user chose a theme that he
wanted as default, and then tried clicking on default and
was confused because his chosen default theme was replaced
by another theme - the one which we know has the name "default"
but is the distribution default but not necessarily the
sysadmin default nor the user's default.
So this problem was reported from actual usage.
|
Wed 03 Oct 2007 11:47:09 PM UTC, original submission:
PROBLEM: Among the present list of css style files is one which
is called "default".
However, it is possible to choose another css file as default.
In that case, default.css is not default, while a default will
exist, but with a different name to default.css.
This can be confusing to users (like it was to me the first time),
since "(defaut != default)" and "(default = !default)" are
rather problematic in first order classical logic.
FIX: Change the name of default.css to something else. i don't
mind what. Maybe 'classic'? Or 'soft_greyish' ? Just about
anything other than 'default' should be ok...
A corresponding change should be made in defaults.yaml ;)
This file is not visible to users, so its name is not so
bad. However, probably its name should be changed too,
e.g. to allsites.yaml which would make things clearer
about the difference between the config-for-all-sites and
the config-for-one-site config files. This would require
changes in deployment.rb, test/mock.rb and install.txt...
cheers
boud
|