Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 965DDD0DB for ; Fri, 5 Oct 2012 13:54:04 +0000 (UTC) Received: (qmail 4332 invoked by uid 500); 5 Oct 2012 13:54:03 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 4298 invoked by uid 500); 5 Oct 2012 13:54:03 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 4290 invoked by uid 99); 5 Oct 2012 13:54:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 13:54:03 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebpatu.flex@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-ee0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 13:53:56 +0000 Received: by mail-ee0-f47.google.com with SMTP id t10so1245252eei.6 for ; Fri, 05 Oct 2012 06:53:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Y777BGqGOXhj7Q/CRowdfcKAmWSSxzHinx2gSTOFwt4=; b=X60JN4+8uQ0SDxZcYr8ZD9TNA1l2vRfcnc8aXVcZq5acoFyb4KSEh5eKkGKXyI2B+P 9hpwmDWGnOx8IoJIdFimwwX0GG96MynPxmyDRqOo0r7HqwDUA+CJL0Zc5lsUTUHvImpp mARvbJfQFgTRPJrthUI6/xeieB4Pn0fE96mAmWbY1kLH9kAbgSpE3N+p5G+x+T7m+u+3 gdV6cuM01GYLHGAOTeS0Lnn1BWjT7BiVnbGc0RI0eb+Ls4Zs+1w21aMcLCBLMsYfxMjs nCNqki0fUwEKcm/ciQS5+HDuEdzSgquPeLgKb2wzMafJZWU/fWk59iEP/6CcwgyLak2J 9rqQ== Received: by 10.14.215.69 with SMTP id d45mr13199454eep.16.1349445216470; Fri, 05 Oct 2012 06:53:36 -0700 (PDT) Received: from [127.0.0.1] (87-231-14-74.rev.numericable.fr. [87.231.14.74]) by mx.google.com with ESMTPS id v3sm19150333een.1.2012.10.05.06.53.35 (version=SSLv3 cipher=OTHER); Fri, 05 Oct 2012 06:53:35 -0700 (PDT) Message-ID: <506EE658.7050905@gmail.com> Date: Fri, 05 Oct 2012 15:53:28 +0200 From: =?ISO-8859-1?Q?s=E9bastien_Paturel?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: flex-dev@incubator.apache.org Subject: Any news about FalconJS donation? (was: Financing the Design View AIR App (Was: Re: Design View AIR App)) References: <66E38C42347D6446BF7FCB22C3D3878072DE7C7A78@ECCR06PUBLIC.exchange.local> <66E38C42347D6446BF7FCB22C3D3878072DE7C7A8C@ECCR06PUBLIC.exchange.local> <506EE2C2.2070702@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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" 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 >>> >>> >>> >>> >>> On Oct 3, 2012, at 7:21 PM, christofer.dutz@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:aharui@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.dutz@c-ware.de" < >>>> christofer.dutz@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 >>>> -- >>>> Alex Harui >>>> Flex SDK Team >>>> Adobe Systems, Inc. >>>> http://blogs.adobe.com/aharui >>>> >>>>