Richard Darst
Email: echo rk`echo "q@mtvo.a" | tr "n-za-m" "a-mn-z"`et # (bash required)
I'm a no one. MrBeige or OFTC, nowadays freenode.
Current random thoughts
- Advanced navigational features: things required for authoring structured works (books).
- Navigation(children) that displays it like a table-of-contents.
- See below
- pages adding advanced nav features to sidebars
- "the way-back machine": view pages at some time in the past, links maintain date.
- LaTeX integration
- Documentation Improvements
I'm always confused by HelpContents and such, perhaps I could try to find a better way to arrange things.
- Macro which colorizes code from the filesystem
- Macros
- keyword argument parser
- Notes on epydoc:
- perhaps useful: @param m: slope of the line ; @type m: number, @keyword, @return
- Common: @param (type in paren), @return, @rtype
Documentation Improvements
(these are to be moved to the main docs once I know they are right)
- Formatters return strings and stuff, you have to take these strings and combine them yourself.
- Marcos
- return values should be strings. Use your formatter to build up a bunch of strings, join them yourself, and the macro returns the joined strings. The returned strings should
be formatted for whatever markup you are using-- thus, the need to use self.formatter. This just needs a link from HelpOnMacros (bottom section) to ApplyingFormatters. (should this be moved into Help.* ??)
- return values should be strings. Use your formatter to build up a bunch of strings, join them yourself, and the macro returns the joined strings. The returned strings should
- Have documentation for all major classes (formatters, requests, parsers, (macros?)), showing what their properties are, and another list of the _important_ ones-- information overload doesn't help casual extenders. The HTML docs start this, but they don't differentiate between what is important and what isn't. (perhaps this is better said as "what is public" and what is "private", with "private" meaning "not commonly used externally")
- Parsers write to requests, macros return their output string directly!!!
Structured Text
- (discussed with DasSheep/starshine)
goals
- Write a book in moin. Have advanced flow features: next, previous, up, see also.
- indexes-- be able to make specific references in the text for index compilation.
- More inter-document references. Use anchors and such, perhaps. Like LaTeX \label and \ref.
- Be able to put things on the navigation bar.
- This could also be usable for making more structured webpages.
make a TableOfContents page with nested list of pages. Have a nav macro which goes at the top and bottom of each page to list "up", "next", "prev".
- Indexes: how would this be implemented? Categories?
- Should there be a way to put some links in the navigation bar depending on what page you are looking at? Each page would say what links to put at the top. (should this be part of the new metadata?)
Things to keep an eye on
RobertSeeger -- large-scale export to other formats.