This has been discussed a few times on the mailing list recently. The original "JS binding" was mostly just a quick and dirty engineering tool used to aid development early on. It was not maintainable and was never really intended to be a permanent or widely used interface. It was broken around the 0.7 release, and we have not had the opportunity yet to fix/replace it. But interest in using BokehJS as a pure JS library has increased recently, and so providing a first-class interface to BokehJS is a priority for us. However, the team is also resource-constrained and there are only so many hours in the day.
I hope to have something minimal in place for 0.8 next week, with more sophisticated integrations with React, Angular, etc. to come later. If You can follow the GH issue here:
Any input, suggestions, or contributions from experienced JS devs would be extremely welcome (for reference, I was completely new to JS and web dev before Bokeh, I would very much welcome some experienced voices weighing in and helping).
On Feb 12, 2015, at 7:33 AM, Patrick Brockmann <[email protected]> wrote:
Any explanation on why examples such as marker
or others from http://bokeh.pydata.org/en/latest/docs/dev_guide.html#bokehjs-examples
does not work when you replace
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/87796f20-baa8-4f12-815a-e6df5ff1ccc6%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.