Currently away3dlite does not support bsp, and for me that is a large
consideration. As far as I understand it away supports haXe ( only in
lite flavor ) but it probably runs slower as it is designed around as3
principles and not haXe so it is not tuned to haXe in the same way as
a project started in haXe, but I might be wrong. The advantage of
haXe compiler is that it currently puts more effort into producing
optimised byte code, you don't need to pass code through an optimiser,
which you can do with away as3, and haxe can support more targets and
it easier to serialize classes and communicate with other targets. If
you want to move it to the iphone as an app, I suspect you will be
looking at sandy3d haxe (or away3dlite haxe), as remapping classes to
native classes will run faster than wrapping a swf in a browser and
setting up communication which is what adobe do, but if you only want
to target flash platform then there is little advantage in haXe, and
the limitations of lite may limit you, porting away3dlite as3 to
away3dlite haXe is not so tricky so really there is no difference if
you are working with lite... so more a preference, if you know as3 and
haXe then porting your code over between lite versions should not be
too hard, you can easily mix code, so you can compile the away3d
standard library and use it in haXe, I have not tried this yet... that
might be the best approach.
Currently I suspect flash.memory will not make huge improvements to
away3d without considerable changes... but that's all rocket science
to me :) I asked Rob if they have plans to do lots on haXe version, I
think they have some other stuff to do first so it may well be awhile.
It must be said that compiling with flashIDE is very slow when
compared with haXe, so there can be considerable man hours gained by
having faster compiler times, but haxe is more strict so it can trip
you up more but will result in a more robust runtime.
So maybe a mix is optimum if you can work out the setup, you might be
able to sneak in some flash.memory and still use away3d full version.
HaXe does not need to be passed through Joa's optimisation tools from
what I have read... it is in theory faster, but away3d was designed in
as3 not haXe.
But if you want to be sure do your own tests.
Cheers
;j
On 6 Oct 2010, at 22:47, Gil Matos wrote:
sorry, just to ask, if you are starting a project right now, is it
worthy to make it in haxe, are the speed improvements that come with
using flash.memory coming soon? thanks
