Presumably you could run OL with the -S option to get the JS 'assembley' and then run it through the closure compiler and compare that with the 'assembled' js code the OL compiler generates.
On 2011-12-13, at 18:43, Raju Bitter wrote: > The simple Flex app without Closure optimizations is 5mb in size, the > optimized version 2.5 mb. Wow! How much better off would OpenLaszlo be > with the Closure optimization... > > On Wed, Dec 14, 2011 at 12:40 AM, Raju Bitter > <[email protected]> wrote: >> Here's a video recording of the presentation: >> https://my.adobeconnect.com/_a295153/p7ysfeovw33/?launcher=false&fcsContent=true&pbMode=normal >> >> On Tue, Dec 13, 2011 at 5:29 PM, Raju Bitter >> <[email protected]> wrote: >>> The Spoon project team has posted some information in their blog on >>> the Flex Summit demos of FalconJS. Here are some interesting facts: >>> http://www.spoon.as/2011/flex-summit-live-updates/ >>> >>> + FalconJS will be donated as open source to Apache >>> >>> + FalconJS AS3 compilation: >>> AS code -> falcon front end / falcon js code gen -> google closure >>> compiler -> faster JS Code >>> Standards used: HTML, JS, SVG >>> >>> + “Falcon JS” refers to two experimental utilities: >>> – AS-> JS >>> – MXML -> HTML/CSS/JS >>> >>> + "Seeing example apps running. They look really good." >>> >>> That actually sounds promising. The DHTML code should be much more >>> optimized with Google Closure support, assuming that FalconJS supports >>> the advanced compilation mode. >>> >>> There will be some changes regarding tooling >>> – Flash Builder >>> — will release support for apache flex >>> — removing unpopular and expensive to maintain features: Design View, >>> DCD, and Catalyst workflows >>> – flash catalyst discontinued (with catalyst cs5.5 support for flex 4.5) >>> – monocle continues as a priority >>> >>> It sounds like the latest components are optimized for FalconJS >>> already, that means Adobe has done most of the work to have complex >>> apps running in JavaScript. >
