Total Posts: 4
Joined: December 25, 2011
|
I am trying to understand and I did find yet the information in the doc
what do I lose in the middle when I am using NME vs writing native (I am mostly interesting in android and ios.)
witch of the api in ios/andoid will be available witch will be automatically converted from haxe api to equivalent in ios/android
thanks
Tags:
Posted on December 30, 2011 at 1:52 AM
|
Total Posts: 2146
Joined: August 25, 2011
|
Re: the pro and cons of NME
There many advantages to using NME. It performs well, performs cross-platform, and makes it easy to create 2D games.
Using extensions, its fairly simple to add additional functionality through C, C++, Objective-C or Java, depending on the platform. However, if you need true 3D or many native GUI elements, you would probably need to modify NME to suit your needs. We're leaning into 3D and application improvements, but Flash-like content (2D games, non-native interface) is NME's greatest strength right now.
The source is open so you can use NME as a starting point for deep levels of customization. As much as possible, I'd love to make it so these kinds of customization can happen officially, so you can continue to receive updates as NME improves. We'll be making it possible to override the default template for each platform, so you can tweak the XCode or Java projects by hand when an official path for customization doesn't exist.
I hope that helped answer your question. If you're curious about anything else, or something specifically or in more detail, feel free to inquire 
Posted on December 30, 2011 at 2:12 AM
|
|
Total Posts: 4
Joined: December 25, 2011
|
Re: the pro and cons of NME
About the development process is debugger available in one or all of the targets.
Posted on December 30, 2011 at 2:00 PM
|
|
Total Posts: 2146
Joined: August 25, 2011
|
Re: the pro and cons of NME
There are two kinds of debugging -- handling your application code, or debugging the framework code below.
When you are debugging your application code, you can usually choose any target. I often test in Flash, or C++ on the desktop, depending on what you are working on. You can use the Flash debugger (or trace messages, of course). It is also possible to use debuggers from Visual Studio, XCode, or gdb, depending on the target.
Using a native debugger was something I needed to do for my applications a year ago. Today, I never need to debug C++ for my applications. Very, very rarely I may print some messages when I am working on something at a framework level, but that's because I'm working to help improve NME. As a user I have never had to do this with NME 3.
Posted on December 30, 2011 at 4:07 PM
|
