Over the past week, I found myself a small spot in Santa Cruz. I moved in Saturday, and I'm getting broadband today.
I'm going to see if I can drop in on the next Linux User's Group @ UC Santa Cruz soon. I'm even thinking about starting an informal Mozilla User's Group down here, just to let me interact with any other Mozillians in the area and provide what I can in the way of help.
DOM Level 3 Events has been revived: Working Draft released
So has CSS 2.1: Working Draft updated
This is good stuff. Unfortunately, there's not much to help me in determining what's changed from the previous versions... can someone help me on that?
ManyOne Networks submitted a proposal to speak at the Open Source Convention 2006 in Portland, Oregon. It was rejected. Personally, I've been to the last four OSCON's, and I didn't really want to go to this year's. Nothing against the Convention; it's a really wonderful experience, as close to a series of Vulcan mind melds as we can get. I'm just not personally inspired to go this year.
It's not money; this year, I actually can afford a full admission. No, I just don't have any urgent reason to go. Verbosio is progressing slowly, and it will require Gecko 1.9, so there's no point to trying to rush it to completion. There are no other projects I'm working on of that great importance (except for the Gecko patches, when I find a bug that sufficiently interests me -- like DOM stuff). I could pick up a lot of knowledge at OSCON by going, but it's just not right for me this year. The truth is, I need to take a break from it.
Tim, Vee, thanks for holding it the past eight years. It really does kick byte, and it's a genuine pleasure to go. I'm writing this blog entry to remind people about it.
I haven't closely looked at the list of offerings this year. I may change my mind... but I don't see that happening.
O'Reilly Open Source Convention 2006
Working drafts for Window, XMLHttpRequest announced
If you ask me, I think it's a Very Good Thing the W3C is looking at these. It harkens back to one of the original purposes of the W3C: creating a standard base for already-existing objects. Having written a JavaScript book before, I believe this should have been done five years ago for Window.
If you're going to offer commentary on these, do bear in mind these are Working Draft documents. In other words, they're about as stable as the Firefox trunk code -- or SeaMonkey trunk, for that matter. ;-) They are not stable specifications, nor should they be used as references. On the other hand, they do accept feedback, and working drafts are put out to the public specifically to seek feedback from consumers.
I'm actually surprised I didn't know about this. I guess I've been getting sloppy. :-)
I've often wanted to set one attribute on a XUL element and have that forcibly disable all the descendants of the XUL element at once. Given:
<xul:vbox sectiondisabled="true"> <xul:textbox value="foo"/> </xul:vbox>
the textbox should be disabled, in my opinion. (Or something like this.) So today I finally wrote up a script that could do this for me:
I also learned about nsIDOMXULControlElement. My work in XUL Widgets could only benefit from implementing this.
There's a couple advantages to this. I can "nest" disabled sections now, so if a inner section is no longer disabled, the outer section still takes precedence. Also, if I replace my usage of disabled with sectiondisabled (on the same node), then I don't have to worry about accidentally and incorrectly setting a disabled property.
I still have to figure out how to handle <xul:command/> elements and command dispatchers, but by and large this is a big improvement.
Feedback welcome.