Deprecate ReactTemplate, IDOM pane and Viewable.app #4293
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After some discussion I've decided to execute a few deprecations ahead of the 1.0 release.
For templates I've simply decided that we do not need 5 different ListTemplate implementations and multiple grid template implementations. Deprecating some of these implementations will allow us to better focus on styling existing templates and reduces the maintenance burden.
Here are the deprecations I'm suggesting:
IDOM
pane: We only support version 0.24 currently which is very old. Since we do not have a maintainer who could update it and Reacton fills the same niche I've decided to remove it. It may be it could be re-added later in apanel-idom
package but without anyone requesting support I think the right decision is to remove it.ReactTemplate
: TheReactTemplate
is overall pretty nice BUT the naming is terrible (it's built on top of a React library but it doesn't actually allow you to use React or anything so really that's an implementation detail. Secondly, theFastGridTemplate
lets you do the exact same thing but looks prettier.Viewable.app
: The.app
method allows starting a server in Jupyter and then embedding it as an iframe. This relies on the port being accessible and to specify thenotebook_url
. This is brittle without much benefit at all because you already get interactivity in a notebook without running a server. I've left the function that will let you do the same thing but we don't need a method on all objects to do this.Please chime in with thoughts and/or objections.
Ping @MarcSkovMadsen, @jbednar, @maximlt, @hoxbro