The Future of Flash…

FlashAppIconWith the release of Flash Professional CC 2014, the program has in many ways returned to its roots as a premiere animation and asset development tool. Let me take you back many years ago, the web was just text and mostly static images. But designers wanted to create a more expressive experience, from this Flash (then FutureSplash) was born.

For a long time, Flash served as the main solution to overcome the short comings of the web and the user experiences that so many of us wanted to create. Now the web platform has finally matured to the point where we can now create these experiences without Flash acting as a bridge for our visions. There is no doubt that the rich engaging things will use and build would not be possible without the content created by Flash.

But what about today? Most of the mobile devices sitting on my desk do not run Flash content in their browsers. But I still want to create engaging web content  that works on my mobile devices, as well as my desktop.

Some of the improvements for this release of Flash Professional CC 2014 is the abilities to publish your animation content into a variety of formats that are very mobile and standards friendly.

So now if I want to take my animation that I developed with all of the incredible animation tools with Flash Pro to play as a canvas based animation, it is not a problem. I can leverage the createjs framework (written by the incredible team a gskinner.com). If want to just use Flash to create a sprite sheet for use in another animation framework, I can just as easily publish that as well.

FlashWebGL

Last but not least, if I want to have my animation leverage the power of WebGL, the latest release has an experimental version of publishing to that format as well.

If you are looking for a tool to help you animate something for web, I would take a fresh look at Flash. There are some great tutorial on these new features on the revised adobe.com site.

PhoneGap Day(s) and a Call for Speakers

phonegapThe PhoneGap team just announced the dates for PhoneGap Day(s). This year PhoneGap Day will be held in San Francisco on October 24th and Berlin on September 26th. As before, there will be full day workshops on the day before. For more information, visit the web page: http://pgday.phonegap.com/

I attended last year’s PhoneGap day in Portland, and can easily say it was a great event. I am looking forward to attending it again.

In addition, the call for speakers is open as well. I am working up a few topics that I plan to submit. What is nice is these talks are short and sweet (about 20 minutes), so it is perfect for . Hope to see you there!

Cordova 3.5.0 Now on PhoneGap Build

PhoneGap Build has added support for Cordova 3.5.0.

I will be updating ConfiGAP shortly to support this, but in the meantime, you can edit your  config.xml with <preference name=”phonegap-version” value=”3.5.0″ />.

If you want to know what’s in 3.5, you can read more about it at:

PhoneGap Developer App for Windows Phone 8

Windows 8

The PhoneGap team announced that the PhoneGap Developer App is now available on the Windows Phone Store. It supports not only Windows Phone 8, but also the upcoming 8.1 update!

For newcomers, the PhoneGap Developer App aims to lower the barrier of entry to creating PhoneGap apps. You can immediately preview your app on a device without installing platform SDKs, registering devices, or even compiling code. Plus, you have full access to the official PhoneGap APIs.

Possibly the most exciting aspect of this announcement is that you can now develop your apps on an OS X machine and preview on a Windows Phone device. Cross-platform, indeed!

I somehow missed posting this correctly, but that I would go ahead and post it even though it is a bit late.

Creative Cloud Event San Diego

sandiegoccevent

Adobe Evangelist, Paul Trani will be coming to San Diego. Join us to see the latest in Adobe Creative Cloud since CS6. Learn new features that make everyday tasks easier and faster and how support for cutting-edge hardware and standards will free you to build anything you can imagine. Get answers to your questions and get inspired by designers who are creating amazing work.

Wake-Up-Now-Sign-Up-Now-WUN

Agenda

6:00 PM – 6:30 PM – Registration Check-In, Food, Networking
6:30 PM – 8:30 PM – Presentation by Paul Trani
8:30 PM – 9:00 PM – Q&A, Raffle & Wrap-Up

Location Details

San Diego City College Career Technology Building
1081 16th St
San Diego, CA 92101

Cost

FREE, just RSVP.

Prizes

Adobe will be providing prizes including a FREE One year Creative Cloud Membership. You must be present to win.

Hope to see you there!

Edge Animate & PhoneGap Build: part 2

In a previous post I wrote on how to convert the audio playback that Edge Animate uses into some that PhoneGap is able to use.

It that post I had this function:

function getPhoneGapPath() {
   var path = window.location.pathname;
   path = path.substr( path, path.length - 10 );
   return 'file://' + path;
};

There a first a slight error that I introduced. When finding the path name, I stripped out 10 characters. This was based on the test case being based on index.html. So if you happen to bring this function into another page with a different file name it would break. Rookie mistake. Actually more like too much prototyping and not enough ‘real’ coding…

Also we actually don’t need the entire path, so based on the platform we can locate our ‘root’ directory and go from there. Here is a revised version of the function:

function getPhoneGapPath() {
  var devicePlatform = device.platform;
  if (devicePlatform === "iOS") {
    path = "";
  } else if (devicePlatform === "Android" || devicePlatform === 'android') {
    path = "/android_asset/www/";
  }
return path;
};

Now two things to note here. 1) I am ignoring other platforms, so if you need to support one of the other platforms that PhoneGap does support, add in the proper if clause. 2) Every time this function is called, I query the device.platform. Now using your phone is actually a Transformer, this value is not going to change. I would recommend making this query once, say upon deviceReady() and storing the value in a variable and referencing it within this function. Also note that you will need to make sure you also include the device plugin in your PhoneGap app as well.