I’m currently using the napari
Viewer launched from a notebook to load some data, do some annotation, grabbing the results in the notebook, doing some simple computation in the notebook and then saving the results to disk. I call this workflow
here's a notebook with instructions in markdown, please follow them. While this is a catchy name, I would like to move to a world where the user’s actions can be guided more interactively and maybe have one less thing to open. I can think of some options, but they all seem a little weird:
build a PyQt app that uses napari as a module and pops up a
viewerthat is controlled by the app. Any additional interaction like dialog windows or computation is done in/from the parent PyQt object.
viewer. I have done this for another project and like it OK, but it’s sort of a no-no for a few reasons. First of all, it’s hard to maintain something like this at the current stage of napari development and second, @sofroniewn told me not to do it.
- plugins. plugins will save us all, but that conversation only really starts once the interface covers all the bases for your functionality, and even then it’s not clear how you would modify user interaction (like enforcing a series of GUI steps) or running some code that is useful for me but no one else.
So what to do? I’d like to put the work into a tool that can fit into the
napari vision for the future…