FOr what I understand falco js is still under development and there is just one resource on it so don't hope on it. Please correct me if I am wrong. Here there is a good solution if you want to use as to create js apps
http://www.jangaroo.net/home/ On 5 October 2012 14:53, sébastien Paturel <sebpatu.f...@gmail.com> wrote: > Following the HTML5 targetting discussion > is there any news about the FalconJS donation, as we now have Falcon > donated, it shoudl be next? > > > Le 05/10/2012 15:46, Charles Monteiro a écrit : > >> I'm wondering if most in this group are more interested about targeting >> html5 than air because it seems to me it would be hard to do both well. >> >> I want to run on AIR. >> On Oct 5, 2012 9:38 AM, "sébastien Paturel" <sebpatu.f...@gmail.com> >> wrote: >> >> I agree with others that you should abandone the idea that Adobe could >>> get >>> Catalyst back from the dead. >>> They have been pretty clear about it, and the open sourcing is not an >>> option because of code dependencies. >>> >>> Your only chance to see catalyst come back from Adobe, is to make Apache >>> Flex te best framework for HTML5 runtime! >>> >>> >>> Le 04/10/2012 00:48, Sebastian Mohr a écrit : >>> >>> @christofer dutz ... thanks for sharing your thoughts. +1 from my side! >>>> Flash Catalyst CS5.5 is a charm for interaction designers like me. >>>> >>>> >>>> Sincerely Yours, >>>> >>>> Sebastian Mohr >>>> Apache Flex Developer (PPMC), >>>> Interaction Designer & Musician >>>> http://www.linkedin.com/in/****masuland<http://www.linkedin.com/in/**masuland> >>>> <http://www.linkedin.**com/in/masuland<http://www.linkedin.com/in/masuland> >>>> > >>>> >>>> >>>> >>>> >>>> On Oct 3, 2012, at 7:21 PM, christofer.d...@c-ware.de wrote: >>>> >>>> Well isn't it usually that way around? >>>> >>>>> I create some general UI scetches using some tools like blamiq mockups >>>>> and deal with negoitating the functionallity with my customers. As >>>>> soon as >>>>> the component works as desired I go "pimp my app" and give it to a >>>>> designer >>>>> to have it pimped. >>>>> >>>>> Using Catalyst this was really easy (As soon as you had a desiger at >>>>> hand that was used to it and it's concepts). I was even able to let the >>>>> designer skin a running application deployed by me somewhere on the >>>>> web, so >>>>> I didn't have give away the code of the application itself or setup the >>>>> environment at the designers office. This workflow was the major >>>>> breakthrough for me and was one of the major things that made me shift >>>>> allmost entirely to the Flex road. >>>>> >>>>> It's a real pitty to have it dropped and wasted :-( >>>>> >>>>> >>>>> -----Ursprüngliche Nachricht----- >>>>> Von: Alex Harui [mailto:aha...@adobe.com] >>>>> Gesendet: Mittwoch, 3. Oktober 2012 18:18 >>>>> An: flex-dev@incubator.apache.org >>>>> Betreff: Re: AW: Financing the Design View AIR App (Was: Re: Design >>>>> View >>>>> AIR App) >>>>> >>>>> >>>>> >>>>> >>>>> On 10/3/12 7:38 AM, "christofer.d...@c-ware.de" < >>>>> christofer.d...@c-ware.de> >>>>> wrote: >>>>> >>>>> Oh ... let me thow in a little more weight for the Catalyst ;-) >>>>> >>>>>> I invested quite some time in setting up a project structure that >>>>>> allowed me to concentrate on developing (Using an ugly but functional >>>>>> developer Skin) and having professional Designers use Catalyst to Skin >>>>>> the application. >>>>>> Unfortunately it seemed that the designers available on the market >>>>>> were all even less "finished" than the Catalyst project, but as soon >>>>>> as the designers got the hang of it, the results were pretty >>>>>> sattisfying and I had what I was allways dreaming about: Being able to >>>>>> concentrate on the functionality and have a designer do all the stuff >>>>>> that sells the application (cool buttons, even greater effects and >>>>>> animated transitions, ...) :-) >>>>>> >>>>>> I would be really happy if Adobe didn't entirely drop this tool, and >>>>>> if they did, If they would somehow open-source it. >>>>>> >>>>>> It is essentially "dropped". See [1]. There are no plans to >>>>>> >>>>> opensource >>>>> it. It too had a lot of "baggage" that made it difficult to implement. >>>>> For example, it really wasn't extensible as to what components it >>>>> could >>>>> handle. >>>>> >>>>> The principle behind it (that you can take designer art and break it >>>>> down into components) is compelling, but I question whether it remains >>>>> valid in a world of dynamic UI. >>>>> >>>>> It is also interesting to note that you used it in completely different >>>>> way than it was intended. It was for a design-first-then-develop >>>>> workflow >>>>> and you did it the other way (which is what I do when I have a choice >>>>> as >>>>> well). >>>>> >>>>> [1] >>>>> http://www.adobe.com/devnet/****flex/whitepapers/roadmap.html<http://www.adobe.com/devnet/**flex/whitepapers/roadmap.html> >>>>> <**http://www.adobe.com/devnet/**flex/whitepapers/roadmap.html<http://www.adobe.com/devnet/flex/whitepapers/roadmap.html> >>>>> > >>>>> -- >>>>> Alex Harui >>>>> Flex SDK Team >>>>> Adobe Systems, Inc. >>>>> http://blogs.adobe.com/aharui >>>>> >>>>> >>>>> >
