Making the current implementations easy to change about markdownsharp

[GoogleCodeExporter]

I don't feel that making every operation an overridable transform is really 
necessary. You Aren't Gonna Need It. (YAGNI).

Even in the case of nofollow, the logic required has nothing to do with 
markdown and logically belongs outside this class. See my response to that for 
more detail.

Original comment by [email protected] on 12 Nov 2010 at 8:54

[GoogleCodeExporter]

Original comment by [email protected] on 12 Nov 2010 at 9:03

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by [email protected] on 12 Nov 2010 at 9:03

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Respectfully, this is an open source project for everyone and anyone, so while 
WAGNI, I might need it and so may others.

Of course the project owners aren't obligated to implement any of this, but 
it's the kind of thing that increases the chance of a project being forked, or 
numerous people duplicating the effort of integrating this kind of thing.

Processing the generated HTML to include this kind of thing afterwards doesn't 
feel right to me.  I want to use a library like this to completely avoid having 
to deal with HTML.  Furthermore it just involves loads more string operations 
on the server which results in unnecessary GC pressure.  A library like this 
should be able to operate on a stream directly to reduce the working set of the 
function.  Providing callbacks as discussed here would allow for that in a 
simple way.  I like the idea.

Original comment by drewnoakes on 18 Nov 2010 at 3:23