Thanks for the replies everyone.
Having recently played with this code I can say it sounds like a good idea to me. The TOC code is tied to the parser and the output more strongly than it need be. It should be free to be output as part of the skin or part of the article. It should be quite easy to implement.
Andrew - I agree completely. I think hacking up the parser class would be easy, however I don't want to mess with the core code. I'd rather build this as an extension on top of what already exists. I've tried extending the class and overriding the Parser::formatHeadings() function but I don't know enough about hooks, etc at the moment to make an informed decision about the best way to go about this.
For my current project CSS positioning isn't an option because I need to position the TOC in another column relative to the actions bar (which I'm displaying vertically). Because both the TOC and Actions bars increase/decrease in size absolute positioning wont cut it, unfortunately.
Again, any suggestions from developers would be received with great appreciation :)
Best Regards, Chris
On Mar 13, 2007, at 11:20 PM, Andrew Dunbar wrote:
Andrew Dunbar (hippietrail)
-- http://wiktionarydev.leuksman.com http://linguaphile.sf.net
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/wikitech-l