As an update, definition lists are now supported, they are simply defined as "term" and "definition" in the WikiDom listItem styles attribute, in addition to the already supported "bullet" and "number" styles.
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki...
It was disturbingly easy to add this functionality.
- Trevor
On Fri, Nov 4, 2011 at 2:33 PM, Trevor Parscal tparscal@wikimedia.orgwrote:
The other day I took the time to migrate the serializers into the latest codebase.
http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/VisualEditor/modu...
There are lots of things we can do to finish and or complete them, but they are a good way to hit the ground running.
Some key things that need to be worked on:
- es.HtmlSerializer needs an algorithm that expands the flat list
items in WikiDom into a tree structure more suitable for HTML rendering
- es.HtmlSerializer and es.WikitextSerializer need support for more
things, namely definition lists but other gaps may exists as well (and we need to define what definition lists look like in WikiDom)
- es.AnnotationSerializer needs some nesting smartness, so that
overlapped regions open and close properly (<b>a<i>b</b>c</i> should be <b>a<i>b</i></b><i>c</i> - es.ContentView does this correctly but is working from the linear data model)
- We need some sort of context that can be asked for the HTML of a
template, whether a page exists, etc. Initially this work is all done on the client, which means this is a wrapper for a lot of API calls, but either way, having a firm API between the renderer and the site context will help keep things clean and flexible
The serializers depend on some static methods in es and es.Html - but are otherwise very stand-alone. We may even want to move es and es.Html (which are very general purpose libraries) to a shared library that the parser and es code can both depend on.
- Trevor
On Thu, Oct 27, 2011 at 1:38 PM, Gabriel Wicke wicke@wikidev.net wrote:
Hi,
today I started to look into generating something closer to WikiDom from the parser in the ParserPlayground extension. For further testing and parser development, changes to the structure will need to be mirrored in the current serializers and renderers, which likely won't be used very long once the editor integration gets underway.
The serializers developed in wikidom/lib/es seem to be just what would be needed, so I am wondering if it would make sense to put some effort into plugging those into the parser at this early stage while converting the parser output to WikiDom. The existing round-trip and parser testing infrastructure can then already be run against these serializers.
The split codebases make this a bit harder than necessary, so maybe this would also be a good time to draw up a rough plan on how the integration should look like. Swapping the serializers will soon break the existing ParserPlayground extension, so a move to another extension or the wikidom repository might make sense.
Looking forward to your thoughts,
Gabriel
Wikitext-l mailing list Wikitext-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitext-l