[sage-devel] Re: help menu in jupyter notebook

On Saturday, April 27, 2024 at 2:30:00 PM UTC+9 Kwankyu Lee wrote: The app provides access to a local copy of the documentation stored inside the application bundle. The files are reorganized slightly to remove duplication and then compressed with gzip. The app views the files using

[sage-devel] Re: help menu in jupyter notebook

The app provides access to a local copy of the documentation stored inside the application bundle. The files are reorganized slightly to remove duplication and then compressed with gzip. The app views the files using cocoserver , which provides a

Re: [sage-devel] Re: help menu in jupyter notebook

Yes, I was only talking about really just running Sage locally. - Marc. On Friday, April 26, 2024 at 7:54:38 PM UTC-5 Nils Bruin wrote: > On Friday 26 April 2024 at 15:44:22 UTC-7 marc@gmail.com wrote: > > I don't see what difference the choice of port makes to a user. It is not >

Re: [sage-devel] Re: help menu in jupyter notebook

On Friday 26 April 2024 at 15:44:22 UTC-7 marc@gmail.com wrote: I don't see what difference the choice of port makes to a user. It is not possible to guarantee that the same port will always be used, since ports are assigned on a first-come first-served basis. Consequently it is not

Re: [sage-devel] Re: help menu in jupyter notebook

The jupyter server operates on the loopback interface which has IP address 127.0.0.1 and IP name localhost. The cocoserver uses that same interface. Jupyter tries to get port and if that is busy it hunts for a nearby port that is not in use. The cocoserver uses an arbitrary

Re: [sage-devel] Re: help menu in jupyter notebook

On Friday 26 April 2024 at 12:29:14 UTC-7 marc@gmail.com wrote: There are other issues with viewing local documentation files in a browser. On Ubuntu, Chrome and Firefox are packaged as snaps. A snap is not allowed to read a file:// url which is not in the user's home directory. As long

Re: [sage-devel] Re: help menu in jupyter notebook

Yes, I meant MB. Thanks. There are other issues with viewing local documentation files in a browser. On Ubuntu, Chrome and Firefox are packaged as snaps. A snap is not allowed to read a file:// url which is not in the user's home directory. As long as sage is installed in the user's home

[sage-devel] Re: help menu in jupyter notebook

On Friday 26 April 2024 at 06:53:28 UTC-7 marc@gmail.com wrote: I have a suggestion to improve the situation, which is to do what the Sage_macOS app does. The app provides access to a local copy of the documentation stored inside the application bundle. The files are reorganized slightly

[sage-devel] Re: help menu in jupyter notebook

Another drawback of linking to online documentation is that the online documentation is always for the current release version of Sage, not the Sage that the user happens to be running,. I have a suggestion to improve the situation, which is to do what the Sage_macOS app does. The app

[sage-devel] Re: help menu in jupyter notebook

Only to put a note in the installation instructions somewhere, along the lines: If the URL in your browser reads /foo/bar/notebooks/whatever.ipynb, then /foo/bar/kernelspecs/sagemath/doc/html/en/index.html will take you to the local documentation. I have bookmarked a few such links, which is

[sage-devel] Re: help menu in jupyter notebook

On Wednesday, April 10, 2024 at 1:30:21 AM UTC+9 Denis wrote: At some point the help menu in jupyter notebooks started pointing to doc.sagemath.org instead of the locally built documentation. I wouldn't mind having a configuration option not to build the documentation, in which case, of

[sage-devel] Re: A menu for the notebook

I wasn't expecting to like it, but I think I could very much get used to it, especially as the number of options seems to increase. It looks like the menu vs. button mode could almost entirely be handled via css too. - Robert On Mar 15, 2007, at 12:03 PM, Timothy Clemans wrote: There

[sage-devel] Re: A menu for the notebook

If lots of options get added then menus are unavoidable, but currently I don't think the options presented in the notebook take up real estate that would otherwise get good use. Avoiding drop-down menus has the advantage that all options are immediately visible. Having to first drop down the menu

[sage-devel] Re: A menu for the notebook

Quote me on this: The SAGE notebook will NEVER have multi-level dropdowns. If I ever suggest it, remind me of this. If I persist, throw something at my head. On Fri, 16 Mar 2007, Nils Bruin wrote: If lots of options get added then menus are unavoidable, but currently I don't think the

[sage-devel] Re: A menu for the notebook

Then can there please be a mode I can go into merge the second menu with the first? Remember everyone that menu is pure css and there are accesskeys that can added for each item. On 3/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quote me on this: The SAGE notebook will NEVER have

[sage-devel] Re: A menu for the notebook

Oh, jeez. I didn't realize that there were multi-level dropdowns in your example. Guess I only rolled over the top and thought, yeah, that's cool. But that simply won't do. Thanks to recent irreversible decisions, multi-level dropdowns get people hit in the head, and we don't want that. I

[sage-devel] Re: A menu for the notebook

There could be a presentation mode in addition to the slideshow mode where the menu would appear. Also cookies could be used to stay in presentation mode until the user switches back to default mode. This way the current navigation system would be the default. On 3/15/07, Georg Muntingh [EMAIL

[sage-devel] Re: A menu for the notebook

I like the simplicity of it... I ran something like this by William once before, and he objected citing Tish's dislike of dropdown menus. What do other people think of this? On Fri, 9 Mar 2007, Timothy Clemans wrote: I have created a menu for the notebook that would be helpful. I really