-
Notifications
You must be signed in to change notification settings - Fork 527
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
Project Description - Simple to Embed: JavaScript Support #95
Comments
If it's useful to see the code that I've got, it's here: https://github.com/nodatime/nodatime/blob/335de575f51912a45adf70fcef6a8a5dcd09595f/src/NodaTime.Web/wwwroot/js/trydotnet.js Try not to laugh too hard ;) |
@jskeet , @LadyNaggaga Now that we publish js api is worth reviewing this issue. |
Definitely very happy to give this a go when I can, although it won't be for a couple of weeks, I expect :( |
Is there documentation for using the JS API from a regular web application? Most of the docs I've seen are for the |
This isn't documented yet. |
Hi, @colombod is there any news on this, I would love to use trydotnet, but because the trydotnet.js is closed for public its currenlty quite hard, the only way is really to do something what jskeet did. |
Same deal, even basic docs on how one could use the online .Net interactive on their own docs site would be greatly appreciated. |
Suggestion from @jskeet
Reference: Product Roadmap Review
Feedback: For Noda Time, I wrote a horribly hacky bit of JavaScript for the various interactions with the server. None of this was complicated, or it wouldn't exist - my command of JavaScript is pretty dire. But it makes sense to avoid wheel reinvention: the Try.NET project could provide the JavaScript to make all of this work with very little effort on the part of the site developer wanting to embed Try.NET.
The text was updated successfully, but these errors were encountered: