RFC: Lua API Normalization

[GoogleCodeExporter]

I noticed some burrs while working on the lua docs. Here are some changes I'd 
like to suggest:

BfObject:getClassId() -> BfObject:getObjType()
Since it's comparison equal to the ObjType enum, and called ObjType internally.

BfObject:getLoc() -> BfObject:getPos()
BfObject:setLoc() -> BfObject:setPos()
Position is the standard physics term. We can simply document that the 
definition of "position" changes with context.

Item:isInCaptureZone() -> [Remove]

SpeedZone:getDir() -> SpeedZone:getAngle()
SpeedZone:setDir() -> SpeedZone:setAngle()
setDir() directly sets vertex 2, getDir() returns point.normalize(v2-v1)
Thus, zone1:setDir(zone2:getDir()) will not work as expected. I think it's 
better just to use angle anyway.

Can we implement BfObject:clone() now?

LuaPlayerInfo:getOwner() / LuaPlayerInfo:setOwner()
getOwner returns a LuaPlayerInfo, setOwner accepts a player name as a string.

Original issue reported on code.google.com by bkcon...@gmail.com on 9 Aug 2013 at 3:38

[GoogleCodeExporter]

Original comment by bkcon...@gmail.com on 9 Aug 2013 at 3:39

• Added labels: 019

[GoogleCodeExporter]

I made the following API changes for 019:

BfObject:getClassId() -> BfObject:getObjType()

BfObject:getLoc() -> BfObject:getPos()
BfObject:setLoc() -> BfObject:setPos()

The rest seem non-trivial and not particularly useful, so I'm relabeling the 
rest for 020

Original comment by bkcon...@gmail.com on 29 Aug 2013 at 8:21

• Changed state: Accepted
• Added labels: 020
• Removed labels: 019

[GoogleCodeExporter]

Mass priority downgrades for long-standing or not immediately important issues.

Original comment by bkcon...@gmail.com on 5 Dec 2013 at 6:11

• Added labels: Priority-Low
• Removed labels: Priority-Medium