Now that Firefox 1.5 has been released, I thought I would follow up this entry with my corresponding entry for Firefox. Read the rest of this entry ...
Jon Ferraiolo of Adobe responds to concerns about Adobe's less-than-clear statements about SVG the "morning after" the post-Macromedia acquisition. Jon says that "SVG-Full" support will not be disrupted - - not exactly a glowing recommendation, but not exactly a death sentence. I had speculated on this yesterday, so Jon's response soothes my fears somewhat. He says that "Adobe's primary attitude towards SVG is fully positive" and the FAQ mention of SVG-T only "was *not* meant to imply anything negative about SVG in the desktop space" but I still maintain that zero mention of Adobe SVG Viewer is not a good sign.
Anyway, if the SVG 1.2 specs could just make it into Recommendation Status we'd see what implementors like Adobe and EvolGrafiX can do...
[Update: The day I posted this, the W3C SVG Working Group released its Third Last Call draft for SVG Tiny 1.2 with a comment cutoff date of December 28th. Now that's service!]
Lot of ups, lot of downs for SVG this past month or two. Let's recap them, shall we? Read the rest of this entry ...
As most people tripping around the blogosphere know, the Firefox 1.5 web browser was officially released tonight. If you already have Firefox 1.5 RC 3, then you already have the final version, but if not - go download your free copy now.
I guess this means that I have to start downloading the Firefox trunk builds if I want to be on the "bleeding edge"? For those of you who don't know, the "trunk" is the main line of development where new and untested features are included while the "1.8 branch" constitutes the stable line of code on which Firefox 1.5 is built.
The W3C CDF Working Group has released third Working Drafts of their documents:
Remember the quality of these documents depends on getting good feedback in the form of review comments that you can submit to the CDF WG Mailing List.
[Note that as of 2005-11-22, 8:43 AM CST all four links to these documents are broken, pointing to XML documents that require login. I have sent an email to have them corrected.]
[Update: Links were corrected by Kevin E Kelly as of 2005-11-22, 9:54 AM CST]