Erik Moeller wrote:
Bug report first: The new "Subcategories"
links do not point to the
Category: namespace but into the main namespace.
Whoopsie ;-)
Fixed.
>3)
Similarly, it would be neat if the list of categories would be
>structured according to parent child relationships, i.e.
What about double entries?
"Biochemistry" is both in category "Biology"
and "Chemistry". Should that appear under both?
Yes, I think it should appear under both. A little redundancy here won't
hurt.
Maybe later today...
>4) I think
the categories should be put under the page subtitle, or at the
>bottom of the page, but definitely not next to "printable version".
Trying your first suggestion. Looks OK.
I agree, looks fine to me.
One thing I can leave unchanged :-)
>5) After I
initially proposed the scheme, Brion suggested that it would be
>useful to have some way to specify how an article should be sorted in the
>category list, e.g.
>
>[[Category:Author|King, Stephen]]
*Way* too complicated without a separate database
table
I presume you're using the LINKS table. Why not add a LINK_ID to the table
and have a separate LINK_AS table that includes the sorting criteria and
can be looked up for categories? Updated on page save?
Yes, that should work. I'll have a look at that part of the code.
As for separation, let's keep the idea of a meta
namespace open -- we can
always move this stuff if need be. I envision a scheme where by default, a
user sees two edit windows for each page, the big article editor and a
small meta editor, but he can decide to disable the meta stuff if he
doesn't care about it at all.
Maybe that could be done "on-the-fly", when showing the edit page? Like
this:
1. Load the article to edit from the database.
2. Extract all meta information.
3. Show the article in a big box, and the meta stuff in the small one.
4. Upon saving, attach the meta stuff at the end of the article.
Advantages:
1. No need to change the database at all.
2. No need to change *any* code except the edit page code.
3. Option to display "classic" (like now), "split" and "article
only".
4. Visual separation of article and meta data for the user.
Disadvantages:
1. No internal separation of article and meta data.
(Which doesn't matter for the categories, as we do them via the links
table anyway.)
Magnus