Archive for the 'Adobe' Category

New: Flex on Google App Engine - proof of concept and source code

I just updated The GAE SWF Project to add the proof-of-concept Google App Engine Flex 3 client. The source code download now includes the source code for the Flex project.

The Flex client works exactly like the Flash 9 client and shares an almost identical codebase. 99% of the framework is the same.

I'm going to document that differences, etc., but it's past 1am at the moment and I need to sleep!

OSFlash Job Board relaunch: Flash, Flex, and ActionScript job listings at half price

Do you have a Flash, Flex, or ActionScript job to post? Post it on the OSFlash Job Board.

I've just relaunched the OSFlash Job Board and all jobs listings are 50% off this week if you use the coupon code RELAUNCH. This expires on April 1st, 2008 (no joke!) :)

If you want to get notified of new jobs, you can get job alerts by email or subscribe to the RSS feed.

The OSFlash Job Board initially launched last year using the Joard system that my friend and business partner Dave Stone was developing. Dave decided to discontinue Joard at the start of this year so we were left without a job board.

It has taken a little while to get everything set up again but the job board is now back up and running using the excellent JobThread system.

OSFlash gets over 120,000 unique visitors every month. We also have a new job board widget that is featured on the OSFlash.org home page and here on my blog (I get around 70,000 unique visitors a month on this blog). By putting your job listing on the OSFlash Job Board, you'll thus be reaching a very tightly-focussed group of close to 200,000 Flash, Flex, and ActionScript developers, designers, and creatives.

Check out the OSFlash Job Board for Flash jobs, Flex jobs, and ActionScript jobs and don't forget to use the RELAUNCH coupon code to get 50% off your job listing until April 1st, 2008.

If you want to help support OSFlash, tell your friends about the OSFlash Job Board by adding the OSFlash Job Board widget to your site.

OSFlash Job Board Widget (JavaScript)

<script type="text/javascript">
<!-- 
var jobthread_jobroll_title = "Jobs";
var jobthread_jobroll_outer_style = "background-color:#dddddd;border:1px solid #999999;width:160px;";
var jobthread_jobroll_inner_style = "background-color:#ffffff;color:#666666;border:1px solid #999999;margin-left:10px;margin-right:10px;padding:10px 10px 2px 8px;font:11px Arial, Helvetica, Sans-serif;line-height:16px;";
var jobthread_jobroll_title_style = "color:#313131;font-weight:bold;";
var jobthread_jobroll_link_style = "color:#0464bb;font-size:11px;font-weight:bold;text-decoration:none;border:none;";
var jobthread_jobroll_featured_style = "";
var jobthread_jobroll_featured_link_style = "";
var jobthread_jobroll_top_style = "padding-top:8px;";
var jobthread_jobroll_bottom_style = "padding-bottom:4px;";
//-->
</script>
<script type="text/javascript" src="http://jobs.osflash.org/feeds/jobroll/?num_jobs=5&num_featured_jobs=1&display_method=default&version=2.0"></script>

OSFlash Job Board Wordpress widget

I also made a simple Wordpress Widget that you can use to add the Job Board to your Wordpress blog's sidebar. Download the OSFlash Job Board Wordpress widget.

Once you've downloaded it, simply extract it into your wp-content/plugins folder, activate it, and add it to your sidebar from the Widgets section of the Wordpress administration tool. (Note: The CSS positioning is set for my site, you may need to modify it to make it display correctly for yours.)

Here's the source for the OSFlash Job Board Wordpress plugin. It's released under the open source MIT license, so please feel free to use and adapt it to make your own Wordpress plugins too.

<?php
/*
Plugin Name: OSFlash Job Board Badge
Plugin URI: http://aralbalkan.com
Description: Displays the OSFlash Job Board Badge on your Wordpress blog. Released under the MIT License. Copyright (c) 2008 Aral Balkan. http://aralbalkan.com.
Author: Aral Balkan
Version: 1.0
Author URI: http://aralbalkan.com
*/
 
