But if I understand it correctly, wouldn't it mean in Erik's model that when I create my own custom datagrid component for instance, I would also have to write a JS version for this? (For me personally this is what I would want to avoid -- writing JS myself :) )
Does anybody know what GWT is doing excactly and how the current paths we (the flexers) have choosen compare to that? To me it seems pretty nice in GWT to be writing your own HTML, and just plug in your java (which then cross compiles). Do you guys think this a good model? (I'm not saying we should this or that, and that i think somebody is choosing the wrong path right now. I think all of you guys are doing an amazing job, and I wouldn't be able to do anything similar myself. Just trying to make some discussion and gather info, because I think that is healthy, at all times) And nice Job Erik, looking forward to experiment with it!! On 25 Jan 2013, at 20:13, Alex Harui <aha...@adobe.com> wrote: > > > > On 1/25/13 11:00 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > >> 2) Actually, I have the AS implementation completely finished... it's >> the Flex SDK (hence the 'vanilla' in the name). On the browser side >> I'll have to create a JS framework that has the same public API as the >> Flex SDK, but I never said that behind that API would be a translation >> of any unused code from the Flex SDK (would be silly, wouldn't it?), >> nor will it necessarily use the same intertwined dependencies. > OK, I'll believe you, but one of the problems in the current Flex SDK is > interwined dependencies caused by the use of complex classes in the API > surface itself. I'm not clear how you can fix that without changing the API > surface. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
