This guide provides a reference for all native ActionScript APIs for the Adobe technology platform runtimes, Adobe
Flash Player and Adobe AIR, as well as the Flex framework APIs.
more fromimjohnny.cn
One of the comments to this post really caught my eye: ...... "Flash has always had better rendering consistency across platforms. However, HTML is much easier to build.
I always wondered why someone (Adobe?) doesn’t build a HTML/CSS/JS to Flash bridge. Sort of like sIfr but for the whole page. I really thought AIR could be that bridge. Write once, and render anywhere. :) ......... "
The thing is, the Adobe AiR runtime implements the WebKit layout engine. Whcih means WebKit documents based on HTML/CSS/JS should render just fine.
The real question will be how Adobe AiR handles the EcmaScript mess! Will they go with the ActionSript 3 version of JS - the one that is optimised for Tamarin? Or will they scale back to the MIcrosoft-Yahoo crippled version of official EcmaScript? My guess is that they push forward with ActiveScript 3 and try to convince WebKit and Mozilla groups to carry the open sourced Tamarin JiT. That would protect AiR developers as well as those who are seriously concerned about the future of the open web going forward.
more fromalex.dojotoolkit.org
Part two of the Prince McClean Adobe-Flash history. Excellent history involves Adobe SVG, Microsoft VmL-XAML-Silverlight, Apple WebKit, Sun (Java) as they battle for dominance over web applications and the future of the Web itself.
more fromwww.appleinsider.com
As many know, i've moved all my attention to WebKit and thw webkit "fixed/flow" document model as an alternative to Microsoft's proprietary XAML "fixed/flow". Webkit is the default layout for iPhone, Safari and the Adobe RIA runtime (Flex/Flash/AiR/Acrobat). It's just a short hop from WebKit to VisualForce Pages, the default document model for SalesForce.com developers. The Meta announcement further demonstrates how powerful the WebKit design is. It's will be worthwhile keepign an eye on the Meta JavaScript SDK-Runtime as a nice addition to WebKit. Good stuff!
more fromwww.atoker.com
Darryl Taft writes a follow up article covering the comments to his original AJAX-ARAX ruby on rails MS-iron python story
more fromwww.eweek.com
Darryl Taft posts an interesting question concerning running Ruby in a browser, and Microsoft's Silverlight proposal to do that with ARAX. I think he misses the larger context of the rise of RIA, and the wane of AJAX.
In particular, he misses the significance of two important RIA aspects: The Adobe RIA runs on the WebKit layout engine and document model. Microsoft RIA (Silverlight) runs on XAML "fixed/flow".
XAML "fixed/flow" is in effect, the web ready representation of MSOffice-OOXML. And Silverlight the Windows Presentation Foundation layer gone portable.
more fromwww.eweek.com
Blog from James Governor covers an exchange with Adobe's David Mendels concerning the transition from the static document centric Web 1.0, to the dynamic application platform we know today as the Web 2.0. David discusses the transition from DHTML to AJAX to RIA. David and his group at Adobe witnessed the transition and coined the phrase RIA - Rich Internet Application, to describe this incredible transition. No mention of WebKit as an important aspect enabling the interactive - dynamic document model behind Adobe RIA.
more fromwww.redmonk.com
The Safari-Webkit CSS Properties Reference.
more fromdeveloper.apple.com
Adobe's Erik Larson introduces Acrobat.com. His blog comments echo his post in response to an article at ComputerWorld: http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9091678
In the CW article, Guy Creese of the Burton Group holds the line, defending, as expected, the Microsoft alighnment of MSOffice, Exchange and SharePoint.
more fromblogs.adobe.com
good interview with Kevin Lynch about the future of the Web. Covers AIR, Flex, Flash, Silverlight and how the Web is moving from universal access and exchange of documents to that of applications. Lynch places Adboe products into a larger context of which problems these inventions solved. The new problem is that of expanding the Web to the desktop through these emerging universal applications.
more fromknowledge.wharton.upenn.edu
more fromwww.infoworld.com
Notation: * = Private bookmark and comment|… = Clipping [?] | … = Public highlight [?]
