- Last visit
|this is about loading updated .as files from server, rather than build + installing a new .apk each time.|
my big issue with Papaya is long cycle from code to running.
compiling the .as files is quick, but then building the .apk takes 30s~60s each time.
BUT papaya is able to load just the updated files without a new apk, right?
eg if i compile to main and also put the main.md5 on the server, the old .apk should now load in my updated .as code?
So i tried to get this working but am a bit stuck.
if i take just the new main + main.md5
move to a webserver
now, when i hit the app (2nd time) the md5 is different so the app knows to try and download the main again, which it does.
I see this in webserver log:
192.168.2.45 - - [Tue, 11 Oct 2011 00:38:43 GMT] "GET /main.md5 HTTP/1.1" 200 32 "-" "Dalvik/1.4.0 (Linux; U; Android 2.3.6; Nexus One Build/GRK39F)"
192.168.2.45 - - [Tue, 11 Oct 2011 00:38:43 GMT] "GET /main HTTP/1.1" 200 1178 "-" "Dalvik/1.4.0 (Linux; U; Android 2.3.6; Nexus One Build/GRK39F)"
so great, that looks like the code should be patched. the two files it read were:
when i do NOT modify anything, it just checks the md5 hash and doesn't load main. all expected behavior so far.
BUT when i run the app, i see no changes.
so if the client is requesting the files, what is it doing with them?
or, are these partial updates to main just for graphics, and not for code?
related question: currently the papaya compile command also builds the apk
$ cat compile.sh
data/exe.macosx-10.6-i386-2.5/r compile $1 $2 $3 $4 $5
is there a command to just do the compile stage?
thanks for help, getting this working would make a big difference!