On Sat, Dec 11, 2010 at 11:58 AM, Juancarlo Añez <apal...@gmail.com> wrote:

> I think that it will be best if this new parser produces only an ad-hoc
> syntactic tree (hierarchical structure, unknown meaning) that can be tested
> independently of the rest of Zim. Converting the syntactic tree to an
> xml.tree should be straightforward.

I already have a parser that understands most of the wiki language.

It lacks:

   1. Checkboxes.
   2. xml.etree
   3. Cleanup and unit tests.

The parser produces a very hierarchical structure through nested tuples and
lists, because that was easy and fast to code. Swtiching to xml.etree should
provide much more functionality, including pretty-printing.

At this point what matters is a code review that assesses if the code is
readable and understandable enough to merit its adoption once it has been
tested to production quality.

Where should I post the source code for review?

Juancarlo *Añez*
Mailing list: https://launchpad.net/~zim-wiki
Post to     : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Reply via email to