January 26th, 2009
Adobe has posted a new video to the Adobe Developer Connection: Flash Lite 3.0: Developing Mobile Applications. Your presenter is Dale Rankine of Moket, and I was pleased to have the opportunity to help with the content for the slides. It was a really fun project to work on, and Dale, Gabriel Gasca from Fuego Creative, and of course Suzanne Nguyen were great to work with.
Posted in Flash Lite 3 | 1 Comment »
January 16th, 2009
I’ve developed a panel for Fireworks that simplifies the process of creating guides in a grid system. I really like using Fireworks to mock-up designs, and personally find that it’s particularly well-suited to mocking up designs for mobile apps. I’ve never understood why it’s never been integrated with Device Central the same way that Photoshop and Illustrator are, but that’s another issue.
Since a lot of my apps/games are grid-based, I end up spending a lot of time just laying out guides that are spaced an equal distance apart. So if you want guides that are 10 pixels apart, then on a qVGA screen you’re looking at about 56 guides. That gets kind of tedious.
(Yes, I know I could just set up the grid to be spaced at 10 pixels and be done with it. But I like to use the grid as a sub-divider system – similar to how the grid in Illustrator can have subdivisions. When you’re dealing with small images and want pixel-perfect precision, it’s nice to have that flexibility.)
(Yes, I also know I could just use Illustrator for mock-ups, and I’ve done this in the past. I like Fireworks.)
The panel is pretty straightforward to use. It’s still very 1.0-ish, so here are some things to keep in mind:
- I’ve tested it on CS4 for the Mac, and CS3 and CS4 for Windows. I don’t have Fireworks CS3 installed on my Mac anymore, but I see no reason why it shouldn’t work;
- Bug: when the panel is started, it doesn’t properly register the current state of the guides, so the current color in the color picker will be black, even if the guides aren’t, and the lock/hide buttons may have the wrong text in them. Working on that!
- If the panel is narrower than the color palette when the picker is being used, you won’t see the entire palette. Not sure yet if this is a bug or just the way the panels work. This is why the panel is somewhat wider by default;
- It’s pretty ugly at the moment.
I just threw down some components and wanted to get it working. Perhaps I’ll pretty up subsequent versions, but for now it gets the job done;
- I’d like to add the ability to modify the grid to the same panel, which would make it easier to create that division/sub-division set-up I mentioned.
In any event, it’s perfectly workable as is. If you encounter any bugs or have any ideas/suggestions for features/improvements, please let me know!
Posted in Fireworks | No Comments »
January 13th, 2009
I’m fairly sure that there is no way to use SWF2JAR to bundle a Flash Lite SWF into a JAR package and be able to exit cleanly from the SWF. So this means using Eclipse (or your JME editor-of-choice) to do your packaging.
I’ve created a simple JME project that shows how to do this. In a nutshell, you need to use the DataRequest API in Capuchin to send a request to Java to quit the app. The files in the project show how this can be done; it’s all pretty simple, if you read through the DataRequest example in the Project Capuchin docs. I did not include the DataRequest.as file from the Capuchin examples/tutorials package since I’m not using classes in the example; so, depending on how your app is set up, you may need to include this when publishing your SWF.
At minimum, if you want to use this to just create a quittable Flash Lite app that uses no other Capuchin APIs, then:
- replace your
fscommand2("Quit") with the appropriate code from the sample FLA;
- drop your swf in the res/ directory of the project
- find this line of code in src/FLClose.java:
InputStream inp = getClass().getResourceAsStream("/FLTest.swf");
and change FLTest.swf to the name of your SWF;
- build the project and package it.
That’s the minimum required to get this working. Bear in mind that you will need to edit the JAD file to change the name of the app in the menu, if you want to use a custom icon, etc.
(Also bear in mind that I’m new to JME, make no guarantees that this will immediately work for you, etc., etc. I think it’s pretty risk-free, but use at your own risk.)
Posted in Project Capuchin | No Comments »