function osflash_job_board_widget_init()
{
	if ( !function_exists('register_sidebar_widget') || !function_exists('register_widget_control') )
		return; 
 
	function osflash_job_board_widget($args)
	{
		extract($args); 
 
		echo $before_widget; 
 
		?>
<div class="osflashJobBoard">
				<script type="text/javascript">
				<!-- 
				var jobthread_jobroll_title = "Jobs";
				var jobthread_jobroll_outer_style = "background-color:#dddddd;border:1px solid #999999;width:160px;";
				var jobthread_jobroll_inner_style = "background-color:#ffffff;color:#666666;border:1px solid #999999;margin-left:10px;margin-right:10px;padding:10px 10px 2px 8px;font:11px Arial, Helvetica, Sans-serif;line-height:16px;";
				var jobthread_jobroll_title_style = "color:#313131;font-weight:bold;";
				var jobthread_jobroll_link_style = "color:#0464bb;font-size:11px;font-weight:bold;text-decoration:none;border:none;";
				var jobthread_jobroll_featured_style = "";
				var jobthread_jobroll_featured_link_style = "";
				var jobthread_jobroll_top_style = "padding-top:8px;";
				var jobthread_jobroll_bottom_style = "padding-bottom:4px;";
				//-->
				</script>
				<script type="text/javascript" src="http://jobs.osflash.org/feeds/jobroll/?num_jobs=5&num_featured_jobs=1&display_method=default&version=2.0"></script>
			</div>
 
		<?php
 
		echo $after_widget;
	}
 
	// Register widget
	register_sidebar_widget('OSFlash Job Board', 'osflash_job_board_widget');
}
 
function osflash_job_board_style()
{
	?>	
<style type="text/css">
		.osflashJobBoard
		{
			position: absolute;
			left: 20px;
		}
		</style>
 
	<?
}
 
// Add widget once plugins are loaded.
add_action('plugins_loaded', 'osflash_job_board_widget_init');
 
// Add the badge's CSS to the head.
add_action('wp_head', 'osflash_job_board_style');
 
?>

Update: There was a small hiccup right after the blog announcement. If you couldn't reach OSFlash.org or jobs.osflash.org, please try again. It's back up and running! Thanks!

Adobe building Flash Player for iPhone

Finally, some concrete news on the Flash Player for iPhone front: according to the Wall Street Journal, Adobe CEO Shantanu Narayen announced in a conference call to investors that Adobe has begun work on a Flash Player that is suitable for the Apple iPhone.

It looks like Adobe is building the "product in the middle" that Steve Jobs is looking for. Let's hope Apple cooperates by adding the Flash Player to Safari on the iPhone.

This is a good move by Adobe. At the very least, they'll be able to say, "look, here's the Flash Player for iPhone, now it's up to Apple whether they include it in Safari or not." If Apple doesn't then it will end up looking bad as it willfully contradicts its own promise to deliver a non-watered down version of the Internet on the iPhone.

Via: ericd via AppleInsider via WSJ.

Astro and Diesel sneak peeks at FITC Amsterdam - Updated

In my haste to put up the video and run to present my session, I apparently placed the wrong video up. Oops! Sorry. Here's the right one.

Adobe keynote at FITC Amsterdam

(I live-blogged this during the keynote; there may be typos, inaccuracies, etc. It has not been proof-read.)

Mike Downey takes the stage.

Mike's going to show us some sneak peeks today that haven't been shown before.

Adobe released Flex 3 and AIR a few hours ago and Mike's kicking off the keynote with a history of AIR.

AIR allows web developers to use existing technologies (HTML, AJAX, Flash, and Flex) to build desktop applications.

(Mike's showing us examples of AIR applications - you can find AIR showcase applications on Adobe.com.)

One of the examples is Analytics Reporting Suite for Google Analytics. It uses Flex and the charting components to display data from Google Analytics and output PDFs, etc.

There's going to a be a dot release of AIR later this year. And they want to frequently update the AIR runtime.

(Serge Jespers has taken the stage and is showing us Flex Builder 3, which also just shipped.)

Serge shows us how you can easily skin Flex components using Photoshop. He creates the various states of a button component in Photoshop (he could also have used Flash, Illustrator, or Fireworks) on different layers using a naming convention and then uses the Import Art feature in Flex Builder 3 to import the PSD and automatically skin the button component.

Next, using the Flex Component Kit for Flash CS3, he is making a Flex component from a Flash movie clip. After creating the Flex component (SWC), he adds it to his project's Library in Flex Builder and he can now use the component just like any other Flex component.

(You can download the The Flex Component Kit for Flash CS3 from the Adobe Exchange.)

Finally, he's showing the Create Application from Database example (basically, scaffolding for Flex) using a simple MySQL database and PHP.

(This is very cool and is the sort of generic server-side support that was previously lacking in Flex Builder.)

And finally, finally ("do we have time for one more?") he is showing us the Export Release Build feature for reducing the size of your Flex applications (Flex Builder now creates a debug version by default). This reduces the size of the SWF from 370K to 270K when the debug code is removed.

Next, he creates a new Module of one of the panels and then loading it in at runtime. He uses the new ModuleLoader tag to load in the new module. The original file is now reduced to 163K.

And finally, he is demonstrating the Flex framework caching feature. You can create a runtime shared library for the Flex Framework. The framework is then not included in your application's SWF but loading in dynamically at runtime. This brings down the size of the SWF to 50K. (And the Flex framework is cached so if a user has been to any Flex application before, it won't be loaded again.)

(Mike's back on stage.)

Flash Player 9 penetration is now on 98% of all machines (and it got there faster than any other piece of software ever; it was released in December 2007).

Mike's giving us an overview of the latest Flash 9 Player update (Movie Star) and the new FMS 3 and FMIS3 servers.

Richard Galvan takes the stage. He's the Flash Product Manager. He's going to show sneak peeks for Astro and Diesel.

(OK, I recorded the sneaks using Seesmic. I'm going to embed the video in the next blog post.)

I'm running off to present my own session in a few minutes.

SWX Jobs

Intercasting Corp swx job

Intercasting Corporation has a job opening for a Flash/Flash Lite Handset Developer and they list knowledge of SWX as a nice-to-have skill on the job description. Another OSFlash project, Red5, is also listed in the same section.

It's really cool to see development houses adopting SWX for Flash and Flash Lite development. If you have any relevant job openings that you want to advertise, please feel free to contact me via the comments or send an email to the SWX mailing list.

There's also a Flash and Flex job board on OSFlash if you want to reach a more targeted audience of open source Flash developers.

Also, if you're making things with SWX and want to get exposure for them, feel free to leave a link at the SWX Showcase and I will feature them there.

Thanks go to Alex Tur of Sonopia for bringing this to my attention. Thanks, man!

SWX PHP and SWX AS now support Flash 6+

I just tested the SWX SWFs being generated by the SWX PHP gateway and I'm happy to report that they work perfectly well in Flash 6 projects. This means that you can use SWX RPC on the following platforms in addition to the existing ones:

  • Sony PSP with Firmware 2.7 or greater.
  • Nokia N770 Internet Tablet.
  • Microsoft Pocket PC 2003 devices.

If you want to use SWX AS (the SWX ActionScript libraries) in Flash 6 projects ahead of the upcoming SWX PHP RC1 release, please check out the latest version from SVN (http://svn1.cvsdude.com/osflash/swx/trunk/).

I want to thank Hayden Porter for emailing me to ask about Flash 6 support in SWX and for providing the list of devices that currently run Flash 6.

I’m speaking at MAX? WTF?

Aral Speaks at max Pigs Flying

Yes, it's true, I'm speaking at MAX 2007 this year. But why, after being so vocally against their policies in the past? Simple. Because Adobe listened and they're making an effort to change, starting with the MAX conferences this year.

My criticism of MAX in the past centered around three things:

  1. They didn't pay speaker's expenses.
  2. You couldn't choose your own topic to present.
  3. It felt too much like a sales event that ignored the community.

This year, I'm happy to say, they've addressed all three of my concerns.

To qualify the first point a little further, it's important to realize that there are two types of speakers at events like these: Corporate and community.

Corporate speakers are there to evangelize their products. They may be Adobe Evangelists or evangelists from partner companies. Their sessions are usually product-based and showcase their latest and greatest features. When done right, i.e., when the speaker doesn't come off like a used car salesman, I personally find these sessions very valuable. I attended a couple such sessions during Adobe Live and learned quite a few things about the latest version of Photoshop.

Community speakers, on the other hand, are a very different group. They're not there to sell you a product but to share their experiences, knowledge, and, hopefully, inspire you. I remember how sessions by Branden and Joshua at the very first Flashforward conference I attended ages ago inspired me to learn more about Flash and get involved with the Flash community. A single inspirational session by a great speaker can easily make attending a conference worthwhile for me. In recent times, I've attended just such amazing sessions by Ze Frank, John Maeda, Jeremy Keith, Mario Klingemann, Brendan Dawes, Erik Natzke, Seb Lee Delisle, John Grden and Chris Allen, Keith Peters, Chris Orwig, and others. These are the sessions that energize me, widen my horizons, and inspire me to create things. In other words, they're invaluable.

One major difference between corporate and community speakers is that while corporate speakers are on company time when presenting at these events, earning their salaries and expensing their accounts, community speakers (for the most part) are not (some community speakers do work for companies like Yahoo! and Google who do pay their expenses, which is fair enough). One of my major beefs with MAX in the past was that it wouldn't pay for community speaker's expenses. This year, things have begun to change in this area and they are covering expenses for a select group of community speakers, including myself. I see this as a very positive step forward.

To put this into perspective, Adobe is a billion dollar company and yet they're listening to community feedback. As a comparison, Apple doesn't pay speakers to present at MacWorld. Do you think any amount of criticism by the community would get them to listen and change their policy on this? (The most I would expect is a fanboy response stating "Apple doesn't owe you anything!") *ducks* :)

The other issue I had with MAX was that you were pretty much asked to speak on a given topic and present the same (often product-related) session several times. In other words, it felt like you were being employed to be a corporate speaker when, in fact, you weren't even being employed. This year, with the "inspire" line of sessions, that's changing too. I'm going to be presenting the latest version of my Rediscovering Fun session and talking about SWX. At MAX. That rocks! :)

This year's MAX is going to be the first one that embraces the amazing community Adobe has around its products and all I can say is, it was about time! I believe that Adobe is finally realizing that the Flash community is far more than a loose conglomeration tied together by commercial interests: It's a living, breathing, passionate family of designers and developers who truly love working on this amazing platform. Among other things, it feels like Adobe has finally begun to realize that this community is one of the things that sets it apart from the purely corporate, follow-the-bucks community that Microsoft has. (Microsoft does an amazing job of building an economy around its products but the monetary incentive is almost entirely the only thing that binds people to it -- not so with the Flash community.)

So is this a clever short-term PR move on Adobe's part or are they truly committed to involving the community in MAX and other Adobe events? There are several strong indicators I've seen that point to the latter.

Firstly, Adobe must be aware of the wonderful feedback Adobe Live Amsterdam got for its Developer Track this year. I was personally floored by the positive feedback my sessions got and I know that the other developer sessions were held in similarly high esteem. At about the same time, Adobe Live in the UK, with an expanded designer and developer track, also got very favorable reviews. The message from this is clear: Involving the community in these events is a winning formula.

Secondly, my good friend Ted Patrick has been tasked with heading up preparations for MAX this year. Ted is one my oldest Flash buddies and has been in the Flash community for as long as I can remember. He's a Flash developer that I both admire and respect and, most importantly, coming from the community, he understands the community. Putting Ted in charge of MAX is a clear signal from Adobe that they want MAX to have a much stronger community focus.

Personally, I am very excited about MAX this year and I want to thank my friends at Adobe for listening and for taking those most important first steps towards changing things.

Here's to the best MAX conferences ever in Chicago, Barcelona and Japan! (I'm especially looking forward to Japan as it will be my first time there and I've been dying to go for ages!) :)

Bug and workaround for Adobe Acrobat Connect (Breeze) Add-In on MacBook Pro/OS X

There is a bug with Adobe Acrobat Connect that bit me really badly today, just before the OSFlash conference. Basically, it seemed as if the Add-Ins were installed correctly (in Safari and Firefox) but they wouldn't work. I couldn't share my screen or upload documents. And yet I wasn't getting any errors and the troubleshooting application was giving me a green light.

Thankfully, I found two forum threads (here and here) that led me in the right direction with only half an hour to go. Based on the information there, I tracked down the folder that Acrobat Connect installs the Add-In to:

~/Library/Preferences/Macromedia/Flash Player/www.macromedia.com/bin/connectaddin6X0

Unfortunately, what Acrobat Connect did was install the wrong version of the Add-In. Instead of the OS X version, it installed the OS 9 version. To make matters worse, because the Add-In does physically exist in the right folder, Acrobat Connect thinks it is installed correctly but when it tries to load it, OS X won't load it. The symptom is that you get a small white pop-up screen that says "Loading Adobe Acrobat Connect" that then silently disappears.

The workaround is to replace the contents of that folder with the actual OS X Add-In.

Thankfully, with ten minutes to go for the keynote, I realized that this was the issue and Ralph kindly sent me his files. Copying the correct files into that folder immediately solved the issue (no restart of the browser or even the Connect session required.)

If you're having the same issue, download the OS X version of the Adobe Acrobat Connect Add-In here. Unzip and place the files there in the folder specified above and that should solve your problem.

I hope that this helps. Until I figured this out, I rebooted (twice), cleared all Flash player preferences, reinstalled Firefox and had three heart attacks! Oh yes, and things started working with only 5 minutes to go for the keynote! Talk about cutting it close!

Great news: Adobe Open Sources Flex

I had a lovely surprise when woke up a few moments ago and read the OSFlash mailing list this morning: There was an email from Mike Chambers announcing that Adobe intends to release Flex as open source under the MPL license. This follows hot on the heals of Adobe releasing the the ActionScript Virtual Machine to the Mozilla Foundation under the Tamarin project.

What a great move! I love you guys!

This is exactly the right move Adobe needed to make to compete with Microsoft and guarantee the longevity of the platform and a healthy future for Flash/Flex developers. I want to thank Adobe for looking past immediate-term profit and having the foresight to make such an intelligent, long-term decision. It's not always easy when you have shareholders to appease with quarter-on-quarter growth figures.

Adobe has a press release and FAQ regarding the announcement that detail Adobe's intentions, including which parts of Flex will be open sourced. Currently, Adobe will be releasing as open source, "all of the components of the Flex SDK needed to create Flex applications, including the Java source code for the ActionScript and MXML compilers, the ActionScript debugger, and the ActionScript libraries that make up the core Flex framework."

As a potential limitation, the FAQ does state that "due to restrictions on some components that have been licensed from third parties or come from other Adobe products, some portions of the current free Flex 2 SDK may be made available in binary form only."

Flex Builder will not be released as open source. (And that's all right -- it's the SDK and compilers that are important.) According to Matt Chotin from Adobe, the source for Flex Charts will also remain closed (although you do receive the source if you purchase it.)

So when will Flex be open sourced? According to the press release:

Starting this summer with the pre-release versions of the next release of the Flex product line, code named “Moxie,” Adobe will post daily software builds of the Flex SDK on a public download site with a public bug database. The release of open source Flex under the MPL will occur in conjunction with the final release of Moxie, currently scheduled for the second half of 2007.

Matt Chotin also confirmed, in response to a question by Robin Hilliard, that it is their intention to start releasing daily builds from June and that SVN access will probably not be available until December, or "before the release of Flex 3".

If you want to learn more and get involved, take a look at Adobe's Flex Open Source Google Talk group.






Bad Behavior has blocked 0 access attempts in the last 7 days.