Infrequently Noted

Alex Russell on browsers, standards, and the process of progress.


So yesterday I was —> <— this close to writing about how much I miss singing and how I got myself talked into singing in chior at church for christmas. But I thought better of it for some reason.

I've got some ideas about the data-transfer problem... I think that instead of hijacking the widget classes to suit our needs, a data receptor class might make sense. It could be subclassed to provide the correct handling of the data, but the superclass could handle things like registering it and making sure that data block get handled correctly by the loading scripts. Well, it's an idea anyway.

Server Interfance

netWindows needs a way to talk to servers genericaly. The parser and the loading scripts are a great interim solution, but I think what really needs to happen is some ready-to-roll extension of the two that can allow for XML data later. And it has to implement (and allow extension of) a subscribe-notify repository for data.

But this is a problem for another day. A day on which I don't have an exam. Which I happen to have one of today.

Data Transfer Demo

Today I found another site with a pageloading script similar to NW's, but they break it out and call it an "http buffer", or something. Anyway, basic principle is the same as with NW, you load content into a specified element via a hidden iframe, etc... yada yada...

Still haven't seen anyone else doing something like the generic parser though...perhaps I'm just out in left field with that one =)

Speaking of the generic parser and the loading queue, I built a little demo of netWindows data transport. Maybe it'll be entertaining for someone.


0.2.3 pre4 is out.

Bah humbug, time for sleep. A whole 2 hours of it.

Tomorrow (well, today, really) isn't going to be pretty.


More fun netWindows news.

The two files that were required to be included in 0.2.2 (NW_config.js and script_registry.js) have now been replaced with a single file, netWindows.js. Instead of needing a separate copy of NW_config.js for each directory in which you want to launch NW from, simply include netWindows.js using a relative URL from the page doing the loading. NW_config.js and script_registry.js will not be included with 0.2.3, so be prepared to update your environment pages when you upgrade.

Big thanks go out to Tim Morgan for inspiring this fix.

Older Posts

Newer Posts