further to this discussion where you mention community support, can we have a bit of direction on how to develop for BokehJS?
Case study: I’d like to modify the autocomplete editor for datatables to enable remote ajax-based autocomplete. I thought I could simply expand /bokehjs/src/vendor/slickgrid/editors with this autocomplete editor modified for jquery ajax autocomplete (this solution works in a plain slickgrid application), however I then realised I don’t know how to surface that in Bokeh as the js code in github is in coffeescript, and I can’t even locate BokehJS in my local bokeh directory. Clearly I have a limited understanding on the development process…
Can we have a bit of guidance on how to start from a modification of the /bokehjs/src/vendor of master, to its incorporation in bokeh proper?
further to this discussion where you mention community support, can we have a bit of direction on how to develop for BokehJS?
Case study: I’d like to modify the autocomplete editor for datatables to enable remote ajax-based autocomplete. I thought I could simply expand /bokehjs/src/vendor/slickgrid/editors with this autocomplete editor modified for jquery ajax autocomplete (this solution works in a plain slickgrid application), however I then realised I don’t know how to surface that in Bokeh as the js code in github is in coffeescript, and I can’t even locate BokehJS in my local bokeh directory. Clearly I have a limited understanding on the development process…
Can we have a bit of guidance on how to start from a modification of the /bokehjs/src/vendor of master, to its incorporation in bokeh proper?
You should start with http://bokeh.pydata.org/en/latest/docs/dev_guide.html. This should give you the basics, but not the complete picture. The source code of bokehjs is located in bokehjs/src/{coffee,js,less}. Besides this, there is also bokehjs/src/vendor and dependencies pulled in from npm (see dependencies section in bokehjs/package.json). In therory, we should only have npm dependencies, but some need special attention and they land in vendor. However, we don’t implement any new features in vendor, only apply integration patches. If possible, you should implement new features in bokehjs, in this case somewhere in bokehjs/src/coffee/widget. Alternatively, especially if you have to modify slickgrid, you should make the modifications upstream, wait for a release and upgrade slickgrid in vendor, maintaining our changes. Unfortunately, slickgrid isn’t currently maintained, so this process won’t work. Maybe we should fork slickgrid under bokeh organization and continue development there.
Mateusz
–
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].
Unfortunately, slickgrid isn’t currently maintained, so this process won’t work. Maybe we should fork slickgrid under bokeh organization and continue development there
bokeh-slickgrid is a great idea. Just opened an issue on this.
To note a user named 6pac has done some work keeping slickgrid up to date in his own fork, with the latest work done a few months ago
···
On Friday, 25 September 2015 10:36:55 UTC+1, mateusz.paprocki wrote:
further to this discussion where you mention community support, can we have a bit of direction on how to develop for BokehJS?
Case study: I’d like to modify the autocomplete editor for datatables to enable remote ajax-based autocomplete. I thought I could simply expand /bokehjs/src/vendor/slickgrid/editors with this autocomplete editor modified for jquery ajax autocomplete (this solution works in a plain slickgrid application), however I then realised I don’t know how to surface that in Bokeh as the js code in github is in coffeescript, and I can’t even locate BokehJS in my local bokeh directory. Clearly I have a limited understanding on the development process…
Can we have a bit of guidance on how to start from a modification of the /bokehjs/src/vendor of master, to its incorporation in bokeh proper?
You should start with http://bokeh.pydata.org/en/latest/docs/dev_guide.html. This should give you the basics, but not the complete picture. The source code of bokehjs is located in bokehjs/src/{coffee,js,less}. Besides this, there is also bokehjs/src/vendor and dependencies pulled in from npm (see dependencies section in bokehjs/package.json). In therory, we should only have npm dependencies, but some need special attention and they land in vendor. However, we don’t implement any new features in vendor, only apply integration patches. If possible, you should implement new features in bokehjs, in this case somewhere in bokehjs/src/coffee/widget. Alternatively, especially if you have to modify slickgrid, you should make the modifications upstream, wait for a release and upgrade slickgrid in vendor, maintaining our changes. Unfortunately, slickgrid isn’t currently maintained, so this process won’t work. Maybe we should fork slickgrid under bokeh organization and continue development there.
Mateusz
–
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].
In therory, we should only have npm dependencies, but some need special attention and they land in vendor. However, we don't implement any new features in vendor, only apply integration patches. If possible, you should implement new features in bokehjs, in this case somewhere in bokehjs/src/coffee/widget. Alternatively, especially if you have to modify slickgrid, you should make the modifications upstream, wait for a release and upgrade slickgrid in vendor, maintaining our changes. Unfortunately, slickgrid isn't currently maintained, so this process won't work. Maybe we should fork slickgrid under bokeh organization and continue development there.
I think a maintained fork of slickgrid would be welcomed by many,
including myself.
Cheers,
Steve
···
On 09/25/2015 09:02 AM, Bryan Van de Ven wrote:
In therory, we should only have npm dependencies, but some need special attention and they land in vendor. However, we don't implement any new features in vendor, only apply integration patches. If possible, you should implement new features in bokehjs, in this case somewhere in bokehjs/src/coffee/widget. Alternatively, especially if you have to modify slickgrid, you should make the modifications upstream, wait for a release and upgrade slickgrid in vendor, maintaining our changes. Unfortunately, slickgrid isn't currently maintained, so this process won't work. Maybe we should fork slickgrid under bokeh organization and continue development there.
In the past when I talked about with Brian Granger (Jupyter project), he
indicated interest in working on QGrid, the Quantopian fork/enhancement of
SlickGrid:
-Peter
···
On Fri, Sep 25, 2015 at 9:35 AM, Steve Waterbury <[email protected]> wrote:
On 09/25/2015 09:02 AM, Bryan Van de Ven wrote:
In therory, we should only have npm dependencies, but some need special
attention and they land in vendor. However, we don't implement any new
features in vendor, only apply integration patches. If possible, you should
implement new features in bokehjs, in this case somewhere in
bokehjs/src/coffee/widget. Alternatively, especially if you have to modify
slickgrid, you should make the modifications upstream, wait for a release
and upgrade slickgrid in vendor, maintaining our changes. Unfortunately,
slickgrid isn't currently maintained, so this process won't work. Maybe we
should fork slickgrid under bokeh organization and continue development
there.
We should absolutely do this.
Big +1!
I think a maintained fork of slickgrid would be welcomed by many,
including myself.
Ah, that would make sense. I was unaware of that one. I spoke too
soon, anyway -- I see that (even according to the author of slickgrid)
there are a *lot* of forks of slickgrid on github, so since I might be
using it in other application contexts than ipython, I would probably
want to use one of the other ones ... thanks, Peter!
In therory, we should only have npm dependencies, but some
need special attention and they land in vendor. However, we
don't implement any new features in vendor, only apply
integration patches. If possible, you should implement new
features in bokehjs, in this case somewhere in
bokehjs/src/coffee/widget. Alternatively, especially if you
have to modify slickgrid, you should make the modifications
upstream, wait for a release and upgrade slickgrid in
vendor, maintaining our changes. Unfortunately, slickgrid
isn't currently maintained, so this process won't work.
Maybe we should fork slickgrid under bokeh organization and
continue development there.
We should absolutely do this.
Big +1!
I think a maintained fork of slickgrid would be welcomed by many,
including myself.
In the past when I talked about with Brian Granger (Jupyter project), he
indicated interest in working on QGrid, the Quantopian fork/enhancement
of SlickGrid:
