Since I'm creating this post directly in the browser, I don't have to login to my Movable Type account via the web, so I don't have to wait for it to load.
Another advantage is that the editor has all of the basic formatting capabilities you'd expect - bold, italics, quote, bullet points, insert image, etc. On the downside, however, I've just noticed that the HTML "b" and "i" tags are used rather than "strong" and "em", so I've had to switch to HTML mode and change these manually.
Hopefully these issues will be resolved in the future or -- better yet -- maybe we'll be able to add custom XHTML tags to the editor.
While there are other ways to get a WYSIWYG editor for Movable Type, they involve adding a plugin to MT itself. For example, MTEnhancedEntryEditing uses TinyMCE's nifty feature set - but I've found this problematic when using IE (and so have others). It works fine in Firefox however.
If you are an MT user and decide to use Performancing, take note of the following:
- You will be asked for the URL of your MT publishing API. This is not your mt.cgi URL; it is your mt-xmlrpc.cgi file (this is in the same directory as your mt.cgi file).
- You will be asked for your API username and password. The username is your regular MT username but the password is not necessarily your MT password.
- To check -- or reset -- your MT API password, log in to your MT account, go to >System Overview > Authors > Your Name, scroll to the bottom of the page and look for the "API Password" field.
Update (5 minutes later): Hmmm... I'm not so sure about Performancing after all. It added a "Powered by Performancing" tag and link to the bottom of my post (which I have just deleted). Is that link going to appear in every post I make with Performancing? That's spam!
I understand that the makers would like something back but, hey, I think a blog post evangelising the plugin (my original intention) and a link back to their site is enough.
Secondly, my paragraphs have become pseudo-paragraphs -- created using double BR tags, not P tags. This looks ugly in source code, but it looks even uglier in my Textile-2 enabled Movable Type interface.
Sorry Performancing, after an exciting start, you now get the thumbs down. Someone's bound to make a better blogging plugin soon.
Comments
0 comments / Skip to comment form
Leave a comment