incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael A. Labriola" <labri...@digitalprimates.net>
Subject RE: Randori framework [was Re: What to expect from FalconJS]
Date Sat, 17 Nov 2012 19:50:45 GMT
>What I don't get is, Mike said all these other companies that had compiler engineers are
not here, meaning they are somewhere else. So Mike has put his time working with C# and a
cross compiler /JS framework.

Actually, I found a really good cross-compiler from C# to JS that was extensible. So, instead
of inventing the wheel to do a POC, I used something off the shelf. If FalconJS was here and
extensible, I would have built it on top of that first.

>Mike Does this have anything to do with this project? Or are you planning on heading in
your own direction with the Randori framework?

I think there are some borders and it will really depend on this group and what we all want
to do. Randori isn’t really just about C#, it's more of an idea that we could do with Java/C#/AS/Whatever.
I could see Flex being a component framework that follows a strategy and exists in the space
to all a familiar development paradigm. I just don’t want to make the same mistakes that
I think we have with Flex now.

>BTW Mike, I really do agree with how you summarized the problems that are occurring today
with Javascript and the View layer.

Thanks,

Mike

Quoting Joan Llenas Masó <joan@garnetworks.com>:

> I think I'm able to get your point after watching these slides and 
> mixing it together with what you mentioned earlier on in another thread.
> So instead of going through direct UI AS3->{MyOutputTargetOfChioce} 
> translation we just concentrate our efforts in the business logic code 
> translation AS3->{MyOutputTargetOfChioce}.
> The views on the other hand are implemented natively in the language 
> of choice, being it AS3, JS or whatever.
> Finally MXML comes to rescue giving us the power of componetization 
> and view declaration.
> This way we can implement same set of components for different output 
> targets but declare them in the same way.
> FalconJS will take care of the rest.
>
> Am I right? or did I make my own movie...
>
> Anyway, I see maaaaany advantages here. Wow, I love it. This is 
> actually the essence of Flex taken to the next level :) Well, I see 
> Haxe fitting here as well. Actually we could plug many packaging tools 
> in the FlaconJS "output port".
>
> Can't wait to see more!
>
> Cheers!
>
>
> On Sat, Nov 17, 2012 at 4:57 AM, Alex Harui <aharui@adobe.com> wrote:
>
>> >
>> >>  In the meantime, make sure you look at the slide deck from 
>> >> Michael Labriola¹s 360Min presentation on how he is developing apps for
HTML.
>>  I¹m
>> >> sure he¹ll reply with the link
>> >
>> > Is the slidedeck already pulished somewhere?
>> >
>>
>> http://www.slideshare.net/michael.labriola/randori-design-goals-and-j
>> ustific
>> ation
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>

--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com

Mime
View raw message