Different games have different needs. By making it clear what features we need early, the development of love-native-android can be focused on what people care about.
My personal list of features I'd love to see goes something like this:
1. An easy way to make stand-alone games. This one's obvious and has already been discussed quite a while, but is a make-or-break feature for me. I can work aroung bugs and missing features, but this is something I absolutely need for my game.
2. Multitouch. This one is also obvious, and I'm sure it's coming in the love.phone api. Perhaps it is already implemented? If so, how does it work? I think the java version made some progress here but I'm not sure how far they got. For my game, all I really need is to get two coordinates (x1,y1,x2,y2) as arguments for a function which is called whenever fingers touch the screen.
3. Force orientation. My game needs to run in landscape mode at all times, regardless of phone settings. I think this is a feature that many other games will need as well. This is not really something that must be added explicitly, as long as we're talking stand-alone applications, this can easily be fixed with an extra line in AndroidManifest. But since some people here seem to want to use love-native-android for more than stand-alone games, this becomes kind of important for them.
4. Ads in the game. Not sure if this is possible but it would be awesome. I intend to release both a demo version and a full version of my game on Google Play. If I could make a little money by putting an ad in the game's menus, that would be great. This of quite low priority for me though. But I think that by supporting this, love-native-android can attract a lot of game developers both to itself and the Android platform as a whole.
I will add more as I realize I need them. Some of these features are already planned, some may be considered low-priority for now. Still, these are the features I need for my game.
What features does your game need? Post them here!
love-native-android: request a feature
love-native-android: request a feature
Last edited by T-Bone on Tue Apr 03, 2012 8:02 am, edited 3 times in total.
My game called Hat Cat and the Obvious Crimes Against the Fundamental Laws of Physics is out now!
- alberto_lara
- Party member
- Posts: 372
- Joined: Wed Oct 30, 2013 8:59 pm
Re: love-native-android: request a feature
Link down I was looking specifically if it's possible to put some ad on my games (?)
- Ranguna259
- Party member
- Posts: 911
- Joined: Tue Jun 18, 2013 10:58 pm
- Location: I'm right next to you
Re: love-native-android: request a feature
1+ for adds
- alberto_lara
- Party member
- Posts: 372
- Joined: Wed Oct 30, 2013 8:59 pm
Re: love-native-android: request a feature
Great! any kind of ads like if it were made in Java?
- Positive07
- Party member
- Posts: 1014
- Joined: Sun Aug 12, 2012 4:34 pm
- Location: Argentina
Re: love-native-android: request a feature
Since T-Bone suggested many features I will answer his post (it is really old but anyway)
1. It is not that hard once you have set your environmentT-Bone wrote: 1. An easy way to make stand-alone games. This one's obvious and has already been discussed quite a while, but is a make-or-break feature for me. I can work aroung bugs and missing features, but this is something I absolutely need for my game.
2. Done (and also now it supports gestures)T-Bone wrote: 2. Multitouch. This one is also obvious, and I'm sure it's coming in the love.phone api. Perhaps it is already implemented? If so, how does it work? I think the java version made some progress here but I'm not sure how far they got. For my game, all I really need is to get two coordinates (x1,y1,x2,y2) as arguments for a function which is called whenever fingers touch the screen.
3. Use the AndroidManifest or just [wiki]love.graphics.rotate[/wiki] and [wiki]love.graphics.translate[/wiki] (This doesn't modify the keyboard thought, since the keyboard is defined at installation time by the manifest)T-Bone wrote: 3. Force orientation. My game needs to run in landscape mode at all times, regardless of phone settings. I think this is a feature that many other games will need as well. This is not really something that must be added explicitly, as long as we're talking stand-alone applications, this can easily be fixed with an extra line in AndroidManifest. But since some people here seem to want to use love-native-android for more than stand-alone games, this becomes kind of important for them.
4. Done by someone elseT-Bone wrote: 4. Ads in the game. Not sure if this is possible but it would be awesome. I intend to release both a demo version and a full version of my game on Google Play. If I could make a little money by putting an ad in the game's menus, that would be great. This of quite low priority for me though. But I think that by supporting this, love-native-android can attract a lot of game developers both to itself and the Android platform as a whole.
for i, person in ipairs(everybody) do
[tab]if not person.obey then person:setObey(true) end
end
love.system.openURL(github.com/pablomayobre)
[tab]if not person.obey then person:setObey(true) end
end
love.system.openURL(github.com/pablomayobre)
Re: love-native-android: request a feature
I would like to have vibration.
While it's annoying in some cases, it might be nice as a haptic feedback sometimes.
While it's annoying in some cases, it might be nice as a haptic feedback sometimes.
- slime
- Solid Snayke
- Posts: 3170
- Joined: Mon Aug 23, 2010 6:45 am
- Location: Nova Scotia, Canada
- Contact:
Re: love-native-android: request a feature
You should post feature requests in the love-android issue tracker (or the regular LÖVE issue tracker, if the feature request would also be useful on Windows/Mac/Linux.)
The iOS port adds a new setting for t.window in love.conf and the flags table in love.window.setMode: an optional orientations table to let you choose which orientations to support in your code, e.g.:
I don't believe it's possible to add the same functionality to the Android port though, unfortunately.
The graphics transformations also won't affect input (mouse, touch) coordinates on their own.Positive07 wrote: 3. Use the AndroidManifest or just [wiki]love.graphics.rotate[/wiki] and [wiki]love.graphics.translate[/wiki] (This doesn't modify the keyboard thought, since the keyboard is defined at installation time by the manifest)
The iOS port adds a new setting for t.window in love.conf and the flags table in love.window.setMode: an optional orientations table to let you choose which orientations to support in your code, e.g.:
Code: Select all
function love.conf(t)
-- If you create this table, the values default to false so you don't need to specify every one.
t.window.orientations = {
landscapeleft = true,
landscaperight = true,
portrait = false,
portraitupsidedown = false,
}
end
- Positive07
- Party member
- Posts: 1014
- Joined: Sun Aug 12, 2012 4:34 pm
- Location: Argentina
Re: love-native-android: request a feature
Nice! So if you are in one of those orientations it automatically changes? Does it calls resize when doing so?
for i, person in ipairs(everybody) do
[tab]if not person.obey then person:setObey(true) end
end
love.system.openURL(github.com/pablomayobre)
[tab]if not person.obey then person:setObey(true) end
end
love.system.openURL(github.com/pablomayobre)
Who is online
Users browsing this forum: No registered users and 13 guests