The very often criticized Badge installer for AIR applications (for cause of security) have a nice tutorials explaining how to use and configure it for your own AIR applications.
You can read this tutorials from the Adobe AIR Developer Center. this tutorials was done by David Tucker.
Ahmet
I came across this news from the Los Angeles Flex Users Group, then I followed to the new O’Reilly website on RIA: “Inside RIA” to finally end up on John Dowdell’s blog.
As it is the first time I disagree with John, and my answer started to be long, I preferred to import it here directly:
IMHO, Google indexing SWF text would be in fact a great news. I already saw some SWF content indexed by Google SE (mostly it was from static Flash Paper SWF).
The fact that we don’t promote our site only by pushing a keyword is obvious, but denigrating the absolute needs for SWF to be readable from SE is somewhat very strange.
As John said optimizing HTML, links inbounds and Metadata (not sure Metadata are still of any needs from Google) are important but where do you make the difference between HTML and SWF (from a not technical point of view)?
The major problem with SWF is mostly that they are providing dynamic content. The second major problem would be that the text can be converted to vector (so very hard to understand by computer, just see how captcha works…).
Those two problems take apart, why couldn’t we tag our SWF text with HTML tags? Can’t I tell to Google that this part of text is a H1 title or any HTML tag available? Or at least couldn’t I just be knowing how will Search Engines index my content?
A long time ago, I used the text under SWF layer solution to help increase the readability of important content to Search Engines, based on the already known behavior of search engines with HTML.
The sentence that made me jump down my chair was: “it’s hard to see how it would matter much“.
Well, for me just knowing that Google is interested in understanding SWF content is a great news! And I really hope that Matt info was solid :=)
Ahmet
As you certainly already know, the Adobe AIR beta 3 is out since mid December. I’ve just read on Oliver Goldman’s blog about a very interesting API added to AIR:
The ability to detect and launch AIR-based applications from within the browser, this API lets you do the following from within the browser:
- Install an AIR-based application
- Detect if an AIR-based application is installed, and
- Launch an (installed) AIR-based application.
Now that is great, so we can prompt someone to download our AIR application if he hasn’t previously installed it and else we can launch the application. So if you have one application that works for several website you can allow them to use it…
I need to find some free times to see if we can also transfer some args. to the applications from the browser to the applications (from www.a.com to AIRapps.exe).
Despite all the security issue that run along the Badge installation of AIR applications I think it is really a nice move and a great improvement. I already know that I won’t have time before February but after this date you can expect some tutorials on AIR very soon :)
