On 3/31/13 12:36 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> Ok, I agree on the minimalist approach very much, but that doesn't
> exclude the use of a large library (sounds silly, but read on).
>
> On the merits of using 'goog' events: Gmail, Google Plus, Google Drive
> etc. This is a cross-platform, cross-browser, tremendously tested and
> proofed implementation. It drives some of what maybe the most used
> online applications. I'll take that over a "roll your own" solution
> any day. And it's there for us to use, since we already require (pun
> intended) the Closure Library.
But one could use the same argument to say we should start with Jquery.
>
> As to the code bloat: looking at the file sizes in the events
> directory is plain silly. That only goes for the 'intermediate/debug'
> release anyway, where size and speed play second fiddle to readability
> and ease of debugging. For the release we use (in both FalconJS and
> FalconJx) the Google Closure Compiler in advanced mode. This is a true
> compiler. The resulting output of that compiler only contains classes
> and methods that are actually used by the code, unlike what minifiers
> do, those include all the code, just reworked to remove whitespace and
> refactored to replace long names.
>
> I will build a FlexJS branch where I use the closure events so we can compare.
That would be great. And like I said, maybe as I try to get IE8 working
I'll realize why the Google version has what it has. For me, no matter who
else is using it and how well tested it is, I want to know what is in it and
that we aren't taking more than we need.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
