-
Notifications
You must be signed in to change notification settings - Fork 121
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
UI questions #29
Comments
The top right one refreshes the list of configurable nbextensions, by making a new call to the JSON handler without reloading the whole page. Perhaps it should have a tooltip of some kind to make this clearer?
The filter works by looking through a set of tags which are sorted by type, and are created for each nbextension as the list is loaded. Each one has an auto-created
The name ones should be created automatically for each nbextension, so that typing any word in the name should make them appear - is that not what's happening for you? The idea behind the tag ones is for them to function essentially as keywords in the way you describe, except that I couldn't think of a way to automatically extract them from the description, so just made them explicitly set for now. I was also thinking they could also be used for pseudo-categories liek the old |
sorry, missed that there were two reload questions:
The one on the parameters section header effectively resets all the parameters to their defaults. It actually removes all the parameter tags from the relevant config file, so that the nbextension should go back to using the defaults from the javascript implementation. This is because the |
Does any of that make sense? Perhaps it would be worth updating the docs or adding some tooltips or other explanatory text to the page? |
Thanks for the explanation. Makes sense. The reload button is not shown in the screenshot. I think it would be sufficient it there is a toolbar explaining it reloads the extensions list. For the reset, maybe it would be With the filter, I think it makes sense. I was more asking myself if it is really helpful like this. Personally, if I know the name of the extension, I don't need to filter. Otherwise I am looking for something, then I am probably looking for a keyword in the description. As we have online documentation on readthedocs, I guess there is no need to overdesign things. Maybe a link to the documentation... |
Right, I'll add some tooltips.
True in most cases, I guess it's only useful if you can remember one word in the name, but not the rest, but that seems pretty unlikely on reflection. Perhaps it'd be best to remove the name tags in favour of better keyword tags.
True, the keywords are/would be the main useful feature, and they're not properly implemented yet. I guess it would also be possible to take words from the description to auto-create tags, that sounds a pretty useful idea. I'll have a think... |
I just tried the reload button: Does not work for me. Reloading the page using CTRL-R shows my added/removed extension. |
To be honest, I haven't done much testing, so it may not actually work correctly, or at all. I'll have to investigate... |
Ha, yes, on further investigation, I added the button, but failed to actually connect it to a callback... |
So, I think I've addressed these issues in #31 - let me know if you get a chance to take a look 😄 |
|
@juhasch I've had a go at implementing name & description text searching in #34 - is that the kind of thing you meant? I guess ideally it would also search readmes, but they're currently only lazy-loaded when needed, and it could really up traffic to load all of them every time the page loads, so I haven't bothered for now... |
Cool, this is really nice! |
I think we can close this now 🥇 |
I was looking at the configuration page and had some questions:
The
section
seems to be useful. I don't understandtag
andname
seems to be not very useful, as you have to add any extension by hand. Is there a chance to select several extensions at once by name or by keywords in the description ?The text was updated successfully, but these errors were encountered: