Category Archives: Mobile

CourseMedia Mobile for Android

Posted on by
Reply

Here is a video I recorded demonstrating progress with CourseMedia Mobile under development for the University of Denver.

CourseMedia is a course media management system that helps instructors organize and present media materials (images, video and audio). Instructors can create media galleries that can be accessed by their students online. Instructors have access to large collection of art and world history images, library reserve videos and audio works. The system is built using ColdFusion, Flash Media Server, Flash, Flex, and AIR.

While the editing functionality of CourseMedia is not present in the mobile version, we plan to support a directed viewing and study experience through this tool. The mobile Android version is represented here, but we do have plans to eventually publish for iOS and other platforms.

I captured this video using a neat little Java app called Droid@Screen which interfaces with the Android SDK.

Flash Development for Android Cookbook: RAW

Posted on by
Reply

My book just became available for preorder over at the Packt Publishing website. Not only can you preorder “Flash Development for Android Cookbook“, but it is also being included in the RAW program. This means that even though the book is not yet finished (still in draft stage, really) you can preorder the eBook or the print book and access the draft chapters online before the book is truly published!

For those wondering about the content, whether it leans more toward Flex or pure ActionScript; while there is a bit of Flex sprinkled throughout a few of the chapters, the code examples are almost always written in nothing but pure AS3 to allow anyone using any framework and toolset to implement the recipes easily. Full AS3 class downloads will be available through the Packt website.

As for the current status of the book, I’m putting the finishing touches on my Chapter 10 draft in the next few days. After that, one chapter left to write. The book is currently being tech reviewed and I’ll have to make more modifications based on that and other feedback.

See- it really is RAW right now! I’m not even sure if the publisher has properly typeset the chapters that are available.

So please spread the word, and place a preorder :)

UPDATE: I’ve heard that even though the publish date is marked as September, this was an original projection and the true print date is more likely May or June.

BlackBerry PlayBook: Code Signing Process

Posted on by
34

UPDATES BELOW…

Since the documentation over at the BlackBerry developer site isn’t exactly crystal… I’m going to share my code signing experience here in the hopes of sharing some information and perhaps helping others along. This is not a comprehensive overview; just my experience.

I have 3 AIR based PlayBook applications approved up in AppWorld right now. These were submitted before RIM had a process for signing our .bar files for submission. Now that we can sign .bar files, I figured I should do so. I was running the Tablet OS SDK within Flash Builder when I originally compiled the .bar files. I no longer have my system configured for this so will be signing the existing .bar files from the command line tools and not from Flash Builder. I am doing all of this from a 64-bit Windows 7 OS.

Treacherous Code Signing Ahead!

