Now that tags are working, I’ve started work on adding text-filter plugins for Typo. The current release (Typo 2.5.3) has support for 5 different combinations of Textile, Markdown, and SmartyPants hard-coded into it. The different combinations are actually repeated in 3 different places–the filtering code itself, the drop-down list for the built-in editor, and the Movable Type API code to list filter options.
That’s all gone now, replaced with a plugin system, similar to the sidebar plugins that made it into Typo 2.5. Individual filters get dropped into
components/plugins/textfilters/ and the system picks up on them automatically. Then there’s an interface in the admin UI that lets you combine the filters into named filter sets, so you can combine Markdown and SmartyPants into “My Filters” (or “Markdown with SmartyPants”, which Ecto recognizes and performs some magic to get Markdown previews to work right). The UI isn’t really complete yet, but the entire back end is there, and I’ve added two new filters as a demonstration of what we can do. Here’s the current list:
- Markdown. This is my favorite lightweight markup language, and I use it for everything that I write here.
- SmartyPants. A companion to Markdown, it does a typographical cleanup on HTML, turning ASCII single and double quotes into their typographically correct cousins and fixing em-dashes.
- Textile. Another lightweight markup language, like Markdown.
- Amazon. This turns URLs like
<a href="amazon:097669400X" ...>into a link to Amazon’s page for ASIN 097669400X, optionally attaching your Amazon affiliate tag. This is mostly a demonstration of what you can do with filters, although I’ll be using it on my blog.
- Flickr. This sticks a picture from Flickr on the page. This is a bit more complex then the Amazon filter, but similar in concept. It turns
<flickr img="31366117" ...>into a formated inline image, linked to Flickr’s full-sized image page, optionally with a caption attached. The full HTML produced is something like
<div style=""><a><img/></a><p>Caption</p></div>, which saves a lot of typing.
I’m currently working on a Sparklines plugin, using Glyph’s Ruby sparklines code. It’ll be similar to the
<flickr> tag, except it’ll spit out an
<img> tag that points to a built-in sparkline generator. Turning
<sparkline ...> into an image tag is trivial; allowing a text filter to export an action to the world is a bit more work.
There are currently two things that bother me about this code that I’ll need to resolve before releasing it:
<sparkline>tags–should they look like plain XHTML, or is that a mistake? Should I turn them into pseudo-bbcode tags, like
[flickr]? I’m currently leaning towards sticking a
typopseudo-namespace on the front of them, and turning them into
<typo:sparkline ...>. Any objections to that?
- The admin interface to this is killing me. I’d love to have a nice, simple way of editing each filter set, but it’s turning into a nightmare. I could just copy the sidebar config page (with a few changes–you can only include each filter once, unlike sidebars), but lots of people have had problems with the sidebar editor, and I’d like something a bit cleaner. Except I have no idea what to do.
If all goes well, I’ll post a public patch for comment early next week, and then kick off the Typo 4.0 process by committing this and the tag code later in the week.