Sorry, I've been AWOL for awhile. I'm still not quite back, but
thought I'd check in.
I think case insensitivity in page names is a bad idea. Mostly for the
reasons that Malcolm Ryan listed. Capitalization is the punctuation
of a wiki --- capitals in WikiWords (should) have clear semantics
attached to them, and one should ignore them by smashing the case. (I
also think page names like EquipMent are a bad idea. That's why
brackets were introduced... better yet: add a word to make the page
name a more descriptive title: EquipmentInventory.)
I agree that HowToEatASandwich should match $WikiNameRegexp.
I see two separate ideas here:
Subpages really are just syntactic sugar, and merely provide a
shorthand notation for related pages. Here's, sort of, how I see this
Within page SuperPage, a link starting with a period, [.SubPage], would
refer to SuperPage.SubPage. I'm still uncertain as to:
1. Whether there can be sub-sub-pages.
2. If there is a shorthand notation which a sub-page can use
to refer to a sister subpage.
Subwikis are true partitions of the wiki namespace (with separate
RecentChanges, etc...). Within the page 'SubWiki/PageName', normal
links, like [OtherPage], refer to 'SubWiki/OtherPage'. If you want to
link to a page that's not in your subwiki, you have to start with a
slash ([/TopLevelPage], or [/OtherSubWiki/OtherPage]).
I like Joe's IncludePage plugin, and agree that it looks to be a good
way to provide partial page locking, etc... If no one beats me to it
I'll try to get it merged into the CVS code next week sometime.
Ticket tracking / ctime in link table:
It's doable. The "right way" to do it (IMHO) is to add the ability to
attach arbitrary meta-data to links, not just ctime. To be brutally
honest, it's not high on my todo list right now though...
Could easily be kludged with a plugin.
Mostly as an aside, somewhere (UseMod?) I saw a suggestion of using a
Category: InterWiki prefix as a hack for this. Category:Example would
be converted, by the InterWiki linker, to a link to CategoryExample,
but it won't show up as a backlink...
What exactly do y'all mean by "templates"? I'm guessing you mean the
ability to choose between various content skeletons when you're editing
a new page.
If so, then, no there's currently no support for it. Here's how I
would envision adding support for them:
Hack lib/editpage.php so that when one edits an non-existant/empty
page, instead of the regular editpage form, one gets a template-choice
form. This would allow one to set the initial contents of the page to
any one of a set of skeletons. The skeletons would taken from pages
matching a particular pattern, like Template*. Eg. TemplateHomePage
would be a skeleton for a home page, ...
Once the user selects a template (or none), he gets the regular