Note that I have removed my PIN and PASSWORD from these examples. So when you see yourPINorPASShere …just plug yours in.

  1. Register as a Blackberry AppWorld vendor.
  2. Order a code signing key from RIM. Once you receive and email from RIM with a .csj file included, you can begin proceed.
  3. If you haven’t done so already, download and install the Tablet OS SDK. You can install within Flash Builder build i3 (MAX or Labs) or just install for command line. For reasons mentioned above, I chose the second option.
  4. Something a bit misleading with the docs; they start off talking about the location of barsigner.csk… which I was able to locate- probably from a previous attempt at signing using Flash Builder. This threw me off big time. Ignore it. We want to open up the Windows command prompt and change the directory to the bin folder of our Tablet OS installation. In my case: cd C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin
  5. The next step is to run the command blackberry-signer -csksetup -cskpass yourPINorPASShere which will create barsigner.csk for you. Since I already had one, I needed to run blackberry-signer -cskdelete to delete it first.
  6. The next step is to register with the RIM server though use of the .csj file that you received via email. Run the following command to perform this action: blackberry-signer -register -csjpin yourPINorPASShere -cskpass yourPINorPASShere client-RDK-3894601367.csj
  7. Now, we have to generate a code signing cert (.p12 file) through use of a command like: blackberry-keytool -genkeypair -keystore FVM_QNX.p12 -storepass yourPINorPASShere -dname “Fractured Vision Media, LLC” -alias author …you must replace the cert name and company name with your own. This created another stumbling point as I received the message “keytool error: java.io.IOException: Incorrect AVA format” back each time I attempted to generate a cert. Apparently, the company name cannot include a comma, so simply changing that portion to “Fractured Vision Media LLC” did the trick and generated my .p12 cert. A lot of company names have commas, no?
  8. The final step is to sign your previously (in my case) compiled .bar file with the freshly generated cert. In order to do this, run a similar command to: blackberry-signer -keystore FVM_QNX.p12 -storepass yourPINorPASShere SketchNSave.bar author …Again, I received an error! This time “manifest error:Invalid value ’0.0.0.0′ for Package-Version.”. I apparently never changed the <versionNumber>0.0.0</versionNumber> value in that particular application, as my two other .bar files signed no problem. I changed it to <versionNumber>1.0.0</versionNumber> in the AIR manifest.
  9. So… now that I changed the AIR manifest file, I also need to compile a fresh .bar from that project so that I can sign it properly. To compile a .bar, we can run the command blackberry-airpackager -package SketchNSave.bar “E:\QNX Apps\SketchNSave\src\SketchNSave-app.xml” “E:\QNX Apps\SketchNSave\bin-debug\SketchNSave.swf” including all image files needed as well just as you normally compile an .air file using command line tools. This threw an additional few errors. One was my bad, in that I had spaces in my directory name and needed to enclose all paths in quotes as you can see above. A secondary error was thrown as well: “error 105: application.initialWindow.content contains an invalid valueError: AIR validation failed” – The problem here is that I needed to add the swf specification within the AIR manifest since I was not relying on Flash Builder to fill this in for me. No big deal. Fixed that and it compiled. Running blackberry-signer -keystore FVM_QNX.p12 -storepass yourPINorPASShere SketchNSave.bar now results in a signed .bar file ready for submission.
  10. Now just go to the vendor portal and submit new versions of your apps. I added all 3 as version 1.0.1 and uploaded the signed .bar files for each with a comment that they were now properly signed.

Not a lot of steps… not terribly difficult once you understand the workflow… but there is a lot of room for error and I think RIM could do a better job with the docs for sure!

I’m including my full Windows Command Prompt session log here:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Joseph>cd C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -csksetup -cskpass
 yourPINorPASShere
CSK file already exists.  Use -cskdelete to delete first.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -cskdelete
CSK file deleted.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -csksetup -cskpass
 yourPINorPASShere
CSK file created.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -register -csjpin
yourPINorPASShere -cskpass yourPINorPASShere client-RDK-3894601367.csj
Successfully registered with server.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-keytool -genkeypair -keys
tore FVM_QNX.p12 -storepass yourPINorPASShere -dname "Fractured Vision Media, LLC" -alias
author
keytool error: java.io.IOException: Incorrect AVA format

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-keytool -genkeypair -keys
tore FVM_QNX.p12 -storepass yourPINorPASShere -dname "cn=Fractured Vision Media LLC" -alia
s author

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -keystore FVM_QNX.
p12 -storepass yourPINorPASShere SketchNSave.bar author
manifest error:
Invalid value '0.0.0.0' for Package-Version.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -keystore FVM_QNX.
p12 -storepass yourPINorPASShere MyBlackList.bar author
bar signed.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -keystore FVM_QNX.
p12 -storepass yourPINorPASShere TransientRecorder.bar author
bar signed.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>E:\QNX Apps\SketchNSave\bin-debug\as
sets\images\icons\i128.pngblackberry-airpackager -package SketchNSave.bar E:\QNX
 Apps\SketchNSave\src\SketchNSave-app.xml E:\QNX Apps\SketchNSave\bin-debug\Sket
chNSave.swf E:\QNX Apps\SketchNSave\bin-debug\close.png E:\QNX Apps\SketchNSave\
bin-debug\assets\images\clear.png E:\QNX Apps\SketchNSave\bin-debug\assets\image
s\close.png E:\QNX Apps\SketchNSave\bin-debug\assets\images\save.png E:\QNX Apps
\SketchNSave\bin-debug\assets\images\splash.png E:\QNX Apps\SketchNSave\bin-debu
g\assets\images\title.png E:\QNX Apps\SketchNSave\bin-debug\assets\images\Writin
g.png E:\QNX Apps\SketchNSave\bin-debug\assets\images\icons\i128.png
'E:\QNX' is not recognized as an internal or external command,
operable program or batch file.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-airpackager -package SketchNSave.bar "E:\QNX Apps\SketchNSave\src\SketchNSave-app.xml" "E:\QNX Apps\Sketc
hNSave\bin-debug\SketchNSave.swf" "E:\QNX Apps\SketchNSave\bin-debug\close.png"
"E:\QNX Apps\SketchNSave\bin-debug\assets\images\clear.png" "E:\QNX Apps\SketchN
Save\bin-debug\assets\images\close.png" "E:\QNX Apps\SketchNSave\bin-debug\asset
s\images\save.png" "E:\QNX Apps\SketchNSave\bin-debug\assets\images\splash.jpg"
"E:\QNX Apps\SketchNSave\bin-debug\assets\images\title.png" "E:\QNX Apps\SketchN
Save\bin-debug\assets\images\Writing.png" "E:\QNX Apps\SketchNSave\bin-debug\ass
ets\images\icons\i128.png"
E:\QNX Apps\SketchNSave\src\SketchNSave-app.xml(49): error 105: application.init
ialWindow.content contains an invalid value
E:\QNX Apps\SketchNSave\src\SketchNSave-app.xml(49): error 105: application.init
ialWindow.content contains an invalid value
Error: AIR validation failed

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-airpackager -package Sket
chNSave.bar "E:\QNX Apps\SketchNSave\src\SketchNSave-app.xml" "E:\QNX Apps\Sketc
hNSave\bin-debug\SketchNSave.swf" "E:\QNX Apps\SketchNSave\bin-debug\close.png"
"E:\QNX Apps\SketchNSave\bin-debug\assets\images\clear.png" "E:\QNX Apps\SketchN
Save\bin-debug\assets\images\close.png" "E:\QNX Apps\SketchNSave\bin-debug\asset
s\images\save.png" "E:\QNX Apps\SketchNSave\bin-debug\assets\images\splash.jpg"
"E:\QNX Apps\SketchNSave\bin-debug\assets\images\title.png" "E:\QNX Apps\SketchN
Save\bin-debug\assets\images\Writing.png" "E:\QNX Apps\SketchNSave\bin-debug\ass
ets\images\icons\i128.png"
Using default icon: C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin\..\samples\icons
\blackberry-tablet-default-icon.png
The bar manifest file is valid.
Package created: SketchNSave.bar

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>blackberry-signer -keystore FVM_QNX.
p12 -storepass yourPINorPASShere SketchNSave.bar author
bar signed.

C:\TabletOS\blackberry-tablet-sdk-0.9.3\bin>

UPDATE #1
The process above only signs the application with the dev cert. You will need to sign with the registered RIM Signing Authority cert by using:

blackberry-signer -verbose -cskpass yourPINorPASShere -keystore FVM_QNX.p12 -storepass yourPINorPASShere SketchNSave.bar RDK

My apps were accepted… and a week later denied for this. They were also denied for not being compiled with Tablet OS 9.4 SDK as I had compiled them all with 9.3 (the only available SDK at the time).

UPDATE #2
This isn’t sufficient either, as I’m receiving a number of signing errors including:

barsigner error: server error: Code signing request failed because this file has
 been previously signed.

and

manifest error: Invalid value '3.0' for Package-Version.

Lovely.

UPDATE #3
I’ve recorded a video demonstrating the final process used to get true, verified signing of my BlackBerry PlayBook applications using Tablet OS 9.4 SDK.

UPDATE #4
Looks like RIM has finally developer a graphical interface tool for signing! Grab it over at:
http://supportforums.blackberry.com/t5/Testing-and-Deployment/BlackBerry-Tablet-OS-Graphical-Aid/ta-p/1207067?CPID=TWDResources&Date=11912

Approval of BlackBerry PlayBook AIR Apps

