codedread

Hallvord R.M. Steen (an Opera employee and member of the HTML WG) was kind enough to create a bug regarding an issue I had raised a few months back. It is currently not possible inside an embedded SVG to determine the parameters sent in from HTML:object if the two documents are on different domains. This appears to be a hole in the HTML4 spec, which doesn’t really address cross-domain security concerns for the HTML:object element. Click To Read More...

One reason I think Web Applications (as opposed to the now watered-down term of Rich Internet Applications) are great for users and developers, is because they do not need to be installed directly on the user’s computer. This is one thing I think Adobe has misunderstood about the ‘RIA’ revolution with AIR. Click To Read More...

David Leunen has released a new JavaScript library to fake SMIL for modern browsers that do not yet support declarative animation (Firefox 3.0- and Safari 3.0-). The nice thing about this is that it uses existing standards, so that when Mozilla and WebKit finally implement SMIL, this script will avoid executing. On that day, suddenly animations will become less processor-intensive. I’m all about progressive enhancement, but I’m also not above occasionally faking it a little to experiment with cool features. Click To Read More...

The Next Big Thing from Laszlo, OpenLaszlo 4 (OL4) codenamed “Legals”, is nearing completion and we should see a first Beta in January. This is the release of OpenLaszlo that will be able to compile to more than one runtime, allowing web developers to target either Flash or DHTML. In future versions of OL we might see more runtimes added to support Microsoft’s WPF/E and W3’s SVG and SMIL.

It will be interesting to see how web development will change in the coming year, as DHTML toolkits like Dojo, YUI, MochiKit, Google Web Toolkit, Microsoft Atlas continue to mature, Adobe’s Flex 2 continues making inroads and Microsoft’s WPF/E deployment gets underway in earnest. Meanwhile, the venerable Java Platform is still evolving, parts of it now open source and Jave SE 6 recently becoming available.

All of these are signs that seasoned web developers are finally ready to move up the tool-chain stack away from the simple text editor. I think key things to look for in differentiation between the various frameworks are:

• Tool Support: What kind of developer tools are out there to support development in your framework/language(s) of choice? From what I understand, Adobe has always been good with developer tools. On the Java side, there’s NetBeans. On the DHTML side, there’s Eclipse’s wtp. Maybe it’s time I looked into IDEforLaszlo in the New Year. Do your tools allow you to quickly and easily test and debug your code?
• Community Involvement: Not necessarily just an open source community, but a vibrant one with lots of energy and open participation. Of course, a transparent development process will help here.
• Cross-Platform Support: You need to support all of the “high tier” browsers like Firefox, Opera and Safari and you need to support multiple operating systems equally. People are passionate about their browsers and operating systems. Projects need to be careful not to lose the next hot web developer to a more compatible framework.
• Ease of Deployment: How easy is it to change one line of code and deploy that change? That was always one of the beauties of the early days of the web - simply update your HTML file and save it on the server
• Beware Of Vendor Lock-In: This is going to sound very anti-corporate, but the truth is that when one company controls the toolkits and the standards, there is always the potential for that project to be shelved or neglected or dropped in favour of new ventures. This ends up taking its toll on the web developer. With open standards and open source toolkits, developers can shield themselves from the whims of corporations.

Needless to say, competition will engender a very exciting year, with the winners being the web community as projects vie for the hearts of hackers everywhere, sparking further innovation. I hereby dub 2007 as the year of the “Web Hacker Wars” - let the battle begin!

Yesterday, Microsoft released their first public preview version of their WPF/E plugin (WPF/E = Windows Presentation Format Everywhere). WPF/E is the web-version of WPF, which is Microsoft’s new graphical framework, available in Vista. WPF/E is a direct competitor of Adobe’s Flash and other open standards based approaches like SVG. Click To Read More...

Apparently the Chicago area is supposed to be hit with the biggest snowstorm in 28 years for December 1st. So, in celebration, I’ve turned on the snow in my blog header. For those with cool web browsers like Firefox 1.5+ or Opera 9 (or even the not-cool browser Internet Explorer with the Adobe SVG Viewer plugin) you might need to right-click in the image frame to force reload … or wait until your browser’s cache pops. For those curious, the SVG does not display at all using Emiasys’ Renesis plugin … pooh.

Anyway, sorry for the CPU hit, but ’tis the season. If anyone can let me know if a Safari nightly build displays the snow yet, that would be awesome - you can consider it your Christmas present to me.

Hm, I wonder if I should try to modify the library to use the Dojo2D API in the Dojo toolkit for that true cross-browser effect. That might prove to be a fun little project and a good way to dip my toe in the Ajax toolkit pool…

[Update: Merry Christmas to me. Allan Jardine tells me in his comment below that it’s snowing in Safari too. Great news!]

I agree with Ryan: I don’t think there is a “Google OS” product. To Google, the “operating system” is the browser, that’s why they’re putting money in Mozilla’s pockets. Too bad Google Documents doesn’t support Opera 9 yet (though if you append “&browserok=true” to the URL, you can at least create documents, not spreadsheets).