Dreamwidth Development

We just released a beta-test of the jQuery implementation on journals. You can turn it on by going to the Dreamwidth Beta page.

You can test even if you're not a dev-type, but please don't spread this link around too widely just yet. There's still a lot left unimplemented (most notably quick reply), and until the most widely-used user-facing bits are done, it's going to seem pretty broken.

(I'd rather not have random people who don't see the warning in this entry come away with the impression that we all just broke / are planning to break Dreamwidth).

When things are ready to go public, we will be setting up a public beta procedure, and post in the appropriate locations. For now, please if you go turn on beta, expect only comment moderation and deletion to work :)

You'll probably want to save the link so you can go turn it off at will.


For developers, I've put up on the wiki some instructions for putting future features in beta.


There's a lot of ways to set up code in jQuery; here are some things that have been working for me. Putting up for discussion; I'd like to start setting up guidelines to make it easier to get started quickly, soon.
( thoughts on standardizing jQuery implementation )

I've been thinking about updating to jQuery 1.4.2, and adding jQuery UI. The new update page will definitely need both, but I'd like to update us earlier, so that we can test all the pages which use jQuery before we start introducing new code that uses it. (I think there are what, like five of them? *g*)

Right now we're using jQuery 1.3.2. Here are the jQuery 1.4 release notes. Nested parameter serialization looks incompatible with what we use, but it's easy enough to turn back into traditional mode. We may also need to double-check our JSON output in the future, to make sure that it passes jQuery's stricter JSON parsing. None of the files that use jQuery have JSON though.

So, does anyone know any reason to avoid the upgrade? Speak now :)