I have an application in mind, where an already existing and authenicated set of users (auth based on users in a MySQL table and on cookies) should be presented with a mixture of HumanlyWrittenMarkup 
and MachineGeneratedMarkup (e.g. from syslog and SQL selects - the results containing references to HumanlyWrittenMarkup). So I have an application, where I need different User and Page concepts.
- What about inserting this data by using macros or processors?
Very good - yes I think that will solve 90% of my problem. --PeterMorch
- One reason why no one really has done it is IMHO that there is not much real improvement
Not for static page names. But if the number and names of pages are determined at run-time, that is another matter, for which the presence and contents of a file are not suited. But I can see that I now create trouble with RecentChanges, page count, Searches. A HUGE job, it looks like, now I think about it. --PeterMorch
- You perhaps can mimic the generated pages with actions (see fullsearch for an example)
I think OliverGraf is already working on the User refactoring
If I actually coded this, it would require modification to at least Page.py, PageEdit.py and User.py, but since (some of) the methods therein are static methods, it would probably also affect all callers. (Or is there some cool Python run-time import feature I could use?)
If this is something the community would consider adding to MoinMoin, I'll write the code, but if its just for me, I'll probably end up with a patch to just the .py files...
Is this something anybody else has considered / done already? Any pointers on how this would fit into the architecture before I commence? :-D Or should this go into MoinMoinIdeas? Where exactly would be best?
I could imagine this as part of the 1.4 release. Be aware that there are some other functions than load and save that have to be overloaded - especially if you want to use the improved functionality of the backend (diffs, incremental backup, ...). -- PeterMorch 2004.05.17