@neurolabusc and @cdrake , Now that the project has grown a bit, I think it would be best to separate the core niivue.js module into its own project. niivue.js contains all of the core image processing and rendering routines. It also imports some shaders and utility functions, so those would accompany niivue.js in its new repository.
What we currently have in hanayik/niivue is not sharable. Others can't import anything we have created easily. The code base has grown organically, but now that it is somewhat stable it would be good to separate things into modules that can be imported into other projects (either ours or anyone else's).
Here's my proposal:
move core niivue to https://github.com/niivue/niivue. This would be a module that anyone can import in order to use niivue for simple webgl2 medical image rendering. We can create basic demo html files with a canvas for easy developing like we currently have.
create https://github.com/niivue/niivue-web as a Vue/Vuetify user interface development repo. This would essentially be the current hanayik/niivue UI code base without niivue.js. niivue-web would import the niivue module as a dependency.
create https://github.com/niivue/niivue-desktop as an electron desktop application that could in time be developed into a more mature, full fledged visualisation tool for offline use. This would most likely mirror some features in current viewers such as MRIcroGL and FSLeyes. This would not be a quick project.
Use this issue to start any discussions we might want to have.
If you support this idea I will setup the new repos and fill them with the current niivue components (once separated). I will also put in some basic development helpers so that we can develop the core library with nice reloadable pages like we currently have with vue.
@neurolabusc and @cdrake , Now that the project has grown a bit, I think it would be best to separate the core
niivue.jsmodule into its own project.niivue.jscontains all of the core image processing and rendering routines. It also imports some shaders and utility functions, so those would accompanyniivue.jsin its new repository.What we currently have in
hanayik/niivueis not sharable. Others can't import anything we have created easily. The code base has grown organically, but now that it is somewhat stable it would be good to separate things into modules that can be imported into other projects (either ours or anyone else's).Here's my proposal:
hanayik/niivueUI code base withoutniivue.js.niivue-webwould import theniivuemodule as a dependency.Use this issue to start any discussions we might want to have.
If you support this idea I will setup the new repos and fill them with the current
niivuecomponents (once separated). I will also put in some basic development helpers so that we can develop the core library with nice reloadable pages like we currently have with vue.