Chumby Device Profile for Adobe Device Central CS3
November 22nd, 2007 by Scott Janousek
(No Ratings Yet)
Loading ...
I put some time towards creating a Chumby Device Profile for Adobe Device Central CS3 (Note: It’s very alpha at this point in time).
I am releasing this into the wild, because Adobe just released a Device Profile Update #4 … meaning it’s most likely to be quite some time before a certified Chumby profile makes it into Device Central via an update (if it does at all).
If you do decide to use it (at your own digression), please be mindful that I am looking for feedback.
Needless to say, I’ll be making updates to it overtime, so you should plan on checking back between now and official launch of chumbys (est 2008).
Download:
This is for Iron Forge model Chumby’s and above (Flash Lite 3.0), and not alpha prototypes (Flash Lite 2.x)!
Installation Instructions:
1. Download the zip above (chumby_template.zip).
2. Unzip it.
3. Follow the instructions in the README.txt file.
History Log:
▪ 11/21/2007 - very crude profile created and posted.
Feedback:
If you decide to use the one I created, I’d appreciate some feedback on it, as right now (as I mentioned previously in this post …) it’s very alpha.
You can send that feedback to me at chumby [@] scottjanousek [.] com.
What is supported, what isn’t:
Also, given some of features of the chumby, a lot of profile can’t be implemented, so bare that in mind (simulating the accelerometer, for instance).
Obviously, in terms of “working parts”, there is some core functionality currently missing including:
▪ No Accelerometer simulation (not likely to happen 
)
▪ No access to top “switch” (brings you to control panel, so not much use, anyways)
▪ … and more. See the README.txt file contained within the download
Bundling the profile as one single MXP
Right now, I’m not able to create an MXP that installs the required graphic skins and Device Central profile info … in Flash 8 this was easily done, because profiles were kept under the default Flash directory … however, with Device Central, this not true anymore.
Information surrounding paths, etc I could not find in any docs, and it may be the case that the current version of Adobe Extension Manager doesn’t support installing files inside the Adobe Device Central CS3 folder structure.
Is there a “$ variable shortcut” for Device Central inside an .MXI? Not sure. Someone please verify from Adobe, if possible.
Building your own custom profiles
If you’re wondering how you can build your own profile (like this one), you can check out the recent Flash/Device Central CS3 devnet article entitled: “Creating your own custom device profile for Adobe Device Central CS3″.
NOTE: This is not a certified device profile, nor is it sanctioned by either Chumby or Adobe, so at your own disgression.
Print This Post
November 23rd, 2007 at 1:54 pm
Hey Scott. Thanks for the post. If you end up hearing back from Adobe on how to package a CS3 .MXP for Device Central, please send me a note.
Thanks!
—Ryan
November 23rd, 2007 at 2:04 pm
Sorry about the typo. Meant .mxi
November 23rd, 2007 at 5:54 pm
Ryan, subscribe to comments on this post (if you haven’t already). That way I won’t have to remember to send you an email.
I’m not sure if it’s possible with the current build of the extension manager to target the Device Central path. More investigation is needed.
November 24th, 2007 at 9:36 am
I’ve put up a sample MXI on my blog with a pdf howto. I’m pretty doubtful that this will cover what you need.
Did you try replacing the $ symbol with an absolute path as a test?
November 24th, 2007 at 12:37 pm
Mark, the zip appears to be corrupt … or at least the latest WinZip is barfing on the archive.
I was trying to stay away from absolute paths, as I do know folks who install on drives other than C: for root (on Windows) … however, it is something to try, I suppose … especially if a new version of the Extension Manager is required so it is compatible with Device Central (aka a $ var can target the ADC path more easily).
November 24th, 2007 at 12:54 pm
Hey Mark, I’ve tracked down the MXI spec doc again.
http://download.macromedia.com/pub/exchange/mxi_file_format.pdf
These are the vars inside the doc I found:
$Dreamweaver Specifies the Dreamweaver installation folder
$Fireworks Specifies the Fireworks installation folder
$Flash Specifies the Flash installation folder
$System Specifies the System or System32 folder
$Fonts Specifies the Font folder on the computer’s hard disk
However, I had forgotten that MXI supports “tokens” … or user defined locations!
So I suppose I could create a custom UI in the MXP that prompts the user for the folder. Perhaps hardcode this, and allow the user to modify to a degree.
Not ideal … but it may be a good workaround if it’s not possible to target the Device Central path without user intervention … as it appears like is the case with the current version of the Extension Manager (but I may be wrong, need the Extension Manager team (Flash team?) to confirm) …
January 1st, 2008 at 7:42 pm
Hey, got it installed… why does it set up my .fla publish settings to flashlite 1.1?
January 1st, 2008 at 9:05 pm
1.) I am guessing you have the updates for Flash Lite 3 installed? or are you still working with Flash Lite 2? That may explain why it’s reverting to 1.1 …
2.) I will repackage the profile as a Device Central profile soon (inside of manual install).
3.) I have to make some mods anyways before that happens though (#2). As I said, it’s an alpha. I hope to get it to beta state soon. Probably this week.
January 2nd, 2008 at 3:56 pm
Yeah, I can select Flash Lite 3.0 from the publish settings. It seems to only fail when I use Device Central to create the .fla. I can do that… then change 1.1 to 3.0 and I’m good to go.
June 20th, 2008 at 11:20 am
Hey Scott,
nice piece of work! I was really desperately looking for a device supporting touchdisplay combined with FL3.
Unfortunately I wasn’t able to play an FLV movie on the chumby-emulator in cevice central. Maybe you could think about getting that fixed, or didn’t you implement that feature on purpose? I thought since the cumby has fl3, it should be able to…
first of all i thought that I could help myself by changing the XML-profile of the chumby but that turned out to be kinda naive of me
can you give me some hints or links on how to create own profiles for device central?
thanks in advance and keep up the good work!
June 20th, 2008 at 12:30 pm
Ulrich: http://www.adobe.com/devnet/devices/articles/custom_profiles.html
Yes. I do believe I made the updates for ON2 and sorenson, but perhaps I did not zip and push to the right location.
July 9th, 2008 at 4:54 pm
[...] CS3 Device Profile, by Scott Janousek [...]