I’m working on a database-intensive AIR application, and I’m thinking wistfully of earlier days spent on a Ruby on Rails project. ActiveRecord magnificence.
Alas, there’s no such ORM magic available yet in AIR. Actually, not true. A few people have recently started an AIR ActiveRecord effort, but the project doesn’t seem to be as far along as the Rails implementation.
So, if you’re building your own database access layer, Christopher Coenraets just posted a series of articles looking at some basics patterns for db interaction for AIR developers. The third article discusses a basic ORM.
Note on Christopher’s blog: I haven’t created -config.xml files for my Flex/AIR apps before. Christopher lists some changes to the application’s -config.xml file in order to keep some class metadata around during compiling. I had to dig for a minute or two to figure out that your project will not be created with this file, you simply have to add it yourself when and if you want to mess with the basic compilation process (e.g. if you’ve name your project MyFlexProject, you’ll be adding a MyFlexProject-config.xml file to the src directory.)
From Adobe’s Flex docs:
Explore posts in the same categories: Uncategorized
You can also use a local configuration file that overrides the compiler options of the flex-config.xml file. You give this local configuration file the same name as the MXML file, plus -config.xml” and store it in the same directory. When you compile your MXML file, the compiler looks for a local configuration file first, then the flex-config.xml file.