• blocked by deathbeds/jupyterlab-starters#46

• merge all outstanding PRs
  • #82
• ensure the versions have been bumped (check with doit)
• ensure the CHANGELOG is up-to-date
  • move the new release to the top of the stack
• validate on binder
• validate on ReadTheDocs
• wait for a successful build of main
• download the dist archive and unpack somewhere (maybe a fresh dist)
• create a new release through the GitHub UI
  • paste in the relevant CHANGELOG entries
  • upload the artifacts
• actually upload to npm.com, pypi.org

  cd dist
  twine upload *.tar.gz *.whl
  npm login
  npm publish deathbeds-*-$VERSION.tgz
  npm logout

• postmortem
  • handle conda-forge feedstock tasks
  • validate on binder via simplest-possible gists
  • bump to next development version
  • bump the CACHE_EPOCH
  • rebuild yarn.lock
  • update release procedures with lessons learned

Looks like the WXYZ JSON Schema Form Version is still indicated 0.4.0 on the 0.4.1 release.

https://github.com/deathbeds/wxyz/blob/v0.4.1/src/ts/wxyz-json-schema-form/src/index.ts#L2

• update (test?) for newest rjsf #32
• build, upload artifacts in CI #34
• verify on binder
• tag
• upload to npm/pip
• badge
• bump version for next dev cycle

Tasks

• update dependencies
• update locks
• reorganize build
• remove extra build steps
• update robot tests
  • consider robotframework-jupyterlibrary
    • moved to #53
• update CI
• update docs
  • README
  • CHANGELOG
  • CONTRIBUTING
• validate binder
  • with bqplot on page, etc. for d3
  • with jupyterlab-classic
    • moved to #52
• tag
• release
  • pypi
  • npm
• conda-forge
• gh-pages

References

• was blocked by deathbeds/jupyterlab-starters#48
  • https://pypi.org/project/jupyter-starters/1.0.0a0/#history

References

• blocked by deathbeds/jupyterlab-starters#87
  • blocked by deathbeds/jupyterlab-starters#92

Motivation

• a number of features have been fixed
• jupyterlab-starters has already handles the CSS conflicts with the (not sharedPackage) rjsf from core

Assuming that it is possible to get a UI that looks like the example here:

https://dgothrek.gitlab.io/ipyaggrid/guide/customize.html#user-params

Specifically:

How would we define a Python panda table/dict to do the same kind of thing with wxyz_datagrid?

A related question: is there a way to add some event callbacks?

E.g, if the user clicks on a row/col table cell, can we get a callback event in Python?

The use case would be display in some kind of property sheet UI some information pertaining to the table selection.

Goal

• figure out a data structure (might be text) for the output of

$> git log --all --decorate --oneline --graph

* 386ca15 (HEAD -> add-git-tree-grid, origin/add-git-tree-grid) resolve locks
| * fecc708 (origin/add-qfd-grid-example, add-qfd-grid-example) resolve
| * b083871 relock
|/  
* c0064c5 (tag: v0.5.0, upstream/master, master, fix-doit-lab) Check Lab 3.0.5, Preflight release (#55)
* 9645f1c Use myst-nb for docs (#54)
| * 0e0bb02 (upstream/gh-pages) Delete CNAME
| * 3a8fe63 wxyz 0.5.0 c0064c5
| * b3b2360 initial commit
| * a4c740e (origin/use-myst, use-myst) more work on myst output
| * 21d0f49 some tweaks for docs
| * b264e59 start trying myst-nb
|/  
* 14e8111 Docs and dependencies for wxyz_notebooks, third-party packages for demo/testing (#51)
| * dde7405 (origin/fix-docs-and-deps, fix-docs-and-deps) update spelling
| * ecbffef fix integrity (don't check for npm package names)
| * 432ac9c some docs for wxyz_notebook, add extras
| * a4f6ace re-lock envs with new demo deps
| * 30c9de7 update readme, tpot deps
|/  
* e0c2739 (fix-editor-undo) JupyterLab 3 Support (#50)
* 5bda783 (tag: v0.4.2) Decomission azure, improve github actions (#49)

• add a grid renderer that can draw the output
  • initially as monospace text
  • eventually pretty lines and symbols on canvas
  • some cute things for heads, tags, branches
  • maybe render LabIcons down to canvas
• include in a demo
• test it

Design ideas

• it should be possible to use the absolute width of the ascii art to make a fairly good, consistent line drawing where the | would line up with its parent

This is one of the last hold-outs on azure. Let's move it over to GHA before the Lab 3 push (#42).

• #45 restored parity with azure
• #46 starts making some optimizations for file structure (keep/appease azure and gha)
• make ci.yml source of truth for lock creation, etc., update conda-lock behavior, remove azure
• do better version validation, cut a 0.4.2 release to fix #47

After the next update of robotframework-jupyterlibrary, it may make sense migrate to that, especially if some of the JSON configuration lands.... and maybe some of the client-specific widget integrations.

References:

• #42
• #52
• robots-from-jupyter/robotframework-jupyterlibrary#29
• robots-from-jupyter/robotframework-jupyterlibrary#26

#51 added jupyterlab-classic but it breaks pretty hard at the widget loading level.

If it's low-effort to support, if not test, we should, but doesn't block #42

Elevator Pitch

Offer as many of the wxyz packages for jupyterlite as possible.

Proposed Solution

• review dependencies, optimize for noarch or pyodide-compatible technologies
• split labextension distributions from kernel components a la deathbeds/ipydrawio#63 (comment)
• add a lite build to docs site

Challenges

• dvcs will be particularly challenging: a dulwich driver might be a possibility

These are likely still hanging around from 0.5.0, but should just get included into _static or something.

This is the last planned JupyterLab 2-compatible release.

Notes:

• lays groundwork for pypi-distributable extensions on JupyterLab 3 (#42)

Tasks:

• #45 migrate build/test infrastructure to github actions (for #44)
• #46 unifies versions between python/javscript packages (for #47)
• #49 turn off azure pipelines
  • changelog
• docs no significant changes needed
• tag
• publish
  • pypi
  • npm
  • conda-forge conda-forge/jupyter-wxyz-feedstock#1

Collecting some thoughts here of other alternatives to mention. They should at least support lab 3 to be recommended.