I think the heavy lifting will be on the Notebook team to make the necessary upgrades.
(and a final follow-up step, which is clearing up inevitable confusion that will happen when things change for our users in issues, discourse, etc) I would imagine this last bit is the least amount of work. Making the switch itself (which I think means releasing in repo2docker, then deploying to ).
#File browser open in terminal how to
Signaling to our users somehow that this switch will be coming (maybe with a banner image on for a month or two) with documentation about how to get the behavior they'd want Evaluating the state of "Jupyter Notebook 7.x" to make sure that there aren't important regressions for our users (I suspect that the jupyter notebook team will make this evaluation themselves, so maybe this just means participating and watching discussions in that space) I think there are three major areas of work for this, similar to what needed to happen for the JupyterLab UI change: We could also explore making retrolab the default interface *before* the release of Notebook v7, if the switch will be inevitableĪ lot of people because this is suggesting that we change the default behavior of this tool, and thus - most people will just go with the default.
if it does point to a specific file, use the Jupyter Notebook interface. if somebody shares a Binder link that doesn't point to a specific file, use JupyterLab as the interface We could explore using a default interface depending on context - for example: We could keep using JupyterLab as the default interface. It is a simpler interface that is more well-matched what I suspect many people want to do when "sharing a notebook on Binder" It more closely matches the primary UX that Binder users have had for the last few years If and when that happens, I think that we should consider switching the default interface for repo2docker (and ) back to use this single-document mode instead of the full-blown JupyterLab interface. AKA, in the next major release of the notebook (I believe v7), typing `jupyter notebook` will launch **retrolab**. There's a good discussion about the (), and one potential outcome (described in ()) suggests that **the Jupyter Notebook may morph into retrolab**. (note, I don't know whether there is buy-in from people to do this, so don't con … sider this a strong proposal but more like a continuation of the discussion in without trying to disrupt the conversation that is here)
0 kommentar(er)
