There's another key issue - who wants to work with machine converted code?
Sounds like a nightmare.
John
2011/12/1 Doug McCune <d...@dougmccune.com>

> **
>
>
> Just to throw in my two cents... I would not hold out any hope for any
> solution that will magically convert your Flex app to a HTML/JS app. Not in
> 6 months, not in 6 years. I don't want to be a downer, but I just don't see
> it happening. Sure, we may see some tech demos that work on super simple
> Flex apps, but I think that's about as far as you'll get. You also might
> get tools that let you write a new app in MXML/AS, specifically with
> targeting HTML/JS in mind, and that might work well. But I have almost no
> confidence that you will ever be able to take an existing, large Flex app
> and magically get it to run well as an HTML app. I'd of course love to be
> proven wrong.
>
> My advice is that if you really need to target HTML/JS is to build it new
> from scratch. It's a harsh reality, and you're going to hate a lot of the
> toolchain, language, and process, but if you really do have the requirement
> that you need to have an HTML/JS app, you might as well just rip off the
> band-aid in one go instead of holding out hope for a holy grail solution.
>
> On Thu, Dec 1, 2011 at 6:27 AM, Merrill, Jason <
> jason.merr...@bankofamerica.com> wrote:
>
>> **
>>
>>
>> Check out another possibility - using haXe for converting an
>> MXML/Actionscript project to HTML5/Javascript.  The syntax is extremely
>> similar to Actionscript, so you could convert the MXML (via the option with
>> the compiler to save the generated Actionscript from MXML) to haXe code,
>> and the Actionscript too.  ****
>>
>> ** **
>>
>> Jason Merrill
>> Instructional Technology Architect II**
>>
>> * Bank of America*  Global Learning ****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> _______________________****
>>
>> ** **
>>
>> *From:* flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] *On
>> Behalf Of *ganaraj p r
>> *Sent:* Thursday, December 01, 2011 4:13 AM
>> *To:* flexcoders@yahoogroups.com
>> *Subject:* Re: [flexcoders] Flex to HTML5 Conversion tool?****
>>
>> ** **
>>
>>   ****
>>
>> If my understanding is right, Adobe is working on it currently. So you
>> might have to wait for another 6 months or so. ****
>>
>> ** **
>>
>> If that time frame is not suitable for you, I suggest you rewrite the
>> project in HTML 5.****
>>
>> On Thu, Dec 1, 2011 at 3:27 AM, Sells, Fred <fred.se...@adventistcare.org>
>> wrote:****
>>
>>   ****
>>
>> I am looking at the same problem.  A very long time ago I designed a tool
>> called ezX that was similar to Flex but not nearly as robust.  That was an
>> Xwindows tool and has since gone the way of the dinosaur.****
>>
>>  ****
>>
>> I’m still researching but I think a tool like pyjamas pyjs.org  might be
>> a building block.  You could write an xml parser to handle the mxml to dom
>> and then use the dom to generate pyjamas class definitions (which you would
>> probably have to tweak by hand).****
>>
>>  ****
>>
>> I’m not sure about the action script.  Source parsing is too tricky and I
>> don’t know if the byte code is easy to handle.  Might be better to
>> outsource that overseas.****
>>
>>  ****
>>
>> Let me know what you decide****
>>
>>  ****
>>
>> *From:* flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] *On
>> Behalf Of *Venkat M
>> *Sent:* Wednesday, November 30, 2011 12:56 PM
>> *To:* flexcoders@yahoogroups.com
>> *Subject:* [flexcoders] Flex to HTML5 Conversion tool?****
>>
>>  ****
>>
>>   ****
>>
>> *Hi Group,*****
>>
>> * *****
>>
>> *I have a quick question.*****
>>
>> *I have a web application that was developed using 100% flex (AS
>> included).*****
>>
>> *Now to be on the safe side we want to evaluate the options of
>> converting the same on to HTML5. *****
>>
>> * *****
>>
>> *Do any one know of any tools that can help in the process of converting
>> from flex (developed) to html5 version?*****
>>
>> *Your help will be greatly appreciated.*****
>>
>>  ****
>>
>> Cheers,****
>>
>> *Venkat.*****
>>
>>  ****
>>
>>  ****
>>
>>
>>
>> ****
>>
>> ** **
>>
>> --
>> Regards,
>> Ganaraj P R****
>>
>> ****
>>  ------------------------------
>> This message w/attachments (message) is intended solely for the use of
>> the intended recipient(s) and may contain information that is privileged,
>> confidential or proprietary. If you are not an intended recipient, please
>> notify the sender, and then please delete and destroy all copies and
>> attachments, and be advised that any review or dissemination of, or the
>> taking of any action in reliance on, the information contained in or
>> attached to this message is prohibited.
>> Unless specifically indicated, this message is not an offer to sell or a
>> solicitation of any investment products or other financial product or
>> service, an official confirmation of any transaction, or an official
>> statement of Sender. Subject to applicable law, Sender may intercept,
>> monitor, review and retain e-communications (EC) traveling through its
>> networks/systems and may produce any such EC to regulators, law
>> enforcement, in litigation and as required by law.
>> The laws of the country of each sender/recipient may impact the handling
>> of EC, and EC may be archived, supervised and produced in countries other
>> than the country in which you are located. This message cannot be
>> guaranteed to be secure or free of errors or viruses.
>>
>> References to "Sender" are references to any subsidiary of Bank of
>> America Corporation. Securities and Insurance Products: * Are Not FDIC
>> Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit
>> * Are Not a Condition to Any Banking Service or Activity * Are Not Insured
>> by Any Federal Government Agency. Attachments that are part of this EC may
>> have additional important disclosures and disclaimers, which you should
>> read. This message is subject to terms available at the following link:
>> http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender
>> you consent to the foregoing.
>>
>>
>  
>

Reply via email to