Test entry. I’m just testing another feature of the Flock browser. This time I’m using Flock to post a blog entry as a “Draft.” Not being terribly familiar with WordPress, I’m not certain what is going to happen. I’m assuming this entry will be saved in some non-public area of the WordPress admin pages, where I can publish it if I wish. If you are reading this, I most likely did.
And now, by biggest gripe about Flock. Keep in mind that this is a development version, 0.4.10 on OS X to be exact. And, to be fair to the Flock developers, the issue is already listed in their bug tracker (bug #1392) with a severity of “blocker,” which is very severe.
That being said, my biggest gripe is when it starts lagging when I open links in new tabs. The app will just kinda hang for several seconds. I haven’t made any attempt to analyze the problem in depth, as some did in the bug entry, but their accounts seem to include the symptoms I’ve been experiencing.
There is no Target Milestone set yet, but being a “blocker” I am guessing it will be sooner rather than later. Despite this problem, I’m still using Flock as my primary browser, unless I can’t afford the delays, in which case I use either Firefox 1.5RC1 on Windows XP or Safari on OS X.
UPDATE: Well, I think I was wrong about how the “draft” version of this post was handled. It now appears the draft was saved locally, as I couldn’t find any references to “drafts” in the administration pages of the blog software.
The only place I found it was on the Blog Topbar of the Blog Editor. A simple double-click and I was typing in this update. Yay Flock! Although, I just thought of a suggestion regarding the Blog Topbar: it would be nice if there was some visual indication that an entry is a draft.
As is, it would be easy to save a draft and then never publish it because I forgot to publish it and there are no visual clues to remind me.
Anyway, this post is much longer than I initially meant it to be. So, I’ll wrap it up right now and try publishing it.
