You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by sébastien Paturel <se...@gmail.com> on 2012/10/05 15:53:28 UTC
Any news about FalconJS donation? (was: Financing the Design View
AIR App (Was: Re: Design View AIR App))
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" <se...@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>
>>>
>>>
>>>
>>>
>>> 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<http://www.adobe.com/devnet/flex/whitepapers/roadmap.html>
>>>> --
>>>> Alex Harui
>>>> Flex SDK Team
>>>> Adobe Systems, Inc.
>>>> http://blogs.adobe.com/aharui
>>>>
>>>>
Re: Any news about FalconJS donation? (was: Financing the Design
View AIR App (Was: Re: Design View AIR App))
Posted by sébastien Paturel <se...@gmail.com>.
Great news, thanks Alex :)
Le 05/10/2012 16:27, Alex Harui a écrit :
> FalconJS is not under development. A prototype was built several months
> ago, but no serious work has been done on it since. I should be able to
> start on its legal review next week.
>
>
> On 10/5/12 7:06 AM, "filippo dipisa" <fi...@dipisa.net> wrote:
>
>> 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 <se...@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" <se...@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/**masul
>>>>>> and>
>>>>>>
> <http://www.linkedin.**com/in/masuland<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<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
>>>>>>>
>>>>>>>
>>>>>>>
Re: Any news about FalconJS donation?
Posted by Jeffry Houser <je...@dot-com-it.com>.
On 10/5/2012 7:20 PM, Charles Monteiro wrote:
> Not getting this air is very much cross platform , running on desktops ,
> android , ios, it seems win surface rtf
>
It depends on your delivery mechanism. If you need "Cross platform"
browser based apps that have to work on an iPad or iPhone; then Flash is
out. I assumed the original poster was referring to browser based apps
/ web sites.
I agree with your sentiment that AIR can be great for cross platform
"native" apps.
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: Any news about FalconJS donation? (was: Financing the Design View
AIR App (Was: Re: Design View AIR App))
Posted by Charles Monteiro <ch...@gmail.com>.
Not getting this air is very much cross platform , running on desktops ,
android , ios, it seems win surface rtf
On Oct 5, 2012 12:21 PM, "FORMER 03 | Robert Brendler" <
robert.brendler@former03.de> wrote:
> I'd also like to drop some comment on this ...
>
> I don't know how it is with you guys, but most of the projects I am
> getting nowadays are required to be cross platform ... or better said ...
> "can you make it run on my iPad? do I really need another app for it, I
> already got like 3 million of them" ... Although I really enjoy working
> with Flex, I usually switch to html-js-css when it comes to the
> cross-platform or code-once topic, which is a step back in terms of comfort
> and speed for my development, but that is what the client wants and pays
> for. You should not blame Adobe for not continuing flex and catalyst but
> rather Mr. Jobs for declaring war on flash, and lets be honest thats a fact
> that we are facing a couple of years already, get over it. As a replacement
> I found jquery-ui to be not that bad. It gives you the "small subset" of
> flex and is available now, even with some ui effects.
>
> On the other hand if there is a project that depends on the strengths of
> flash (effects, rendering, ...) or if I am in an enterprise project that
> only runs in an enclosed environment, where there is a company that can
> dictate their employees which tool to use, I go back to flex. But in these
> cases there is no need for a conversion to js, it probably wouldn't bring
> an advantage cause it won't run as fast or make any difference other than
> the used technology, correct me if I'm wrong. And in case they still want
> something to play for their ipads I do a little html web interface that
> talks to the same services, those kind of clients usually can afford it.
>
> The only thing I could imagine that really needs both performant rendering
> and cross-platform compatibility are games ... but if you wanna walk down
> that path you are better off with C/C++ anyway.
>
> Cheers,
> Rob
>
> On 05.10.2012 16:27, Alex Harui wrote:
>
>> FalconJS is not under development. A prototype was built several months
>> ago, but no serious work has been done on it since. I should be able to
>> start on its legal review next week.
>>
>>
>> On 10/5/12 7:06 AM, "filippo dipisa" <fi...@dipisa.net> wrote:
>>
>> 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 <se...@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.flex@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/**masul<http://www.linkedin.com/in/**masul>
>>>>>>> and>
>>>>>>>
>>>>>>> <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.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<http://www.adobe.com/devnet/****flex/whitepapers/roadmap.html>
>>>>>>>> <http://www.
>>>>>>>> adobe.com/devnet/**flex/**whitepapers/roadmap.html<http://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<http://adobe.com/devnet/flex/whitepapers/roadmap.html>
>>>>>>>> >
>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>> Alex Harui
>>>>>>>> Flex SDK Team
>>>>>>>> Adobe Systems, Inc.
>>>>>>>> http://blogs.adobe.com/aharui
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>
>
> --
> _____ FORMER 03 GmbH
> _____ infanteriestraße 19 haus 6
> _____ 80797 muenchen
>
> _____ robert.brendler@former03.de
> _____ www.former03.de
>
> _____ fon 089.322112.28
> _____ fax 089.322112.11
>
> _____ geschäftsführer
> _____ sebastian fiedler
> _____ gert zellentin
>
> _____ handelsregister
> _____ HRB München 148468
>
> _____ steuer
> _____ ust.-id DE 229107876
>
Re: Any news about FalconJS donation? (was: Financing the Design
View AIR App (Was: Re: Design View AIR App))
Posted by FORMER 03 | Robert Brendler <ro...@former03.de>.
I'd also like to drop some comment on this ...
I don't know how it is with you guys, but most of the projects I am
getting nowadays are required to be cross platform ... or better said
... "can you make it run on my iPad? do I really need another app for
it, I already got like 3 million of them" ... Although I really enjoy
working with Flex, I usually switch to html-js-css when it comes to the
cross-platform or code-once topic, which is a step back in terms of
comfort and speed for my development, but that is what the client wants
and pays for. You should not blame Adobe for not continuing flex and
catalyst but rather Mr. Jobs for declaring war on flash, and lets be
honest thats a fact that we are facing a couple of years already, get
over it. As a replacement I found jquery-ui to be not that bad. It gives
you the "small subset" of flex and is available now, even with some ui
effects.
On the other hand if there is a project that depends on the strengths of
flash (effects, rendering, ...) or if I am in an enterprise project that
only runs in an enclosed environment, where there is a company that can
dictate their employees which tool to use, I go back to flex. But in
these cases there is no need for a conversion to js, it probably
wouldn't bring an advantage cause it won't run as fast or make any
difference other than the used technology, correct me if I'm wrong. And
in case they still want something to play for their ipads I do a little
html web interface that talks to the same services, those kind of
clients usually can afford it.
The only thing I could imagine that really needs both performant
rendering and cross-platform compatibility are games ... but if you
wanna walk down that path you are better off with C/C++ anyway.
Cheers,
Rob
On 05.10.2012 16:27, Alex Harui wrote:
> FalconJS is not under development. A prototype was built several months
> ago, but no serious work has been done on it since. I should be able to
> start on its legal review next week.
>
>
> On 10/5/12 7:06 AM, "filippo dipisa" <fi...@dipisa.net> wrote:
>
>> 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 <se...@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" <se...@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/**masul
>>>>>> and>
>>>>>>
> <http://www.linkedin.**com/in/masuland<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<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
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>
--
_____ FORMER 03 GmbH
_____ infanteriestraße 19 haus 6
_____ 80797 muenchen
_____ robert.brendler@former03.de
_____ www.former03.de
_____ fon 089.322112.28
_____ fax 089.322112.11
_____ geschäftsführer
_____ sebastian fiedler
_____ gert zellentin
_____ handelsregister
_____ HRB München 148468
_____ steuer
_____ ust.-id DE 229107876
Re: Any news about FalconJS donation? (was: Financing the Design
View AIR App (Was: Re: Design View AIR App))
Posted by Alex Harui <ah...@adobe.com>.
FalconJS is not under development. A prototype was built several months
ago, but no serious work has been done on it since. I should be able to
start on its legal review next week.
On 10/5/12 7:06 AM, "filippo dipisa" <fi...@dipisa.net> wrote:
> 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 <se...@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" <se...@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/**masul
>>>>> and>
>>>>>
<http://www.linkedin.**com/in/masuland<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<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
>>>>>>
>>>>>>
>>>>>>
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Any news about FalconJS donation? (was: Financing the Design View
AIR App (Was: Re: Design View AIR App))
Posted by filippo dipisa <fi...@dipisa.net>.
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 <se...@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" <se...@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.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<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
>>>>>
>>>>>
>>>>>
>