We've just upgraded to the latest jQuery / jQuery UI version. I'd eventually like to settle us on jQuery 1.9 which according to their road map is the final one with support for older browsers, and will retain compatibility with 2.0 (which is lighter, by dropping said support for older browsers).
I've updated our own code as much as i could, to use the newer APIs, in some cases replacing our implementation with newly added functionality built into the library. I've also switched the tooltips from tooltip.js, to jquery ui's tooltips because the API fits everything else we use better and, more importantly, it's got people working on it who are focused on accessibility issues (so ARIA support, plus whatever else might be added in the future)
This gets rid of a schroedenbug with the contextualhover menu sometimes disappearing as soon as it appears at the risk of introducing new bugs. It overall seems to behave better, and was easier to debug, but do keep an eye out for weird behavior and let us know ASAP.
The contextualhover menu appearance has been changed; we have a bug open for actual further styling.
The light-colored theme for widgets has been tweaked just a tiny bit here and there. Most noticeable will probably be that dialog boxes/overlays now have a font size that matches the rest of the page, instead of being larger.
This isn't live on dreamwidth.org, but is on the develop branch, so you can poke at it. We'll push it live by next code push. If there aren't any major issues, we can take the jquery on journals out of beta shortly thereafter.
( Extra info on: Why JQuery-izing? )
We're going to create a registration form really soon but I wanted to tell you about this so you can put it on your calendar.
I figure you folks have better ideas for Wikipedia integration than I do (I didn't see any in Bugzilla but maybe they aren't there yet?). I know there's a WordPress plugin, PhotoCommons, that makes it easy for bloggers to browse Wikimedia Commons for freely licensed images to dress up their posts. Maybe replicating that functionality in Dreamwidth would be cool? I've added it to the Suggestions queue.
Of course you don't need to come to the event to work on MediaWiki or on integration with Wikimedia sites -- our site has an intro tutorial and we are on IRC at #mediawiki on FreeNode and so on. But if you came to the event, that would be cool too. Open data!
As you can imagine (Bob) this isn't very fun. Inevitably, we end up forgetting edge cases, which we only turn up after a user has run into the issue and reported it. (We probably have three or four outstanding bugs that have to do with how we haven't called the init function on this page, or after doing that action, and well it's a pain.)
So a thought: I propose we start using jQuery's .live() function in conjunction with a custom event. ( cut for examples and discussion of efficiency )
It looks like .delegate() is a better alternative to .live() (thanks jproulx!
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 )
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 :)