@Kurt: yeah the list is the best resource. haxe is based on AS3, but you get better structure, type inference, enums, typedefs all sorts of extra goodies....
On 30 November 2011 17:20, Matt Perkins <nudoru.m...@gmail.com> wrote: > It's only been three days but haXe seems to be able to use all of AS3 > intermingled with haXe syntax, so I'm thinking of it as AS3++. (maybe > that's a stretch) > > -- > Matt Perkins > ----------------- > http://www.nudoru.com > > On Nov 30, 2011, at 9:53 AM, "Merrill, Jason" > <jason.merr...@bankofamerica.com> wrote: > > > Wow, thanks for all this discussion - this is great! So many good > responses, thanks everyone for contributing and keep it coming! I think > I'm definitely taking up haXe in 2012! > > > > Another question, I know haXe is just as good and powerful (if not more) > than AS3, but does AS3 have any syntactical / features that give it an > advantage over haXe or is haXe just a better language overall in your > opinion(s)? > > > > Jason Merrill > > Instructional Technology Architect II > > Bank of America Global Learning > > > > > > > > > > > > _______________________ > > > > > > -----Original Message----- > > From: flashcoders-boun...@chattyfig.figleaf.com [mailto: > flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Kurt Dommermuth > > Sent: Wednesday, November 30, 2011 8:35 AM > > To: Flash Coders List > > Subject: Re: [Flashcoders] Switching to HaXe? > > > > Thanks again Tom. The example is impressive. > > > > On Wed, Nov 30, 2011 at 8:21 AM, tom rhodes <tom.rho...@gmail.com> > wrote: > > > >> Hi, > >> > >> ok, initially the haxe flash api to html5 was done with a lib called > jeash. > >> which has been around for a while now. the nme project has very > >> recently incorporated jeash as it's route to html5. > >> > >> here is a nice example of using one codebase to hit swf and html5... > >> > >> > >> http://www.joshuagranick.com/blog/2011/09/22/first-glimpse-at-cross-pl > >> atform-game-running-flash-and-html5/ > >> > >> if you do a google for haxe jeash, you'll see it's been around for a > >> while and it's integration into nme seems pretty natural. they were > >> parallel efforts in intepreting the flash api for ages... > >> > >> On 30 November 2011 14:03, Kurt Dommermuth <k...@kurtdommermuth.com> > >> wrote: > >> > >>> Hi Tom, > >>> > >>> Thank you. I'm going to look into Haxe more. > >>> > >>> Psychologically I have a stumbling block with NME. On their how it > >>> works page (http://www.haxenme.org/about-nme/how-it-works/) there > >>> are > >> solutions > >>> that go in the opposite direction of what I'm personally interested in. > >>> > >>> They very nicely show how NME publishes to SWF, iOS, webOS, Android, > >>> MAC/LInux, but it doesn't mention publishing to HTML5/JS. > >>> > >>> It very well may, but you can understand why I'd tend to move on if > >>> it's not mentioned on that page. > >>> > >>> Forgive me if I'm missing something. I'm deep in this search for a > >>> solution and I'll be the first to admit I could easily misunderstand > >>> something. > >>> > >>> Kurt > >>> > >>> On Wed, Nov 30, 2011 at 7:33 AM, tom rhodes <tom.rho...@gmail.com> > >> wrote: > >>> > >>>> the haxe forum isn't very active but the mailing list is, and it > >>>> is a > >>> great > >>>> place to get help to get started. > >>>> > >>>> this is the new home of the list > >>>> > >>>> https://groups.google.com/group/haxelang/topics?pli=1 > >>>> > >>>> you have to dig around a bit to get going as documentation is > >>>> limited > >> at > >>>> the moment but the list is the best place to get the information > >>>> you > >>> need. > >>>> > >>>> if you want to do html5 using code that is familiar to you as an > >>>> AS3 > >>> coder > >>>> then look at NME as i mentioned in a previous post. > >>>> > >>>> On 30 November 2011 13:16, Kurt Dommermuth > >>>> <k...@kurtdommermuth.com> > >>>> wrote: > >>>> > >>>>> Hi Jason, > >>>>> > >>>>> You're very first statement is exactly what interests me too. > >>>>> You > >>> wrote > >>>>> "Thinking of starting to learn haXe to produce OOP apps and > >>>>> export as Javascript for HTML 5 apps." > >>>>> > >>>>> What are your thoughts so far? I just looked at Haxe too but > >>>>> I'm > >>>> concerned > >>>>> because there doesn't seem to be a lot of actvity in the Haxe forum. > >>>>> > >>>>> I'm at a loss this morning because at this moment I really just > >>>>> want > >> to > >>>>> make a web based app that performs well on the iPhone. I have > >>>>> looked > >> at > >>>> the > >>>>> following and am not finding satisfaction: > >>>>> > >>>>> appmobi - they get too many hooks into you and force you down > >>>>> paths > >> you > >>>> may > >>>>> not necessarily want to go - like using the Amazon network to > >>>>> store > >>>> files. > >>>>> I just wanted to grab my resources and upload them to MY server. > >>>>> No > >>> easy > >>>>> task with appmobi. > >>>>> > >>>>> phonegap - everyone seems to love it, but it seems to be > >>>>> primarily > >>> geared > >>>>> to use traditional web based tools to compile to native apps. I > >>>>> want > >>> to > >>>> be > >>>>> on the web - not the device. > >>>>> > >>>>> jQuery mobile - assumes you want to make a web site, not an app > >>>>> and > >>>> injects > >>>>> all kinds of styles that get in the way. I'm a big fan of > >>>>> jQuery, > >> but > >>>>> jQuery mobile is very confining. > >>>>> > >>>>> sencha - seems promising, but within 2 hours of working with it > >>>>> I > >> seem > >>> to > >>>>> have found a bug. I cannot add a listener. May be my > >> misunderstanding > >>>>> though, so I'm going to continue. > >>>>> > >>>>> Based on this conversation I looked at NME, but again, my small > >>>> mindedness, > >>>>> it feels like voodoo and it just doesn't seem to put much > >>>>> emphasis on publishing for web based apps. > >>>>> > >>>>> Overall, I must say I resent the hell out of Steve Jobs. His > >> comments > >>>> have > >>>>> thrown us back into the dark ages. I look at the options to > >> accommodate > >>>> his > >>>>> vision and I see one Frankenstein solution after another. HTML5 > >> seems > >>> to > >>>>> be a handful of multimedia tags meant to make everyone and their > >>>>> mom > >> a > >>>> web > >>>>> programer and that it will work on everything. Hahhahahaha. > >>>>> The > >>> problem > >>>>> is that the reality is it takes a boat load of JS and fall backs > >>>>> to > >>> make > >>>> it > >>>>> work. > >>>>> > >>>>> We had AS3. It did the job and though it was flawed it was far > >>>>> and > >>> away > >>>>> the best cross platform solution there was. dammit. Because of > >>>>> one > >>> dummy > >>>>> and his legions of lemmings we're back to using 15 year old > >>>>> scripting languages to get things done. > >>>>> > >>>>> Hmmmm. Guess I'm a little feisty and bitter this morning! > >>>>> > >>>>> :) > >>>>> > >>>>> Thanks for letting me vent. > >>>>> > >>>>> Anyway, I appreciate the discussion very much on this topic. > >>>>> > >>>>> Kurt > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> On Tue, Nov 29, 2011 at 11:04 AM, Merrill, Jason < > >>>>> jason.merr...@bankofamerica.com> wrote: > >>>>> > >>>>>> Thinking of starting to learn haXe to produce OOP apps and > >>>>>> export > >> as > >>>>>> Javascript for HTML 5 apps. Checked it out years ago, but > >>>>>> decided > >>>> against > >>>>>> it since it was not part of the normal ecosystem and would > >>>>>> have to > >> be > >>>>>> sharing code with non-haXe AS3 developers. But not thinking of > >>>>>> the > >>>>> future, > >>>>>> I am more interested in it given what's happening with Adobe > >>>>>> and > >>> HTML5. > >>>>>> Anyone done that and does it work well for that? Can you have > >>>>>> a > >>> single > >>>>>> source base and export for AS3 apps and Javascript for HTML 5 > >>>>>> or > >> are > >>>>> there > >>>>>> caveats? > >>>>>> > >>>>>> Jason Merrill > >>>>>> Instructional Technology Architect II Bank of America > >>>>>> Global Learning > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>> -------------------------------------------------------------------- > >>> -- > >>>>>> 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. > >>>>>> _______________________________________________ > >>>>>> Flashcoders mailing list > >>>>>> Flashcoders@chattyfig.figleaf.com > >>>>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > >>>>>> > >>>>>> > >>>>> _______________________________________________ > >>>>> Flashcoders mailing list > >>>>> Flashcoders@chattyfig.figleaf.com > >>>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > >>>>> > >>>> _______________________________________________ > >>>> Flashcoders mailing list > >>>> Flashcoders@chattyfig.figleaf.com > >>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > >>>> > >>>> > >>> _______________________________________________ > >>> Flashcoders mailing list > >>> Flashcoders@chattyfig.figleaf.com > >>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > >>> > >> _______________________________________________ > >> Flashcoders mailing list > >> Flashcoders@chattyfig.figleaf.com > >> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > >> > >> > > _______________________________________________ > > Flashcoders mailing list > > Flashcoders@chattyfig.figleaf.com > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > ---------------------------------------------------------------------- > > 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. > > _______________________________________________ > > Flashcoders mailing list > > Flashcoders@chattyfig.figleaf.com > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
