Charts and mx components aren’t available in a “Flex mobile project” created with Flash Builder Burrito (preview release). But it is possible to include them in your mobile project if you really need them.

Attention: Charts and mx components aren’t optimized for mobile applications, that’s why Adobe didn’t include them. So only use them if you really have to.

mx components

To add the default mx components to your project, just add the mx.swc library to your project. This library can be found at the following location: %YOUR_FLEX_SDK_INSTALLATION%/frameworks/libs/mx

chart components

Adding the chart components to your mobile project requires some more steps:

• Add the mx.swc and datavisualization.swc libraries to your project
  • mx.swc can be found at the following location: %YOUR_FLEX_SDK_INSTALLATION%/frameworks/libs/mx
  • datavisualization.swc can be found here: %YOUR_FLEX_SDK_INSTALLATION%/frameworks/libs
• The mx namespace isn’t included in airmobile-config because of a bug in the Flash Builder Burrito preview release (see FB-28538). Therefore autocomplete for chart components won’t work in mxml files. A “workaround” for this bug is to add the namespace declaration manually to the root tag of your mxml file, like this:
  <s:View xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:charts="mx.charts.*">

Once you’ve done these steps you should be good to go!

For this year’s Devoxx conference, iDA-MediaFoundry has created an Adobe AIR application for browsing the meeting schedule. You can find this app at http://www.ida-mediafoundry.be/devoxx.

iDA-MediaFoundry’s Jan en Filip also spoke at this conference about porting this AIR application to a mobile device. The mobile application itself can be downloaded from the Android Market (search for air.be.idamf.devoxx.android).

If you would like to know more about Adobe Flex mobile applications and the challenges & best practices for making them, don’t hesitate to contact us at info@ida-mediafoundry.be.

In the last post about the new Adobe Data Model codename Fiber First Experiences with the Adobe Data Model – Setup, I looked at the setup and installation process. This one will be a short post about how to run a first HelloWorld example, so let’s take a look if we can do a some click & drag and get some data on the screen.

A week ago or so, Adobe has put LiveCycle DataServices 3 on labs (http://labs.adobe.com/technologies/livecycle_dataservices3/), and one of the new things is the Adobe Data Model and the Modeler plugin code name Fiber. In this post I want to take a look at the setup of Fibre. It’s not a complete tutorial, I’m just taking notes wile trying to figure out how it works.

Over the past days I found the time to look at the Adobe LiveCycle Data Services 3 beta and in particular the new Adobe Data Model, and I thought I could make a small post series about my first experiences while I’m exploring the new possibilities.

Everybody loves youtube, for its almost unlimited source of music video’s and its funny clips. So how can we get those clips into our Flex or Air app? Here’s one way how to do it:

Adding bookmarks automatically can be realized with Acrobat Javascript. It is possible to use Acrobat Javascript in LiveCycle Designer. You can use the Acrobat Doc object in a LiveCycle Designer form. You must adapt your code to use the following technique of assigning a variable to the target of, for example, a click event, to access the current document:
var myDoc = event.target;

Afterwards it is quite easy to add the bookmarks. Just suppose you want to add a bookmark with the name of “Management Summary” which refers to a subform with the same name. You must place the javacript code on the layout:ready event of the subform because you need the page number. You first need a reference to the bookmark Root like in the following example:
var root = myDoc.bookmarkRoot;

Now you can add a bookmark to the root through the createChild method. This method has one required and two optional parameters:
1)Name of the bookmark
2)Expression to evaluate: in this case the page number. We must subtract 1 from the page number because acrobat starts counting from 0.
3)The 0-based index into the children array

You can add the bookmark as follows:
root.createChild(“Management Summary”, “this.pageNum=” + (xfa.layout.page(this)-1),0);

If you want to add a child to the bookmark you just created, you can do it like this:
var bm = root.children[0];
bm.createChild(“Overview”, “this.pageNum=” + (xfa.layout.page(this)-1),0);

Last week David and Maarten were speaking at the Adobe Usergroup NL event in Amsterdam. They did a session about Flash Builder 4 and Flash Catalyst user experience and demoed the Youtube Desktop Player, CrazyCam 3.0 and  (althoug very shortly the Contact Manager. All were skinned in Flash Catalyst and coded in Flash Builder with the Flex 4 SDK. More information and downloads of these apps will be online soon after we clean them up and tweak them some more, but the broadcast of the session is already online and can be viewed at:

The Adobe Usergroup NL’s website.

You can also find some pictures of the event at Maarten’s Flickr Steam.

We loved the experience and hope to do more of these sessions.
Also we want to thank Bert Haagendooren once more for inviting us, we had a blast!

This year’s trainees project was a desktop store build in AIR.  This is their story.

Tuesday 25 February I attended FITC in Amsterdam where I saw many interesting presentations and “cool shit” that I would like to share here.