jd/adobe

I’m not sure how that would work… we could change our own versions of those two published-source browsers, but it has been hard to get such commits admitted for general distribution, much less into majority distribution

Really? I’ve found both the WebKit and Mozilla teams to be quite amenable to improvements and bug fixes. I would be extremely curious to look at the bugs that Adobe tried to submit. Do you have some links?

Creative Suite is already used every day for web formats. I’m not sure what you’re seeking.

I thought I made that clear: Let me save my Flash project as a web app that uses HTML, CSS, JavaScript and SVG. There is a gaping hole right now for sophisticated tools that produce rich interactive experiences for the Open Web technologies. The Flash IDE is what everyone wants to use, yet SWF is not available everywhere.

I’ll be even more explicit. I’m talking about the Flash IDE here: Vector graphics, rich text, filters/effects, animation, hooking up code snippets, audio/video, etc.

You also mention on your blog post “would you do for a movie clip?”. But didn’t I answer that question ?

As for the main point of my post, which you admit to side-stepping, the never-ending gospel according to JD is that Flash is a reliable runtime while the browsers are a grab bag of unreliable capabilities. My point is that Flash is only a reliable runtime because Macromedia/Adobe have made it so (by carefully engineering software that works reliably on the Windows, OSX and Linux platforms). Now it’s Adobe’s turn to do the same thing on the browsers.

“Adobe needs to update its tools to output in Open Web formats. Simple, no? Instead of Save As SWF, Save as Web App, right?”

Creative Suite is already used every day for web formats. I’m not sure what you’re seeking. Maybe this is relevant…?
http://blogs.adobe.com/jd/2010/02/adobe_authoring_for_html5.html

“And guess what – two of the major browser engines are open source – which means if a particular feature is missing in those implementations you can put an engineer on it for two months so that in the next version of the browser, it will be there for you.”

I’m not sure how that would work… we could change our own versions of those two published-source browsers, but it has been hard to get such commits admitted for general distribution, much less into majority distribution. Flash improvements, on the other hand, are adopted by “all” consumers within a year, and all browsers are thereby improved. Seems a useful complement.

jd/adobe