Brit Gardner

Tagged: flex RSS

• 

  britg 2:08 pm on September 2, 2008 Permalink | Log in to leave a Comment
  Tags: adobe, ajax, flash ( 4 ), flex, google chrome, javascript ( 14 )   

  Who Google Chrome Affects the Most: Adobe 

  I see a lot of coverage of the new browser out by Google – Chrome.  And rightly there should be – this is pretty exciting stuff!  Javascript running on it’s own thread per tab?  Sweet!

  I’ve also seen a lot of “Should Mozilla be pissed?” or “How will this affect Microsoft?” etc.  But I haven’t seen a lot of coverage on who I think is affected most by this move: Adobe.  Why?  Because the whole concept behid Chrome is to spead up web applications, namely Google’s style of web applications which all happen to be using AJAX instead of Flash.

  So, if Google has completely revamped it’s javascript engine in Chrome so that each tab operates javascript in it’s own thread, and you can run AJAX applications like google docs, gmail, etc. continuously without worrying about your browser bringing down your entire computer, we’re likely to see a renewed interest in AJAX as a platform.  Also, we’ll see a renewed effort from other browser vendors to make their javascript engines comparible.  This is all bad news for Adobe Flex/Flash.

  How are you, as a web developer, going to build that next business app?  Using Adobe’s Flex/Flash platform that requires users have a plugin installed (although most do) but has all the limitations of Adobe’s Flash plugin running in the browser?  Why would you when for most business applications, AJAX can meet all your needs AND be optimized to run as well as desktop applications?

  No matter what the outcome, it’ll definitely be fun to see how this plays out!

  Oh, and I’m writing this blog post through Chrome – it’s so new and shiny, go get it now!

  Update: Chrome doesn’t have to gain huge market share for this scenario to play out!

  Chrome is open source and hence their Javascript Engine is open source! (http://chromium.org) So, Chrome doesn’t have to make a huge dent in market share to make a huge dent in how the other browsers support javascript and AJAX apps.

  From limited testing over about 2-3 hours I could noticeably tell a difference in performance running Gmail, Google Docs, Google analytics, and google reader in separate tabs as opposed to doing this on firefox.

  This tells me that their javascript engine technology is superior to others out there – and since it is open source, I can imagine a scenario where other browsers, especially mozilla, adopt this engine.

  So, google chrome may never ever gain market share but I’m willing to bet their javascript technology will! This is what bodes poorly for Adobe in my opinion – a new browser market that isn’t dominated by Chrome per se, but is dominated by fast and multi-threaded javascript engines!

   

  Reply Cancel reply

  You must be logged in to post a comment.

• 

  britg 10:45 am on June 11, 2008 Permalink | Log in to leave a Comment
  Tags: actionscript 3, air, flex   

  Actionscript 3 AIR Application 

  I’m toying with the idea of distributing the Space Survivor game as an AIR application rather than embedded in the space survivor site (or concurrently with). Took me a while to find information about how to build an AIR app from just AS3 source, so I thought I’d share. Requires Flex Builder 3:

  • Create a new Flex Project and specify that it is a Desktop application

  

  • Follow your normal project-creation procedure
  • After the project is created, Make a new Actionscript file – name it whatever you want.  Make sure your Class extends Sprite or MovieClip.
  • Right click the newly created .as file and mark it as your default application:

  

  • Copy and past this, or write something similar in your main AS file:

  package
  {
  	import flash.display.NativeWindow;
  	import flash.display.NativeWindowInitOptions;
  	import flash.display.Shape;
  	import flash.display.Sprite;
  	import flash.display.StageScaleMode;
  
  	public class SpaceSurvivor extends Sprite
  	{
  		public function SpaceSurvivor()
  		{
  			var options:NativeWindowInitOptions = new NativeWindowInitOptions();
  			var mainWindow:NativeWindow = new NativeWindow(options);
  			mainWindow.activate();
  			mainWindow.title = "Space Survivor v0.0.1";
  			mainWindow.width = 1024;
  			mainWindow.height = 768;
  			mainWindow.stage.scaleMode = StageScaleMode.NO_SCALE;
  			var shp:Shape = new Shape();
  			shp.graphics.beginFill(0x0000FF);
  			shp.graphics.drawRect(0,0,100,100);
  			shp.graphics.endFill();
  			mainWindow.stage.addChild(shp);
  		}
  	}
  }

  • Finally, hit the Run or Debug button and voila!  You’re good to go.

  Also, look for more information here about petitioning Adobe to make a ‘Run as Desktop App’ an option for new Actionscript projects.