Re: [Python-markdown-discuss] GSoC plan

[Waylan L. <wa...@gm...>]

Hi Artem,

On Wed, Jun 4, 2008 at 5:34 AM, Artem <ne...@gm...> wrote:
> 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.

Don't worry to much about breaking old extensions. If you refactor the
inline patterns (as noted below), extensions will need to be updated
anyway. Just make sure your changes are actually useful, not just a
new color for the bikeshed.

>
> - 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.

I agree. I'd really encourage you to spend the most time on the inline
pattern issue. That's where markdown.py needs the most help IMO.
>
> - 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.

I've been meaning to do this myself, but your more than welcome to.
>
> 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.

Just be sure to update any extensions in the repo that you break. Feel
free to check with me on any of them as I wrote most of them.
>
> 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?

Yes, that is correct.




-- 
----
Waylan Limberg
wa...@gm...