Building A Mobile App Using Flash Builder 4.5
Adobe has lately launched Flash Builder four.5. This launch enables developers to construct “Mobile Apps” for some celthe lular device structures, similarly to developing internet applications and laptop packages using MXML and Actionscript 3.
This release seems squarely focused at coping with the latest remarks from Steve Jobs and others, and the ensuing debate over whether Flash is useless, given the competencies of HTML five and different technological trends.
Since this is quite a chief release for Adobe and a crucial new capability for us Flex developers we notion we might go through the method of developing a smallish App and enforcing it on some of the gadgets. The idea of being capable to increase Mobile Apps for a wide variety of mobile gadgets the usage of an unmarried code base is certainly an attractive one.
Overall, the developer enjoys that Adobe has added with Flash Builder four. Five is pretty spectacular, even though there are one or two pretty fundamental omissions. Given the differences in Operating System, screen length, screen resolution, and handset capability deploying a Mobile App for a variety of gadgets is a daunting undertaking. Whilst it would not remedy all issues, Flash Builder 4.5 is simply an awesome begin.
Flash Builder four.5 would not goal each mobile device in the marketplace. It goals cell devices running Android 2.2 and upwards, iOS (iPhone 3G, iPhone four and iPad) and QNX (Blackberry Playbook Tablet). These are essentially the excessive capability of present-day Operating Systems for Smartphones and Tablet PCs. That covers around 50% of the existing cell tool established base and pretty possibly a much better percent of recent cell tool income. The vital omissions to the target platforms available are Symbian, Blackberry Smartphones and Windows Mobile 7.
Development Environment and Experience
Overall, the usage of Flash Builder four. Five to broaden Mobile Apps is extensively just like the use of it to increase computer packages for Adobe Air or web packages strolling within the Flash Player. The Flash Builder development environment is properly integrated with the rest of Adobe’s services such as Creative Suite five.5 and Flash Catalyst so that you can increase assets in those packages and import them into Flash Builder easily. Developers use MXML and Actionscript to expand the App, but there’s a more constrained range of user controls. Importantly there may be the same connectivity to records offerings the use of Web Services, AMF, HTTP and similar.
Differences to Developing an Air or Web Application
The ViewNavigatorApplication Tag
The first distinction you notice with developing Mobile Apps is that in preference to an Application tag that’s used for developing Air and web packages, you’ve got a ViewNavigatorApplication tag. With the Application tag you usually location a navigation manage after which region toddler components (efficiently the extraordinary views) within the navigator manage. This offers developers the capability to recognize what components are being used irrespective of how deep they are buried in the file hierarchy. With ViewNavigator however whilst you navigate to a distinct View you “pop” an extraordinary View onto the screen with the aid of call. You can then pop different views later in response to activities and user moves. You must move again to the house screen through the equal view order but in reverse.
With the Application tag since you are privy to what components represent your baby monitors, you could configure the software to skip any required records from the primary software to the kid additives. Since residences are commonly strongly typed, Flash Builder will deliver construct time mistakes if you are attempting to get right of entry to or skip a belonging that don’t exist. With Mobile Apps and the ViewNavigator tag, the compiler doesn’t honestly see the other Views which can be a part of the application till runtime consequently the developer loses an essential stage of errors checking before runtime. In addition, Views only have a single “Data” belongings. The Data property may be any item, so you can bypass a set of all of the records you require however build time blunders checking is lost on whether homes inside the statistics being handed actually exist.
There isn’t a drop-down listing in Flash Builder Mobile. No, there definitely isn’t. To me, this appears the biggest oversight and I anticipate in Flash Builder five, or optimistically earlier than that, they’ll restoration it. However, for now, the workaround is to have a button that looks like a drop-down list (has a skin with a drop-down listing icon) after which whilst the person clicks the button, to pop up a component based across the “SkinnablePopUpContainer” with a listing of your items internal it. So you can come to be with something that appears to the user like a drop-down the listing, however, is sincerely a button that calls a pop up with a listing of objects.
No MX Components Except Charts
No MX components will paintings besides charts. The MX namespace isn’t always available in Mobile Apps so most of the MX components aren’t available in the drop-down menu within the intellisense editor. In addition, a number of the Spark additives (eg dropdown list) are “Not Mobile Optimized” which is Adobe’s way of announcing they probably won’t work. In popular but, there are sufficient controls to create the display screen you need.
From the appearance of it then, being able to give you something to be able to appearance suitable on each screen seems like undertaking impossible. However, Flash Builder comes with built-in capabilities that help considerably. Firstly, you may say what screen density you are targeting after which when the App masses if the device being used has a different display screen density, the App will shrink and make bigger buttons and other components as required. Flash Builder categorizes every tool as having certainly one of three display densities, either 160, 240 or 320 dpi.
Bitmap photographs but shrink and develop very poorly so the above approach is not suitable. To handle this, Adobe has provided the “MultiDpiBitmapSource”. This is wherein if you are using a bitmap as the icon for a button, you could offer three unique versions of the identical bitmap to the button, every sized to goal display screen density one hundred sixty, 240 or 320. Flash Builder will then hit upon what the device is and use the correct bitmap as the icon.
The end result is that you may code once after which and then after spending a few efforts ensuring it seems as properly as possible in various conditions, it’s going to look quite correct in maximum gadgets. If you’re targeting the full spectrum of gadgets you’ll have a few sorts of change-off of time spent on styling v the payback for every device. Some research into the target market length for each tool after which prioritization will enable you to make suitable choices on what the principle device have to be after which how tons time have to be spent styling for the other gadgets.