-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Getting started is challenging #228
Comments
I wrote this issue up rather quickly yesterday, and today I'm feeling paranoid that it reads as rather blunt/abrupt, or that I'm expecting you to do something. I'm not expecting anything, just trying to be helpful - apologies if the original description doesn't come across that way. :-) |
Hi! Firstly thank you for the clarification message. I've no problem with your original but I really appreciate the kindness and know exactly what you mean in feeling how you felt. Text always seems to be a bit more ambiguous without a tone of voice bundled with it. Unfortunately I don't have the time to spend making a nice getting started guide (at least for a while). I was kind of hoping that having the real working demo project and the examples in the readme would be enough, but I can see how that actually relies on quite a bit of implicit knowledge. Which is a perfect segue to the issue you're seeing and the questions you're asking about. The implicit knowledge required there is pure Scala.js knowledge, and not scalajs-benchmark specific. I think you'd have the same problems with any other lilbrary... which I'm sure provides exactly zero comfort to you now haha. Let me do my best:
There's no One Way for running Scala.js stuff. For short and sweet projects like this demo (and the scalajs-react ghpages site for another example), I just have a few static html files, and a little python server to serve both those files and the Scala.js-generated JS files. For larger projects I use something like http4s, or even a servlet + Jetty. There are some sbt plugins to make it nice and pleasant, (
Yeah you've got to expose some kind of function, which you then call from a little inline
Nah no need to export a module. You're gonna laugh when I tell you this but I think the problem you're having is that your Now all of that aside, not to be rude or anything but I've got tons on so I can be a bit infrequent in checking in on OSS issues. If you don't mind a delay then np, but you'd be able to get immediate feedback if you check out the Scala.js gitter. From what I've seen they're pretty nice and friendly, and pretty quick to respond too. I hope that helps! |
In response to japgolly#228. I got it working and thought I'd try and help the next person. :-)
Hi, There were two problems:
I've submitted a PR for your consideration that may help the next person: #229 Thanks again, Dave |
Hello!
This looks like a great project ...but I found it difficult getting something simple up and running and gave up. The details in the readme seem to be inadequate and the arrangement of the demos/examples is too involved for a quick start.
Examples:
build.sbt
arrangement.@JSExportTopLevel("main")
- I should have known about that one but I still tripped over it.Doing the prescribed minimum for me produces:
Should I be exporting modules? The HTML file examples suggest not?
I'll have another go some other time, just thought the feedback might be useful as it may be a barrier to adoption. This is what I did (nothing clever, just followed/interpreted the readme):
PurpleKingdomGames/indigo@ea622ea
All the best,
Dave
The text was updated successfully, but these errors were encountered: