Hi I am only a user of flex, I have spent 3 years of my time building a app for a charity, and we have 5-10 year life in the product, what I know, flex works, it is simple, it works, the good chaps on this list are investing a lot of there time to give flex a future, yes HTML/CSS/JS is the elephant in the room, if / when we have quality cross-compiling we will look back and think adobe giving flex to Apache was the best move ever
We just need to give this project time Anyway that¹s my 2cents Scott On 2/28/13 8:52 AM, "Harbs" <gavha...@gmail.com> wrote: >Huh? > >You can compile MXML to AIR today. Who said anything about not supporting >that? > >If you are talking about the Falcon Compiler (which is not required for >compiling to AIR), the work for MXML compilation is currently being >finished by Gordon Smith. That's near-term support. The HTML /JS support >is a longer term goal. I've never seen any indication to cause your >concerns. > >Harbs > >On Feb 28, 2013, at 10:05 AM, Terry Corbet wrote: > >> Why is it that you fail to see that each time you advertize your rush >>to cross-compiling MXML to HTML/CSS/Javascript and never provide status >>concerning the compilation of MXML to run in the AIR environment you are >>causing the very anxiety that we all deal with? You know that your >>employer is going to stop shipping the old compiler in favor of the new >>compiler. You know that the Gaming Guru will not let any resource be >>devoted to having the new compiler successfully compile Flex, i.e. Spark >>Components. So, exactly where are we supposed to feel confident that >>the Apache Flex project will let us maintain 'parity' [your favoirite >>word] in regards to compiling our AIR MXML applications with the new >>compiler? I have every reason to believe that you will achieve your >>objective, which is to have the Falcon work let you cross-compile to the >>environment that you believe has future possibilities, and, as long as >>one person is on loan one day per week, to get MXML compilation working, >>not much reason whatsoever to believe that on-going developoment of AIR >>applictions has a future. >> >> >> ----- Original Message ----- From: "Alex Harui" <aha...@adobe.com> >> To: <users@flex.apache.org>; <flex-us...@incubator.apache.org> >> Sent: February 27, 2013 10:05 PM >> Subject: Re: Future of Flex technology >> >> >> >> >> >> On 2/27/13 9:48 PM, "Devesh Mishra" <devesh.mis...@mastek.com> wrote: >> >>> Hi, >>> >>> Is there any future of Flex technology, as we can see that there are >>>no big >>> improvements are coming in Flex. According to today's scenario, Flex >>>is only >>> for desktop application and we are entering into mobile technology. So >>>it's a >>> bit difficult to understand the future existence of Flex. >>> >>> If we talk from market point of view, everyone is moving towards >>> HTML5/Android/Ios, after Adobe declaration for no support in >>>Flash/Flex. >> Adobe did not say "no support". Adobe is still supporting Flash, and >>you >> can still purchase Flex support contracts from Adobe. Adobe donated >>Flex to >> Apache so it can continue to be developed in the open. Adobe continues >>to >> make releases of Flash. >> >> Still, lots of people are moving to HTML5/Android/IOS, and so is Apache >> Flex. If you monitor the d...@flex.apache.org mailing list you will see >>that >> we are hard at work on trying to cross-compile MXML and ActionScript to >> HTML/JS/CSS which can then be run through PhoneGap/Cordova to create >>mobile >> apps. It is still in its infancy and we have lots of work ahead, but >>we are >> making progress. >> >> See [1] for more on one approach we are taking. >> >> [1] >> >>https://cwiki.apache.org/confluence/display/FLEX/Alex%27s+FlexJS+Prototyp >>e >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2013.0.2899 / Virus Database: 2641/6135 - Release Date: >>02/26/13 >> >> > ________________________________ Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
