-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JupyterLab Heuristic Evaluation #63
Comments
Thank you very much for this work @grey280, @jabumeri, @JDLEarley, @emilythefan, and @Nastraughn! These type of insights are invaluable to improve our product. Can you please give the output of |
And I use "our" in "our product" here to include you as well, this is a community project after all 😉. |
Been learning to use
but did occasionally switch to the 'base' state, which was just:
@jabumeri, @JDLEarley, I believe you two contributed most of the screenshots, what do your setups look like? |
Thank you @blink1073! We are happy to be a part of this project and look forward to assisting the community. I was running JuptyerLab 2.1.0 with no extensions. |
Yes, thank you @blink1073! Your excitement about our work thus far is encouraging and to echo Justin, we're excited to be part of this project.
I have primarily been running JupyterLab with the enable extensions and have not switched to the base version like Grey. |
Thanks @grey280, @JDLEarley, @jabumeri. The filetree extension was what I was most interested in, since we may decide to replace the stock filebrowser with that one and this feedback can help guide that decision. |
I’m part of a group from UC Irvine, working on designing a new file browser experience. As part of this work, we’ve been doing a lot of research on the current state of JupyterLab.
While it’s mostly focused on the file browsing/managing experience, the heuristic evaluation we’ve completed could be of some use to the community, so we’re sharing it here.
At the moment, I’m linking to this as stored in my personal .github.io repo, for lack of a better place, but are hoping @tgeorgeux can help us get this stored somewhere more appropriate/permanent for use by the Jupyter community.
Here’s hoping this is helpful, and thank you for your time.
Oh, and for reference, the group consists of @jabumeri, @JDLEarley, @emilythefan, @Nastraughn, and myself.
The text was updated successfully, but these errors were encountered: