…that by placing:
<a name="<$MTEntryID pad="1"$>" href="http://<$MTBlogHost$>/path-to/mt.cgi?__mode=view&_type=entry&id=<$MTEntryID$>&blog_id=<$MTBlogID$>" onclick="OpenComments (this.href); return false"> </a>
in a strategic place you will have an invisible link that will open a window that allows you to edit the MT post you've embedded the link in?
Or that by placing:
<a name="<$MTCommentID pad="1"$>" href="http://<$MTBlogHost$>/path-to/mt.cgi?__mode=view&_type=comment&id=<$MTCommentID$>&blog_id=<$MTBlogID$>" onclick="OpenComments (this.href); return false"> </a>
in a strategic place you can do the same with comments?
Advantage: with entries, when you see that stupid misspelling you can fix it on the fly, with the text (minus all those distracting markup tags that probabl made you miss the error in the first place). Same with comments, plus you can delete assholes without searching for them.
Actually, the OpenComments javascript function makes the window kind of small for editing posts, so I have a seperate function that opens an 800px wide window (hey, it fits on my screen and no one else will use it anyway). Or you can just change OpenComments() so that it creates a resizeable window,