Can I use Adobe AIR to create applications using Javascript and the Web Audio API and then have said applications still retain their audio functionality after they are turned into stand alone desktop/mobile applications. I have not started using Adobe AIR yet so I am not acquainted with the software.
I don't think AIR's runtime includes Web Audio support; it may on iOS, if the user has iOS6 installed; won't have it on Android right now, and doubtful they keep it synced with current Chromium on desktop.
Related
I'm currently trying to know if I can release a couple of my games on Windows Store. The games are single-file executables and they do not require any additional software installed nor installation. More to say, they performed very well on Steam.
I don't plan to use in-app purchases or ads. The games support any screen resolution and both mouse and touch input and fullscreen mode.
So is there a way to publish a "not-Visual-Studio" app on Windows Store?
I have found this thread on Windows Dev Center but not sure if the guy succeed with his trial and it seems he was talking about releasing air app, not a standalone .EXE .
Any help?
Adobe Air is not a way you can create a windows store app. There is a windows desktop bridge for converting .net apps to windows store apps. There is an ios bridge to convert apps created objective c to windows store apps. There is also a way to convert web apps to windows store apps. I am not aware of any way to convert an adobe app air to a windows store app.
I want to evaluate the new sandboxing mechanism in Windows 8/Windows Server 2012. I searched MSDN site for any resources but the documentation is extremely scarce. In comparison with FreeBSD Capsicum documentation, the one provided by Microsoft is just unusable.
How are we supposed to build robust sandboxed apps? Are the sandboxing APIs intended for metro style apps only?
I'm not sure what you mean by "sandboxing APIs". All "metro" (Windows 8 UI Applications) are sandboxed. I'm not aware of any way to sandbox desktop applications in the same way. See here.
Metro apps are pretty tightly sandboxed, and apps submitted to the
Windows Store need to declare many types of capabilities that they use
— not unlike Google Play's permissions list.
. . .
Windows 8 features a specific SDK for Metro style apps . . .
A quick explanation of capabilities: There are certain potentially sensitive things that you can do on a user's machine, such as access the Pictures library or use the webcam. If an app wants to do these things, the developer must declare a capability in the app's manifest. Then, when users download the app from the Windows Store, they can clearly see if the app is using any of this functionality. More info and a list of all of the capabilities is provided at App capability declarations.
Regarding sandboxing, there is some information at http://msdn.microsoft.com/en-us/library/ie/hh673561(v=vs.85).aspx. Yes, Metro-style apps are sandboxed in a way that desktop apps are not.
There is a whitepaper discussing security in Windows Store apps built with HTML5 at Secure development of Metro style apps with HTML5. There are also some common security scenarios documented.
at first i thought with Titanium, i can develop for Mobile and Desktop over AIR on Desktop only, but a quick look at the AIR Site, i guess i am wrong.
Benefit from a consistent, flexible,
and visual development environment for
applications on multiple platforms and
devices such as smartphones,
smartbooks, tablets, netbooks, and
PCs.
so my question is are there any major differences of titanium over air that i shld be aware of?
if no, i guess now air maybe better documented and has the backing of a more recognized company? after working with titanium desktop for a while i felt abit helpless and the docs are not really helping much
There are a lot of subtle differences, of course, and there are advantages and disadvantages to working in either, but the largest difference is that Titanium can produce apps for the iPhone/iPad, and AIR can't (well, at least not conveniently).
AIR can produce iPhone apps that you can deploy using the ad-hoc provisioning, but you can't distribute via the app store.
I've got desktop apps on both and am making a mobile app right now. Titanium desktop will cut your dev time to 1/3 of the time you'll take jumping through AIRs various sandboxes and security measures. Best yet, the code I wrote for my Ti desktop app is all javascript with about 3 Ti API calls and can be taken anywhere. The AIR app is all mangled by the wild structure you have to use with AIR apps and 1 million api calls.
The downside to Ti desktop is the API isn't as fully featured, and the Ti team pushes 4 times as many updates for the mobile API as the desktop API. Also, you won't be able to port your app from desktop to mobile easily as they are two different structures and APIs.
That said, developing for iPhone and Android on Ti is the same exact process and that won't happen on AIR.
Lots to weigh, but for my money it's Ti over AIR.
Hope this helps.
I am developing an application with Flash Lite designed to run on Nokia S60 5th edition phones using the Flash Lite API Bridge Interface. The application uses the API Bridge to access the phones camera and upload functionality to take a photo, display it to the user then upload it to a server. I am using Flash CS4 Professional and Device Central to develop and test the interface.
Are there any emulators that will run my flash lite app and simulate the camera? What are my options short of getting a phone and installing my app every time I want to test something new?
"Remote Device Access also known as RDA allows developers to test their applications on a variety of Symbian based Nokia devices remotely over the Internet. The current setups consist of over 40 devices and various device models. Usage is free of charge for all Forum Nokia members."
I'm curious what "features" are in Adobe AIR that makes it unique from browsers. I've heard that it has SQLlite on board, but what else makes it any different from Chrome's application mode (get the same functionality using Firefox's Prism plugin)
Is it fair to call it a browser?
AIR is technically a runtime much like Prism, and Silverlight (dunno about Chrome) for RIAs. They try to bridge the gap between the desktop applications and the browser. Browsers typically do not have disk access.
I'd suggest you go through this link.
Adobe Air is sort of like having a web application run on your desktop as if it was a windows/mac application. It is the answer from Adobe to Microsoft Silverlight out of browser experience. There are some technical differences; for one you need to install a seperate piece of software before you can use it while the Silverlight one comes with the Silverlight runtime. Another difference is applications running on Adobe Air have much higher permissions on your system than Silverlight ones.