From: Artem <ne...@gm...> - 2008-06-04 09:34:31
|
Hi all, So, I plan to do the following: - Some code refactoring, there are a lot of ideas about it in Greg Wilson's review, and I as well have some ideas. For instance, in current Markdown DOM implementation there are some differences from standard DOM libraries, for example usually in Element.replaceChild the first argument is newNode and the second is oldNode, in Markdown implementation first is oldNode and the second is newNode. Usually Element's parent property name is "parentNode", but here it's just "parent" etc. I realize that it'll break some extensions, but I think it'll help people in future to avoid reading code if they already know some DOM library. - There is something to do with Inline patterns, I didn't decide yet what is the best way to fix it. That was discussed in list and there are some ideas. I thought of writing syntax/lexical parser instead of current Inline Patterns mechanism, but I think it'll be a bit slower. - I'll try to boost performance, I think choosing the right way of inline patterns modification is the best way to boost Markdown. - An extension for Crunchy to load files using the Markdown syntax. - Test suite extension - Some additional documentation, maybe adding more examples about writing extension modules. Also I wrote to Django community asking if they need something special, but they said that nothing Django-specific, but API stability. Someone suggested adding markdown extras, but Waylan said that it was already almost done. Maybe while working I'll find some other ideas, of what else I can do. As I understand code must be compatible with python 2.3, 2.4, 2.5, isn't it? |