"NooParser" is the CVS branch for the new, modular parser architecture that should (hopefully) allow new types of Wiki notation to be added simply by defining a class in _UnitySite.py, or as part of an extension. See BraveNewWiki for more on this.
<<< As of last night (2003-09-29), I sorted out what I hope is the last major hurdle in getting NooParser to parse wiki notation as it stands. I need to sort out the extensions system and implement a few remaining (simple) node types, but hopefully it should be testable pretty soon. -- RobHague >>>
<<< NooParser development got slightly sidelined for a while, but as it fixes a number of long-standing problems, I'll have a go at finishing it off and putting it up this weekend (for testing initially, but hopefully it should become the sole version pretty quickly). And yes, this is displacement activity. -- RobHague (2004-04-20) >>>
<<< Yesterday (2005-03-28) I sorted out the snazzy new metaclass-based extension system, and wrote the node classes for most of the current syntax. When I've filled in a couple of remaining holes, I'll set up a CGI script so that people can view (but not edit, at least initially) the Wiki using the new parser, and spot any problems that I've missed.
Just in case you're wondering if there's a point to all of this, the new version already has a true verbatim mode (written }} - it would be very difficult to implement this in the current, point-replacement model), fixes a bunch of malformed content related UnityWikiBugs, and allows you to add new syntax (such as "standard" ==== headers) in a couple of lines of code.
-- RobHague>>>
<<< This morning (2006-02-08) I got round to looking into why the NooParser branch wasn't recognising POST request, and fixed it. Hence, I give you... http://unity.einval.com . At the moment, it's main purpose it to flush out the remaining rendering bugs, but when these are fixed (soon, hopefully) I'll migrate the content from here across. Thanks to Steve for hosting.
-- RobHague >>>