Lua vs Corona in OOP "who owns who" any consensus?

Solar2D Lua Language
#1

Just curious: anyone got a feel for which OOP style of “who owns who” is more prevalent?  (primarily since messing with Corona metatables is verboten, figure most end up with some such approach eventually)

For example, here’s some commonly encountered approaches, if easier to just say “I do #1”.

Note, i don’t much care if some “framework” or just DIY involved, just the resulting \ *structure between * Lua and Corona objects.  If you want to share any “whys” you prefer one over the other, bonus!

  1. just “tag” display objects with extra properties/methods, no metatable fiddling

    fe:  aDisplayObject.someCustomProperty = “foobar”

    fe:  aDisplayObject.someCustomFunction = function(self,params) end

  1. create “real” (metatable-based) Lua classes, display object “owns” lua object

    fe:  aDisplayObject.myLuaObject = SomeLuaClass:new()

  1. create “real” (metatable-based) Lua classes, lua objects “owns” display object

    fe:  aLuaObject.myDisplayObject = display.newSprite(…

  1. keep them separate and proxy them to each other “somehow” without “polluting” either

    fe:  theListOfAllDisplayObjects[“fish”] = display.newSprite(…whatever…)

    fe:  theListOfAllLuaObjects[“fish”] = FishClass:new(…whatever…)

    – implied: they could then proxy each other by same-named key

    – or to any degree of ‘more elaborate’:

    fe:  theProxyTable[aLuaObject] = aDisplayObject

  1. some other arrangement?

cheers

#2

I do #4, mostly out of habit, and because I learned that way before I learned how to do metatables.

Trying to force myself to use more intelligent metatable design in future projects.

#3

I’ve done #4 mostly in the past but I’m experimenting with method #1 now.  I haven’t run into any major issues yet but I have been careful not to overwrite any of the existing functionality.

#4

I do #4, mostly out of habit, and because I learned that way before I learned how to do metatables.

Trying to force myself to use more intelligent metatable design in future projects.

#5

I’ve done #4 mostly in the past but I’m experimenting with method #1 now.  I haven’t run into any major issues yet but I have been careful not to overwrite any of the existing functionality.