merge interesting parts of minecraft-demo into develop about arcadia HOT 9 CLOSED

perhaps a unity.interop ns? I may have a few pull worthy things for that.

from arcadia.

destroy is already in unity.core. Anything that is useful on a daily basis should be in core and core should be useable is our approach, I believe.

@selfsame Your stuff is all amazing interop wrappers. Anything in particular you'd want to merge in? Any approach that can be generalized?

from arcadia.

@nasser I'm not seeing destroy:

from arcadia.

Just pushed up the api branch, my bad. https://github.com/clojure-unity/clojure-unity/blob/api/Assets/Clojure/Libraries/unity/core.clj#L263

from arcadia.

@nasser @timsgardner

Here's my current interop stuff with some comments:
https://gist.github.com/selfsame/6eb5c9c9f3c4d7aa5572

I'm also working on input interop:
https://gist.github.com/selfsame/8b88db25f1abd433bfe0

It only covers a fraction of the API, the new defwrapper macro looks great for straightforward API, but I'm really digging fn's that can accept sequential or Vector3

Also paging @OmerShapira, he has some vector overloading stuff in the works that I consider pretty vital

from arcadia.

Really solid stuff, @selfsame, especially the input stuff. Nice! Once we get 0.1 out and stable we'll work with you to get some interop libraries designed and merged in.

from arcadia.

closed with 1cce644

from arcadia.

got confused with #34 (now closed), this issue still open.

from arcadia.

also the conversation's drifting a bit from "merge interesting parts of minecraft-demo into develop"...

from arcadia.