Posted on by
6

Happy to report that two of the applications I ported to the BlackBerry PlayBook have been approved!

Granted, it took almost 6 weeks for approval to take place, but this should give a little more hope to those developers who haven’t heard anything from RIM since submitting to AppWorld. Especially those aiming to get a free PlayBook!

Both apps use Flex 4.5 ‘Hero’ and are compiled to run on Adobe AIR for QNX. After I get my hands on a device, I’ll be performing additional development to take better advantage of the unique APIs available through the Tablet OS SDK and to better tweak each application for this specific piece of hardware.

Here are the two apps that have been approved:

My Black List!

My Black List! for the BlackBerry PlayBook

Ever think “I’m putting that guy on my black-list?” Well, now you can manage your black-list on the go with “My Black-List!”. Keep an up to date list of the people that cross you… so that you NEVER forget!

Sketch-N-Save

Sketch-N-Save for the BlackBerry PlayBook

Sketch-N-Save provides a canvas to perform simple sketches on your BlackBerry® Playbook™ device using a variety of colors and nib sizes and then save them as images to the device media storage.

Speaking on Mobile Workflow at D2W!

Posted on by
1

D2WC Speaker

Thrilled to announce that I will be speaking in the mobile track for the upcoming Designer/Developer/Mobile Workflow Conference (D2WC)!

One of my goals for this year was to attend and present at a few conferences that I’d never been to before; as I think it’s important to move beyond ordinary paths every so often. Well, so far I am attending 360|Flex and speaking at D2WC and Ignite Denver – so this goes a long way to fulfill that goal. I’ll hopefully be able to make my regular appearances at the Adobe Summer Institute and Adobe MAX (including the FITC Unconference) as well. This would provide me with a new conference opportunity every 3-4 months. Not bad!

I really like the premise of this conference. I began my professional career as a designer and shifted to a developer role early on so that I would be able to easily move across the complete workflow. Most of the work I do now is still on the developer side of things- but design remains a big part of my day-to-day work, and my personal workflow between the two areas is always changing. It is an exciting area to focus on for a conference!

My session information is below:

Adapting Expectations to Fit a Mobile Workflow
Friday, July 15th 2011 10:55AM – 11:55PM
Mobile devices exploded onto the scene in 2010 with a number of new platforms and form factors emerging to the forefront, iOS4, Android 2.2, mobile Flash Player, AIR for Android, QNX, iPad and other tablets… not to mention the digital living room. A literal invasion of unfamiliar platforms and devices with their own, unique sets of peculiarities and limitations. Such a radical shift in technology demands a concurrent shift in how we design and develop for these innovations. Where do we scale back? What additional functionality should we keep in mind during the planning phase? What restrictions do we need to work into the design and development phases of project workflow? We’ll discuss these problems in depth and attempt to find some practical adjustments to the current workflow to make the mobile process a bit more straightforward.

Of course, that is just my contribution. There are a lot of great speakers lined up and the following sessions are definitely on my must-see list:

  • Chad Udell – Is Mobile For Me? What Skills Do I Need?
  • David Orthinou – Developers – The Most Critical Designers On Your Project
  • Paul Trani – Hybrid – Complete Flash Workflow – From Design to Multiple Devices
  • Michelle Yaiser – We need to talk: Things you can do to prevent breaking up with your developer
  • Ben Stucki – The Dirty Truth About Project Management — how to get PM’s to do what you need to do?
  • Doug Winnie – TBA (also the keynote!)
  • Jim Babbage – wireframing/prototyping for mobile using Fireworks
  • Tom Green – Rocking the house with After Effects and Flash
  • Antonio Holguin – The smartest designer/developer workflow to build Flex/AIR Projects
  • Chris Griffith – UI Design Patterns for RIAs and Mobile
  • Elad Elrom – Make your Flex application show some skin

Don’t want to leave anyone out, so be sure to check out the full schedule.

Here are the conference details. I strongly urge you to join us!

Designer/Developer Workflow Conference
3 main tracks – designer, developer, and mobile
July 14-16, Kansas City, MO
Crown Plaza Hotel

Register Now!