pdf417 barcode generator javascript // Transform Listeners in Java

Generate PDF417 in Java // Transform Listeners

this.addEventListener(TransformGestureEvent.GESTURE_ZOOM, eventHandler); this.addEventListener(TransformGestureEvent.GESTURE_SWIPE, eventHandler); this.addEventListener(TransformGestureEvent.GESTURE_PAN, eventHandler); this.addEventListener(TransformGestureEvent.GESTURE_ROTATE, eventHandler);

// Touch Listeners this.addEventListener(TouchEvent.TOUCH_BEGIN, eventHandler); this.addEventListener(TouchEvent.TOUCH_END, eventHandler); this.addEventListener(TouchEvent.TOUCH_MOVE, eventHandler); this.addEventListener(TouchEvent.TOUCH_OUT, eventHandler); this.addEventListener(TouchEvent.TOUCH_OVER, eventHandler); this.addEventListener(TouchEvent.TOUCH_ROLL_OUT, eventHandler); this.addEventListener(TouchEvent.TOUCH_ROLL_OVER, eventHandler); this.addEventListener(TouchEvent.TOUCH_TAP, eventHandler);

} protected function eventHandler(event:TouchEvent) : void { trace( event.toString() ); } ]]> </fx:Script> </s:WindowedApplication>

One of the biggest complaints about AIR applications is that they consume too much CPU memory and have large runtime sizes. It is encouraging to see that in AIR 2.0, Adobe s team put effort into increasing optimization and decreasing resources used by the AIR application:

File improvement: Smaller runtime size and CPU/memory improvements. WebKit upgrade: WebKit HTML-rendering engine was updated to an optimized version. Native Linux installed: Linux installer available as native .deb and .rpm installer. AIR will be available for Linux 64bits.

AIR applications have been judged by many to consume too many resources from the machine they are installed on. In AIR 2.0, Adobe put extra effort into decreasing the runtime size and into decreasing the CPU/memory consumed by an AIR application. In fact, you have tested a simple application that includes a text field and noticed a decrease in resources used. Look at the results in Table 5-2 of a sample application you ran as a test.

WebKit (http://webkit.org/) is an open-source browser that has been available since AIR 1.0. The WebKit engine renders HTML and executes JavaScript. WebKit is the engine that drives Safari, claimed by Apple and others to be the fastest browser. Adobe AIR 2.0 uses the same branch of WebKit as the Safari 4 beta: http://trac.webkit.org/browser/releases/Apple/Safari%204%20Public%20Beta. The most significant feature of using this branch of WebKit is the usage of SquirrelFish Extreme (SFX), which has been integrated into the WebKit engine and increases the overall performance of WebKit (see Figure 5-10).

Figure 5-10. WebKit s vs. JavaScript s performance in different versions as provided by WebKit.org Using a newer branch of WebKit provides faster performance and additional functionality.

SquirrelFish Extreme: The new WebKit engine resulting in faster performance. According to SunSpider, the performance is more than double the speed as compared to the regular SquirrelFish. The reason SFX is faster is mainly due to bytecode optimizations, polymorphic inline caching, a lightweight JIT compiler, and an expression engine that uses the JIT infrastructure. See www.satine.org/archives/2008/09/19/squirrelfish-extremefastest-javascript-engine-yet/. CSS transitions: WebKit added built-in animations using CSS. By describing how to animate from an old value to a new value over time, you can create animations. CSS transformations: Transformations, via the -webkit-transform property, allows you to scale, rotate, and skew blocks of elements.

CSS animations: Animation that uses the -webkit-transition tag and lets you set timings for fades, rotation, expansion, collapses, and others. CSS gradients: You can create gradients in CSS. There are two types of gradients: linear gradients and radial gradients. The syntax is as follows: -webkit-gradient(<type>, <point> [, <radius>] , <point> [, <radius>] [, <stop>]*). WebKit CSS selectors: You can access the DOM faster and easier using the Selectors API. It allows you to select elements within a document using CSS.

WebKit is embedded into AIR and lets you create HTML/JS/PDF objects and render them as Flash objects. You can then manipulate these objects just like any other object in Flex. Take a look at a simple application that uses the HTML tag and displays HTML content.

< xml version="1.0" encoding="utf-8" > <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" width="800" height="600"> <mx:HTML id="htmlObject" location="http://google.com" width="400" height="400" x="126" y="404" rotation="280"/> </s:WindowedApplication>

Take a look at the following example using the same HTML component, which allows you to test some of the new WebKit functionality:

< xml version="1.0" encoding="utf-8" > <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" width="800" height="600" initialize="initializeHandler(event)"> <fx:Script> <![CDATA[ import flash.utils.Timer; import mx.core.UIComponent; import flash.events.Event; import mx.controls.HTML; import mx.events.FlexEvent;

private var htmlTransitions:XML = <html> <div onmouseover="this.style.opacity = 0;" onmouseout="this.style.opacity=1" style="-webkit-transition: opacity 1s linear; background-color: #efefef; border:5px solid black;"> CSS Transitions Example </div> </html>;

private var html:HTML; private var timer:Timer = new Timer(1, 10000); protected function initializeHandler(event:FlexEvent):void { html = new HTML(); html.width = 400; html.height = 400; html.addEventListener( Event.COMPLETE, onComplete ); component.addChild( html ); } private function loadHTMLCode(htmlText:XML):void { timer.start(); html.htmlText = htmlText; } private function loadHTMLPage(location:String):void { timer.start(); html.location = location; } private function onComplete(event:Event):void { trace("page loaded after: "); label.text = "HTML code executed in " + this.timer.currentCount + " seconds"; timer = new Timer(1, 10000); } ]]> </fx:Script> <fx:Declarations> <s:RadioButtonGroup id="radiogroup"/> </fx:Declarations> <mx:UIComponent id="component" width="400" height="400" x="10" y="42"/>

<s:RadioButton x="10" y="10" label="Transitions" groupName="radiogroup" click="loadHTMLCode(htmlTransitions);"/> <s:RadioButton x="103" y="10" label="Animations" groupName="radiogroup" click="loadHTMLPage('asset/Animation.html')"/> <s:RadioButton x="275" y="10" label="Gradient" groupName="radiogroup" click="loadHTMLPage('asset/Gradient.html')"/> <s:RadioButton x="193" y="10" label="Transform" groupName="radiogroup" click="loadHTMLPage('asset/Transform.html')"/> <s:RadioButton x="353" y="10" label="Selectors" groupName="radiogroup" click="loadHTMLPage('asset/Selectors.html')"/> <mx:Label id="label" x="9" y="450" width="374"/>