On Tue, Jan 29, 2013 at 8:55 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:
> > One thing I asked myself when I looked at your VanillaSDK code is why you > > checked in the JavaScript code of the framework classes (everything but > > Example.as). Aren't they written in AS3 and cross-compiled, too? At least > > that's how I thought you'd do it, even if this code is never compiled to > > run in the FlashPlayer or AIR. Take into account that you are intending > to > > implement a complete UI component framework, you wouldn't want to do that > > in JavaScript directly, would you? > > No, I don't. I will use the Closure Library on the JS side. Yes, I got that, but my proposition is to use the goog library *from AS* to create the wrapper code. That's what we do with Ext JS successfully. > I am not even going to implement a framework on the AS side. I use the Flex > SDK. The VanillaSDK JS framework is just a very thin wrapper around > these frameworks. Even if you only have to implement a thin wrapper, my experience is that this always becomes more code that you first expected. It would just be a better means to code JavaScript that stays completely "under the hood". Have a look at the "native JavaScript" thread, the idea would be to define a [Native] wrapper for goog and use that to implement component rendering and event transformation. Just think "there is no -spoon- JavaScript", only ActionScript... ;-) My 5 Cents -Frank-
