On Wed, Mar 5, 2008 at 11:56 AM, Raimond Spekking
<raimond.spekking(a)gmail.com> wrote:
Why not put
the float style in the class definition?
You mean by adding this class to main.css?
Well, no, shared.css.
The intention was to give this extra flexibility. You
can use multiple
columns now and sort in any manner the community finds it useful.
But I will think about/work on your suggestion to use messagekeys
instead to avoid duplication of the special pages list.
But what happens when an extension adds a special page? What happens
when a new special page is added to the core software? It will be put
at the end until someone manually alters the list. Maybe you're
giving a little extra flexibility, but on the other hand you're
forcing more ongoing maintenance to get it to work nicely.
As a wiki administrator, for something as trivial as this, I would
certainly prefer to have a sensible ordering that I *couldn't* change
than a modifiable ordering that I *had to* change. Especially given
that with an appropriate hook or two, any changes I really wanted
could be done by extensions.