Currently Reading

Image of Derivatives Demystified: A Step-by-Step Guide to Forwards, Futures, Swaps and Options (The Wiley Finance Series)

Image of Working Effectively with Legacy Code (Robert C Martin)

Image of Coders at Work: Reflections on the Craft of Programming

Image of Succeeding with Agile: Software Development Using Scrum (Addison-Wesley Signature)

Recently Read

Image of Refactoring: Improving the Design of Existing Code (Object Technology Series)

Image of The Secrets of Consulting: A Guide to Giving and Getting Advice Successfully

Image of Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin)

Image of UML 2 for Dummies

Image of ActionScript 3.0 Design Patterns: Object Oriented Programming Techniques (Adobe Developer Library)

Image of Test Driven Development (The Addison-Wesley Signature Series)

Image of Cloud Atlas

Image of Test Driven: TDD and Acceptance TDD for Java Developers

Image of Beginning iPhone 3 Development: Exploring the iPhone SDK

Image of iPhone Advanced Projects (Books for Professionals by Professionals)


June 3, 2008

Canon Buzzwords goes Live!

Filed under: ActionScript, Flex, JavaScript — Anthony @ 10:28 am

The application went live on Friday lunchtime at http://www.canon-europe.com/buzzwordbuster in support of Canon's attendance at "DRUPA", the "World Cup" of Print Industry events!.

(The application is also available in German at http://www.canon.de/druck_glossar).

There were some interesting challenges presented with this application such as

  • Bilingual
  • Deeplinking ( without the use of JavaScript )
  • PureMVC Framework
  • Component Driven.

The problem with the Deeplinking was the fact that Canon uses a content management system that doesn't allow you to add any JavaScript to the Page! Not even as an include. This posed a big problem with the app due to the fact that Deeplinking was requirement of the brief. As you may or may not know Deeplinking is enabled in Flex via an external folder called history and within this folder you have history.js and history.css files both of which are needed to allow Deeplinking to work.

However, I was not allowed to "include" any JavaScript but i could use browser specific JavaScript as this is built into the browser and as such should run automatically so ::

if( ExternalInterface.available )
{
   var call : String    = 'window.location.href.toString'
   var url : String 	= ExternalInterface.call( call );
   var pos : int 	= url.indexOf( '#' );
   if( pos == -1 || pos == url.length - 1 )
   {
    	//No fragments so return;
       	return;
   }else{
        //Do Fragment Processing here;
   }
}

2 Comments »

  1. Hey,

    Is the data pulled from an XML document?

    By the way…good job.

    Comment by Max Dutton — October 8, 2008 @ 9:28 pm

  2. @Max
    Hi Max, yeah the data is loaded in from a seperate XML file and the application localization is also done using a secondary locations.XML file.

    Comment by Anthony — October 13, 2008 @ 11:18 pm

RSS feed for comments on this post. | TrackBack URI

Leave a comment

XHTML ( You can use these tags): <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> .