This page is created in hope that UseMod
1.1 might someday see the light of day. (NextRelease
seems to concern itself with version 1.0)
Many people are probably reluctant to incorporate changes that add radically new features, and thus stray from the best minimal feature set that makes usemod so popular. This is a correct approach, extended functionality is what patches are for. Which brings up the final reason for not releasing a version 1.1: it could break too many of the existing patches.
That said, I would like to propose a usemod 1.1 that will be a small enough incremental improvement over 1.0 that is important enough to consider, yet small enough not to require months of regression testing and not break too many patches. The goal I propose for 1.1 would be:
- Support for patches
- Preserving small size
- Support for CSS-based themes
Without further verbiage, here's a list of changes that I (UngarPeter?) would propose:
- 1. Fixes
- 2. Simplifications
- 3. Changes
- 4. CSS support
- 5. Other patches
At least we should put together a pure bugfix release, maybe as first step before adding new stuff. --MarkusLude
- I already have that ready... Now what do I do with it? -- UngarPeter
- You could send me them to usemod at usemod.com or try to check what hasn't made it yet to the latest bugfix release --MarkusLude
These are already fixed since bugfix release 1.0.2.
- Remove "ParseParas?" as it complicates life for patches that introduce new markup.
- Remove "FastGlob?", make this method the default.
- Remove the fast script parsing (eval) tricks (people who need faster execution are bound to run mod_perl).
- User management (login, logout, number-based id) seems to be the most confusing for my users. Either WikiPatches/UserList or WikiPatches/LoginLogoutByUsername -- this could also mitigate the growth of the user database.
- Introduce a "standard" place for patches to add their own global variables without breaking each other.
4. CSS support
- Make sure that the middle of the page (the page between DIV.wikiheader and DIV.wikifooter) is always in a DIV of it's own. This makes creating themes and CSS layouts much easier. (I've done this with all my personal wikis independently at one point or another) [added CSS class wikibody in the dev version -- MarkusLude]
- Create new config variables (FooterNote) that are eval()'ed before and after the header, the footer and the goto bar. This allows the generation of some additional formatting markup, which is very useful for themes.
- Make sure FooterNote and friends are displayed, even on pages that call &GetMinimumFooter().
5. Other patches
my primary goals for 1.1 are:
- change html to use html 4.01 transitional
- mostly done in dev version, some stuff maybe should be moved from html to css (is needed for html strict)
- add css stuff where needed for easier styling
- make script run with perl -wT. I prefer to do untaining on parameters rather early than later (this may make it a bit more complicated than in WikiPatches/TaintMode. that patch seems to miss some cases)
- state: in the dev version I don't get warnings any more, taint checks are still missing at least at a few places with regards to the page name, mainly editor or admin functions
- unify the action handling Do* functions
- look into problems with other charsets and try to fix them
I'm especially interested in feedback from using non-english usemod wikis and problems with the current CSS classes. Currently stuff is spread over lots of wiki pages here.
ToDo?: look through the bugs / patches listed on NextRelease which where already in 1.0 and cleanup that page.