Device appears to be offline. Restarting the device may fix the problem. Ok. I'm running into the same exact problem. I cannot get it to work with the fix above. I'm running windows 7, Flash Builder 4.7, and did a fresh install of the Android SDK. I'm trying to use my Samsung Galaxy 3 as the debugging device. It has Android 4.3 as well as Air installed. Debugging is on and drivers installed.
I copied the following files. From C:\Program Files (x86)\Android\android-sdk\platform-tools adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll From C:\Program Files (x86)\Android\android-sdk\build-tools\19.0.1 aapt.exe From C:\Program Files (x86)\Android\android-sdk\build-tools\19.0.1\lib dx.jar To C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib \android\bin I still get the error below. Extending LabelItemRenderer to look like iTunes on the iPad.
Mobile ItemRenderer in ActionScript (Part 1) - AsFusion. If you are starting to do mobile development and are used to create all your ItemRenderers in MXML, you may notice that the small devices like phones and tablets do not perform as well as the desktop does and you need to start looking closely to different ways to optimize you app. One of the ways to optimize your mobile app is to create your ItemRenderers in ActionScript. Narciso Jaramillo wrote a good article for Devnet with great tips for mobile development and one of the items was exactly that, to keep your ItemRenderers in pure ActionScript. Narciso mentions the Flex Framework comes with two ItemRenderers one is LabelItemRenderer that extends UIComponent and the other is IconItemRenderer that extends LabelItemRenderer.
Those classes are great, but sometimes you have a different use case that needs a different set of classes. For the purpose of this tutorial, I'm planning a series of posts explaining the basics and moving on to more difficult renderers. Basic Example Application Styles. Pull down to refresh. [Code updated at the end of the article] I visited a Flex developer last week who’s developing an amazing Flex 4.5 application for tablet devices. We were talking about the classic mobile gestures on lists and the “pull down to refresh” behavior came up in the discussion. If you use the Twitter client on Android and on iOS, you can refresh the list of tweets by pulling down on the list.
To reproduce this classic mobile behavior, I used a few tricks. First, I needed to catch in real-time the position of the list. The tricks First, to get the position of the scrollbar, just use the Scroller object attached to your list: List.scroller.verticalScrollBar.value returns the position (Check the optimized UPDATE at the end of the post). If the users releases his finger to refresh the list, I just add an item to the data provider and I launch a new HTTP request. To display a “Loading” busy indicator, I have to analyse the data passed to the item renderer. And that’s it. [UPDATE] Code optimization. Android's CalendarContract Content Provider | Grokking Android.
Android developers have been longing for an official Calendar app and content provider since Android has been released. With the release of Ice Cream Sandwich Google has finally added this feature to our tools list. Now we developers can use the Calendar app from within our Activities using Intents or we can access the data by making use of the new CalendarContract content provider. CalendarContracts entities Before I explain how to use the calendar I first present the calendar’s data model. It consists of calendars, events, event instances, event attendees and reminders.
First we obviously have calendars. Events of multiple accounts Account selection when adding an event For each calendar you can have multiple events. Many events are recurring. Events can of course have multiple attendees as well as multiple reminders. Furthermore the data model contains some helper tables that are only relevant for sync adapters. What are sync adapters Sync adapters don’t deal with calendar data alone. Calendar Provider. The Calendar Provider is a repository for a user's calendar events.
The Calendar Provider API allows you to perform query, insert, update, and delete operations on calendars, events, attendees, reminders, and so on. The Calender Provider API can be used by applications and sync adapters. The rules vary depending on what type of program is making the calls. This document focuses primarily on using the Calendar Provider API as an application. For a discussion of how sync adapters are different, see Sync Adapters. Normally, to read or write calendar data, an application's manifest must include the proper permissions, described in User Permissions. Basics Content providers store data and make it accessible to applications. Every content provider exposes a public URI (wrapped as a Uri object) that uniquely identifies its data set.
Figure 1 shows a graphical representation of the Calendar Provider data model. Figure 1. The Calendar Provider API is designed to be flexible and powerful. <? The only free and fully functional Android GCM native extension for Adobe AIR « Priorisk. Overview This tutorial is about native extension for Adobe AIR and GCM (Google Cloud Messaging) which is a free service provided by Google that allows messages to be pushed to devices of your app users. If anyone is interested in more information on how to create an Android app capable of reception of GCM messages please check out this article on Google dev portal: GCM Tutorial.
In the course of development of a new social drawing app “Sketch Guess”, we wanted to add an ability for the server to notify players when important events occur in the game and display the appropriate view when the application resumes or restarts (the “fetch message payload after app just launched” capability is only implemented in our own solution so far). While there is an abundance of Adobe AIR native extensions for iOS, there was definitely a gap to be filled for Android applications. The extension is made for Adobe SDK 4.6 + AIR SDK 3.1 . Although, I’m sure it’ll work with 4.5 and 3.0 or newer versions. OAuth in Adobe AIR Applications built with Flash or Flex | ADC Presents. Community Translation Your transcript request has been submitted. Adobe TV does its best to accommodate transcript requests. It can take a few weeks for the transcript to become available in the Community Translation Project, so keep checking back.
Join the Community Translation Project Thanks for your interest in translating this episode! Please Confirm Your Interest Thanks for your interest in adding translations to this episode! An error occurred while processing your request. Another translator has already started to translate this episode. Thanks for Participating! This episode has been assigned to you and you can expect an e-mail shortly containing all the information you need to get started. About This Episode In this second episode of a two-part series, Piotr Walczyszyn demonstrates how easy it is to get started with the OAuth API authorization protocol in Adobe AIR applications built with Flash or Flex.
AIR 3 MapView Native Extension on iOS | www.flashmobileblog.com. For quite some time I’ve had my Radar application out on the Android Market, but one of the major annoyances was that the Google Maps component didn’t work on iOS. So I could never release the application for that platform, despite many “attempts” to get it working. With AIR 3 we have new feature called Native Extensions, so I asked one of our great Engineering team called Meet Shah to look at this problem and see if we could expose native UI components within an AIR application.
It turns out that Native Extensions don’t just give us the capability to access APIs like Notifications and Bluetooth, but to actually present native UI within our apps. The goal is to finish the Native Extension for Android, iOS, Playbook and Desktop platforms and then release the code. Meet decided to follow the current (deprecated) AS3 API for Flash so that your existing applications will continue to work ongoing, great idea! AIR3, Flash Map API, Flash Maps, Native Extensions. APIReference - air-maps-ane - Native Extension for using Maps in Adobe AIR applications.