OK, so did you measure how long it takes now?
how long do you wait exactly?
how do you build and test currently?
how do you compile the SWF? have you already used incremental compilation?
do you recompile only the as3 sources or also the assets? the ANE? etc.
do you do it on the command-line ?
do you use ant? make? bash?
do you do it from an IDE?
so what IDE are you using?
how long it takes from “making an update to the code” to “seeing the changed results on the screen” ?
when you have this measurement, then tell us how you imagine “Hot Reload” will be faster?
My point is you have an ideal idea of how “Hot Reload” should work but you don’t really have hard numbers to back it up, what is “slow” ?, what is “fast” ?
without measures you can not know that, so the “I need Hot Reload as a development standard” point becomes kind of moot
It is like about performance, saying “I want AIR to be faster” is nice and all, but if you don’t measure it first you’re wasting your time.
yeah it’s not like they already have 200+ issues to go through
Before asking Harman to do something, maybe you could try and show what you tested?
where is your automated build script?
what would you expect to be different? at at which level?
“I want things faster” does not cut it
- you have to show the current numbers, eg. it takes that long to compile code and that long to show in the ADL to test it
- you have to show what you already tried to make it faster
- and then you have to tell how much gain you would expect from the “hot reload” feature
the “slowness” you are apparently experiencing could be caused by many other different things than not having “Hot Reload”
maybe it is a problem with the compilers options
maybe it is a problem with the Java setup to use more memory to compile faster
maybe it is a problem with the Java version installed on your OS
maybe it is a problem with the hardware, eg. old machine, weak CPU, not enough RAM etc.
maybe it is a problem with the sources being on a SMB remote network drive
maybe it is a problem with the OS being 32-bit
maybe it is a problem with your expectation of “speed”
for ex: redtamarin on the command-line, the debug runtime takes 300ms to startup,
the release runtime takes 30ms to startup
it is the same logic with ADL, it will expect a debug SWF and will run in debug mode, and because of that you should expect a 500ms startup time, and certainly not a 50ms startup.
well @r0cketleague been kicked so he not gonna be able to answer.
When you load a SWF there is a difference between code and assets
things like sound, image, etc. can loaded/unloaded and reloaded (there are limitations on iOS see the archive)
but for code, it is what I mentioned earlier, you can not reload the same code definition
it is very easy to test by yourself, declare a class like
compile it once to
mytest1.swf and a second time to
maybe just changes some property string to different strings
mytest1.swf in the current
mytest2.swf in the same current
then see the error you get
but if I load the same class again in the same ApplicationDomain, will it override the old one?
answer is no, it will not override the class definition, you will get an errror
never tried it