State of the attempt to natively port love to android

[Ensayia]

Not entirely sure about the ins and outs of the Android Market, but is there any way that LOVE could go up there and maybe cost a few dollars which would be a 'donation' to the LOVE team? I see these type of donor apps all the time and I think members of the community would pay to send a few dollars their way.

[kalle2990]

I am not sure. but I planned to check the license stuff, upload the code and prepare an alpha apk within the next weeks.

Okay, that seems fair Would be quite sad if the licenses got messed up..

Not entirely sure about the ins and outs of the Android Market, but is there any way that LOVE could go up there and maybe cost a few dollars which would be a 'donation' to the LOVE team? I see these type of donor apps all the time and I think members of the community would pay to send a few dollars their way.

There's not really any rules for the Android Market (except from porn, malware and illegal things) so I guess it should be fine I would gladly spend a few dollars on it, and I think others might too

[Moe]

Finally, it time that I register here, too - short intro: I am also working on the native port

I am not sure. but I planned to check the license stuff, upload the code and prepare an alpha apk within the next weeks.

Okay, that seems fair Would be quite sad if the licenses got messed up..

The reason for the license issues is convenience during development. The simplest thing (because we would not need lawyers ) would be to change our build scripts to separately build all libraries instead of one lovely monster lib. We should do it anyway for several reasons, up to now it simply made our live easier, because the build script is faster written.

Not entirely sure about the ins and outs of the Android Market, but is there any way that LOVE could go up there and maybe cost a few dollars which would be a 'donation' to the LOVE team? I see these type of donor apps all the time and I think members of the community would pay to send a few dollars their way.

There's not really any rules for the Android Market (except from porn, malware and illegal things) so I guess it should be fine I would gladly spend a few dollars on it, and I think others might too

As soon as we solve the licensing stuff, we can put a version to the market, I can upload a free version with my account.

[T-Bone]

Finally, it time that I register here, too - short intro: I am also working on the native port

I am not sure. but I planned to check the license stuff, upload the code and prepare an alpha apk within the next weeks.

Okay, that seems fair Would be quite sad if the licenses got messed up..

The reason for the license issues is convenience during development. The simplest thing (because we would not need lawyers ) would be to change our build scripts to separately build all libraries instead of one lovely monster lib. We should do it anyway for several reasons, up to now it simply made our live easier, because the build script is faster written.

Not entirely sure about the ins and outs of the Android Market, but is there any way that LOVE could go up there and maybe cost a few dollars which would be a 'donation' to the LOVE team? I see these type of donor apps all the time and I think members of the community would pay to send a few dollars their way.

There's not really any rules for the Android Market (except from porn, malware and illegal things) so I guess it should be fine I would gladly spend a few dollars on it, and I think others might too

As soon as we solve the licensing stuff, we can put a version to the market, I can upload a free version with my account.

That would be awesome, especially if you were to update the Market version on a regular basis, which is much easier than downloading a new apk all the time.

Welcome to the forums, btw Hope you'll have a good time here.

[firefly2442]

Tried this on a Samsung Galaxy Nexus with ICS 4.0.

Downloaded and built from Github hash: dbb56cae2ad3249fa07da2a283b24248c0d28e11

Changed target to 15 for new 4.0 Android version.

Set the ANDROID_HOME path variable or whatnot in bash.

After removing the @overrides for an error in Eclipse, the project seemed to build. Test and fonttest worked fine. Clouds and myZipTest didn't seem to do anything, although the clouds one I couldn't even get to run on the desktop (complained about a missing .wav file).

Anyway, looking forward to more updates. Let me know if you need additional testing on my phone. Cheers.

[firefly2442]

Also, I noticed this in the readme:

t.android_native_screen ** if this is not set, then love.graphics.setMode(w,h) is called at startup with t.screen.width/height or default pc resolution

Would it be better to use something like this:

http://developer.android.com/reference/ ... trics.html

as a fallback in case the value isn't set in the lua config file? I don't know much about Android but just an idea. Cheers.

[kraftman]

Also, I noticed this in the readme:

t.android_native_screen ** if this is not set, then love.graphics.setMode(w,h) is called at startup with t.screen.width/height or default pc resolution

Would it be better to use something like this:

http://developer.android.com/reference/ ... trics.html

as a fallback in case the value isn't set in the lua config file? I don't know much about Android but just an idea. Cheers.

my guess is that a lot will change now that they are porting it natively.

[hagish]

Probably yes. The first thing is to get to work loves main parts. Then we plan to add the mobile/touch stuff.
But all the current love-android specific things are "unstable". It is likely that they change in some way.

[Moe]

After removing the @overrides for an error in Eclipse, the project seemed to build.

Sounds like your Java version is not right. Sorry, I always forget if it is too new or too old if it does not accept @override. Make sure that you use Java 1.5 or 1.6. If you build for Android >= 2.3 you should use 1.6, elsewise 1.5.

[bartbes]

I need to remove them, and I'm running 1.7.