[wp-hackers] Text Flow Again (Was: Let's whip WYSIWYG)
Michel Fortin
michel.fortin at michelf.com
Tue Jun 14 11:19:45 GMT 2005
Matt Mullenweg wrote:
> Feel free to submit requests for additional filters or actions on the
> bug tracker, these are almost always implemented.
It isn't as easy as it seems. To make things less abstract, I think the
problem can be summarized this way:
Q: Where can I put a Custom-Syntax-To-HTML filter in the text filter
chain so that it works properly?
A: Nowhere. Not "nowhere where there is a hook" but really "nowhere at
all."
This is a *design* issue; adding new filter hooks won't help much. What
is needed is a change to the default WordPress text flow, in the order
filters are run and the way some filters work to accomodate the new
text flow. I thought this was pretty obvious from [my weblog entry
about this][1] and [what I said before on this list][2].
Understanding and documenting the problem already took me much time and
effort. Without a clear commitment to understand and solve it, I won't
waste more time in explanations. So I ask: Is there someone willing to
rethink the entire text flow in order to address this issue?
[1]:
http://www.michelf.com/weblog/2005/wordpress-text-flow-vs-markdown/
[2]: http://textdrive.com/pipermail/wp-hackers/2005-June/001229.html
Jeff Minard wrote:
> Probably because there are better options out there now:
> - http://dev.wp-plugins.org/wiki/TextControl
I agree, Text Control way better than the Markdown plugin alone. But it
also has the same issues Markdown had prior all the "patch" work I have
done.
Michel Fortin
michel.fortin at michelf.com
http://www.michelf.com/
More information about the wp-hackers
mailing list