![]() Darian: proposal -> use some of these calls to do "BBQ bonanza/triage" -> find where the issue resides to help fixing this Adjacent: Tania proposed this docs reorg (JupyterLab) Tania: could we look at codetours for example? Provide examples of extensions with the panels/layout explanations (maybe in the readme in Lumino) Ely: some helpful information was around panel, CSS, historical context (from Jason), panels needed for a particular situation Ely: had plenty support from Jason when walking this path Darian: is happy to offer office hours to help folks orient around the codebase Examples of manual-testing scripts we are working on Most recent Zoom audit in JupyterLab and findings Example that sparked this conversation ![]() Discussing depth-levels in JupyterLab/lumino codebases Add "office hours" help for under agenda and make a queue of issues to pull from Shadow DOM needs more research and/or a binder to test it in #JUPYTERLAB THEMES CODE#If we have time for office hours, can we chat about tab focus indicators and/or tab traps in code cells? Office hours follow up (from last meeting)? low hanging fruit good first issue for new contributors Some related work with consistency of CSS variables between background color and text color: Please report any issue if you find any, thanks! Happy to help in the `jupyter/notebook` or `jupyter/accessibility`. There is no development happening in `jupyterlab/retrolab` anymore, improvements and fixes should be done in JupyterLab and Notebook 7. #JUPYTERLAB THEMES UPDATE#Now that the CodeMirror 6 update is available in a Notebook 7 pre-release it should be possible to make this audit with a document-oriented notebook UI. ![]() Closed the old issue on the RetroLab repo that was about doing an accessibility audit on the RetroLab UI. It includes the switch to **CodeMirror 6** that landed in JupyterLab: A new pre-release of Notebook 7 is available: # JupyterLab Accessibility Goals Meeting Notes ![]() > * widgets have virtual dom and may have react. > * import Lumino Widgets (EVERYTHING IS A WIDGET) as the framework for our objects Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).īy default, the jlpm run build command generates the source maps for this extension to make it easier to debug using the browser dev tools.> * Extension (Package) -you can get this from npm/pip With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. # Watch the source directory in one terminal, automatically rebuilding when needed You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension. # Rebuild extension Typescript source after making changes # Link your development version of the extension with JupyterLab #JUPYTERLAB THEMES INSTALL## Clone the repo to your local environment # Change directory to the jupyterlab_theme_sophon directory # Install package in development mode The jlpm command is JupyterLab's pinned version of ![]() Note: You will need NodeJS to build the extension package. Install pip install jupyterlab_theme_sophon ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |