I’ve been pretty busy recently and haven’t much been keeping up with what’s been going on with mozblogger, but it looks like Mike‘s been doing a lot of work. There’s now a second pane and a clipboard and some still-beta dragging stuff. I think there are some interface issues because there are some things I just can’t figure out (like textarea wrapping?).

Doing some skimming/catchup recently. Some interesting stuff:

Two lessons learned from a pit-stop at the McDonald’s on the road home. 1) While chocolate dipped ice cream cones sound good in theory, in practice, the warm chocolate will cause your soft-serve to start melting and leaking almost immediately. 2) While it may be possible to delude oneself into believing that french fries are a “soft” food that doesn’t require chewing, this is not the case. Chewing is bad, chewing means pain.

Click to edit me if you’re in IE5+. — Inspired by the K5 additions and impending deadlines, I’ve whipped up a little real-time editing / innerHTML test.

It’s literally two lines of code, one to make the text editable and one to grab the value (and presumably post it through an iframe).

Of course, Mozilla barely has a working textarea, so we’re not even going to talk about ranging or inline editing ability there. > Earlier post on same subject.

Was thinking a bit more about dynamic thread loading, and it seems to me that for a site like K5, it should be the preferred display method and the default if the browser supports it.

  • Minimizes transmission; only transfers what’s requested, when it’s requested w/o extra page wrapping data
  • Gives the additional information on reader interest that threaded mode does (extra posts are requested) without the annoying page refresh. Can be used to more accurate collaborative filtering, still more efficient than sending all posts nested or flat
  • Virtually insures focus for inline loading of alerts and ads. This obviously could be used for good or evil.

Some other improvements on dynamic loading could be inserting inline loading algorithms to do preload based on hover/focus activity (or in K5’s case, the inevitable ‘dynamic’ moderation)

(can be expanded w/ inline loading algorithms based on focus, etc.).