Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not work with webplayer #4

Closed
grav opened this issue Aug 24, 2014 · 3 comments
Closed

Does not work with webplayer #4

grav opened this issue Aug 24, 2014 · 3 comments

Comments

@grav
Copy link

grav commented Aug 24, 2014

Had to switch platform (File -> Build Settings...) to PC, Mac & Linux Standalone to get a connection to the repl, since the default Web Player does not support incoming TCP connections (with good reason, I suppose).

Took me some time to notice the small warning and figure it out. Maybe this should be stated in the README?

So, I got (+ 2 2) evaluated, and I managed to create a UnityEngine.GameObject. Apart from this, I have no clue about what I'm doing ;-) Looking forward to some more documentation :-)

@nasser
Copy link
Contributor

nasser commented Aug 24, 2014

Good catch. There are a couple of build settings that need to be in place for it to work, actually, including setting the .NET API Compatibility to not be .NET Subset. These should be in the README, and we're going to want a way to automatically configure this stuff.

Exciting that you got a REPL up and running! Did you do it from Emacs or Sublime?

We are working on better wrappers for the interop stuff (we already have a pretty solid get-component implementation) and a way to write components.

@grav
Copy link
Author

grav commented Aug 25, 2014

I just used the ruby-script from the shell directly. I wanted to do it with Emacs (since I'm normally using nrepl/cider), but I'm not sure how Inferior Lisp works?

@nasser
Copy link
Contributor

nasser commented Aug 25, 2014

@timsgardner exclusively uses an Emacs/Inferior Lisp setup and its pretty solid. He'd be able to answer better, and we should document that.

@nasser nasser closed this as completed Apr 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants