Wishlist of SimonHardyFrancis
Both ideas appear valuable. Code helps.
--jh
Now it's funny that you should mention that because I did follow the instructions successfully on MoinMoinUnixCvs but a quick look around MoinDev didn't result in any obvious instructions on how to get the thing working. Perhaps I over-looked something. A pointer in the right direction would be great. P.S.: I have lots of experience with Perl and only have a formal understanding of CGI and APACHE concepts. Python doesn't look that difficult... a sort of cross between Perl and Java -- SimonHardyFrancis 2003-01-29 15:47:51
- First of all, we should stone you for that heresy, on the spot. For the rest, "code helps" translates to "you are invited to provide patches or present an implementer"; otherwise, finding time to implement it can be a longer process. %) --jh
Ooops. Er... well what I meant was that indeed I wanted to have a go at patching / implementing but I came unstuck searching for instructions on how to get the sources working. Any help / pointers greatly appreciated. -- SimonHardyFrancis 2003-01-30 03:41:01
Browse around on MoinDev, MoinMoinUnixCvs, MoinMoinWinCvs and subscribe the moin-dev list, if you didn't do that already. As mentioned above, a good start would be to make a subpage index macro from a mix of the LocalSiteMap action and TableOfContents.
Bad news: I've got Redhat 7.x which only has crummy Python 1.5. And it looks like a problem to install Python 2.x on Redhat 7.x. And I guess Python 1.5 is too old, right?
No, that's no problem, if you keep the two installations apart (i.e. if you keep the 1.5 one in /usr). You can specifically select a py 2.2 installation in the bang path of moin.cgi. Install from source, and use --prefix.
Yeah I know... normally that should work. Except that py 2.2 doesn't compile. Apparently it's a known problem with the Redhat 7.x gcc libraries... and py 2.2
Probably easiest to install a newer, more up-to-date Linux and then have another go. At least Python will be installed then etc. I'll probably have a go with Debian or Mandrake...
Better Support For Lists Of Subpages
For those users who like using subpages then what about a more intuitive (?) way list those pages. For example, currently [[PageList(regex)]] makes a list of pages looking like dense text:
MainPage/SubPageA/ MainPage/SubPageA/SubSubPageA/ MainPage/SubPageA/SubSubPageA/DeepSubPageA/ MainPage/SubPageB/ MainPage/SubPageB/SubSubPageB/ MainPage/SubPageB/SubSubPageB/DeepSubPageB/
As an alternative then what about an option for a more hierarchical looking tree:
MainPage
+---SubPageA/
| +---SubSubPageA/
| +---DeepSubPageA/
+---SubPageB/
+---SubSubPageB/
+---DeepSubPageB/IMHO it's somewhat clearer and more importantly (for subpage enthusiasts such as myself) more compact on-screen.
A variation and/or implementation of this could be a modified version of LocalSiteMap.
Support For Metadata And Workflow Features
I'm new to MoinMoin but have some experience with http://twiki.org. The big difference that strikes me immediately is that MoinMoin suffers from a lack of what I'll call structured meta-data handling.
For example, this very page--if it were a TWiki page--would consist out of a mixture of wiki markup and dynamically generated tables of structured meta-data. Each feature would be a record in a table. Other columns in the tables would consist of info such as type of feature, date introduced, name of person suggesting it, page, status, etc.
The work-flow happened by changing one of the column values. For example change the type of feature from requested feature to rejected feature or todo feature effectively and automatically channels that meta-data record into different dynamically generated tables on different pages (for example, MoinMoinDev/RequestedFeatures, MoinMoinDev/RejectedFeatures, MoinMoinDev/CompletedFeatures, etc).
In this way then the meta-data 'flows' from page to page without the poor users getting finger cramps cutting and pasting and formatting normal wiki markup (instead of the meta-data).
IMHO this feature is one of the main reasons for TWiki being favored over other wikis by high-profile organizations. But not only that--I've got a hunch that the feature has also helped the TWiki user and development community no-end on http://twiki.org by reducing the manual friction to handle large volumes of similar items such as support questions, etc. My guess is that it would also provide a boost to MoinMoin too.