![]() Using above mentioned techniques, we finally were able to run the application in both AIR and web-browser and it was a wonderful moment for us. For instance InvoiceViewAIR.mxml (extends from InvoiceView.mxml) could be something like this. InvoiceViewAIR.mxml and InvoiceViewWeb.mxml which extend from InvoiceView.mxml). We created a nomenclature something like AIR and Web (e.g. They became base version of view which could either be directly used in web version or needed to be extended for both web and AIR versions. We refactored the Views and taken out any AIR specific functionality. However for majority we could refactor and reuse them. For some views where it was just not possible, we created different views (one each for web and AIR version). ![]() One of the major issue comes when you have to reuse View (MXML). Instead of storing data in file-system (possible in AIR), we used SharedObject (Flex cookie) to store the user-information on desktop. We used recently introduced Flex 3.2 SDK to access these features. Recently Flash 10 introduced a new feature of read/write files in flash player without any need to send anything back to the server. ![]() It was just not possible in Flash 9 as it is a violation of sandbox security. We used Spring ActionScript, an ActionScript dependency injection framework, to inject appropriate AS3 interface implementations based on applications we are using (different applicationContext.xml for ProjectAIR and ProjectWeb).Īs AIR version is able to work on files (say images), we had to provide a similar functionality in web version also. In other words wherever AS3 code had to be implemented in different ways for AIR and Web version, we identified common abstraction in form of AS3 interfaces and provided AIR (in ProjectAIR) and Web (in ProjectWeb) based implementations. We abstracted out these functionalities using ActionScript (AS3) interfaces. SharedProject contained the common shared code between ProjectAIR and ProjectWeb.Īdobe AIR based applications use windows, file-system, SQL operations etc which needed to be replaced with their counterparts in web version. We started with refactoring existing AIR project (ProjectAIR) into two more projects, SharedProject and ProjectWeb (web project). To accomplish this task, we found a good article which provided us a basic architectural approach to do it. We had a similar situation in our project where we had to refactor an existing AIR application to provide support for both browser and AIR versions. In terms of features and power, browser based application may be a subset of desktop application but still provides majority of features for most of the quick users. On the other hand browser based applications are quick to experiment with. Desktop applications are here to stay as they come with the power of providing rich features in efficient/optimal way compared to browser mode.Īnother side of the coin is – in the competitive age of software products with two many choices and with a lot of time-crunch, end-user might be a bit lazy in downloading and installing just to be able to look at the features of the application. That’s the reason why Adobe AIR is considered as the future of desktop applications. Gone are the days when Windows operating system used to be ubiquitous in desktop market. If you don’t specify the sha1 there are number of implications, most importantly you lose out on all of our caching schemes, and you expose yourself to somebody spoofing the download location and tricking you into installing something malicious.Adobe AIR is a great technology to provide platform-independent desktop RIA applications. You should replace the ‘download’ commands with a ‘prefetch’ command and specify the size and sha1 of your downloads. Wait /bin/sh -c "devname= mount | grep yammer | cut -f1-1 -d \ | cut -f3-3 -d / | tail -1 hdiutil detach -force $devname " Wait “/Volumes/yammer/macairappinstaller.app/Contents/MacOS/Adobe AIR Installer” -silent -eulaAccepted “/Volumes/yammer/Yammer.air” I then used the Windows Software deployment wizard to upload the folder.ĭownload URL Of Folder Containing The AIR APP INSTALLER and the AIR APP to install/yammer.tmpĬontinue if ” ARI files are ARRIRAW Image files captured by ARRI digital cameras, and are opened with an image viewer/editor like Adobe Photoshop. Note: I renamed the AIR APP INSTALLATION file to airappinstaller, and created a folder called yammer which included the airappinstaller and the Yammer.air app. ![]() Here is the Action Script for silently installing the Yammer Adobe AIR app. The installer files are necessary to silently install Adobe AIR apps. Once Approved (Takes maybe 30 min) you will be emailed a link to download the adobe air installer files. I have figured the complete process out for Windows, but still working on the MAC action script.įirst thing you need to do is apply for a Redistribution License from Adobe. I have recently came across the need to install Adobe air applications using BigFix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |