You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think we should try to create a new directory structure for the server side code just for type-extensions - extending the server with any 3rd-party code is a wider issues IMO, and can be handled in a more generic (and just as "easy") way.
At the end of the day, to support 3rd-party code we need to have a way for the 3rd-party to easily add a jar(s) to the classpath, or to install a new python library (which will be lreachable via java/jpy).
See discussion: #1468
Extension needs a directory structure specified, ie:
Not too sure what the install command/process would be yet, that is something to discuss here. But in terms of the structure:
/init
folder for initialization scripts. In the matplotlib case, this would need a script in grpc-api to pip install matplotlib and a script in py-env to extend matplotlib.figure.Figure with the getDeephavenObject method. We could add subfolders for any other initialization scripts we may need (eg. for other containers)/ui
folder for Web UI dashboard plugins. In the matplotlib case, the MatPlotLibPlugin handles it.The text was updated successfully, but these errors were encountered: