What to do with 'official' extensions?

[0Hughman0]

Currently I have put cassini-deps in a separate repo, perhaps indicating my intention not to actively develop it too much.

Similarly, now we have the ipy_gui, which is made somewhat redundant because of jl_gui (although ipy_gui I think is compatible with old-school notebooks and possibly with embedded notebooks like in VS-code?).

Already having jupyter_cassini in a separate repo is sometimes kinda annoying.

I think maybe gui implementations should stay in this repo, although that does come with an obligation to maintain them.

Alternatively, I could make them both extensions. Currently, extend_project is defined in here, but could be defined in the jupyter_cassini repo. Perhaps that project should be renamed to cassini_jl_gui?

Part of me want to include cassini-deps as part of the library, but I'm not sure where I'd put it.

[0Hughman0]

As a minimum, should at least define an abstract gui class that I ensure has a header method and the correct __init__ signature for NotebookTiers.

[0Hughman0]

To properly implement cassini-deps, I need to hook into the Project setup_files(), currently there's no way for me to nicely make the folder for the dependencies to go into.

I think we need to provide some hooks for Project.

I suggest:

1. Before setup_files()
2. After setup_files()
3. Before launch()
4. After launch()

These could be lists that extensions can append to.

I think later adding some sort of resolver attribute which we delegate to for looking after getting TierClasses, which could allow for some interesting things down the line!

[0Hughman0]

Official extensions can be optional dependencies:

https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#dependencies-and-requirements

[0Hughman0]

They got moved into .ext