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
Quit worksheet behaviour #1230
Comments
Attachment: sage-1230.patch.gz |
comment:1
The attached patch fixes all the above issues: class SendWorksheetToFolder(resource.PostableResource):
WARNING: This might depend on the patch at #2636 and its dependency (#336). |
comment:3
On sage-devel, William already pointed out that the second change in the patch dated 05/10/2008 02:04:01 PM. includes an erroneous deletion of an else clause. The patch "works for me" and the changes are very small. I am not familiar with the code, but just doing "pattern matching" on the code around it, gives confidence that it is coded consistent with what was already there. COMMENT: The worksheet "list" page now also has a big fat "Quit" button, next to "Archive" and "Delete". The fact that "Quit" on a worksheet itself indeed means "close this page" might confuse users into thinking that the button logs them out or something. Ticket #3147 should probably be closed if this gets accepted, since it solves the problem there as well (it's not really a duplicate of this ticket, though) -- never mind, it's been closed already. |
Attachment: sage-1230-part2.patch.gz Attachment: sage-1230-part3.patch.gz Quit --> Stop as recommended by referee |
comment:4
No issues with the code for me anymore. Note that within the worksheet there is "Save and Quit", whereas on a worksheet list, there is "Stop" for the same function. I am in favour of this difference in naming, because it matches the difference in perspective (in one case you're standing in the worksheet and hence you "quit" (exit) it. In the other case, you're viewing the worksheet from outside and you "stop" it. Someone more knowledgeable about the sage development model should decide if further refereeing is necessary. (It would probably be good if Tom Boothby could look at it) |
comment:5
Merged all three patches in Sage 3.0.2.alpha0 |
Three points:
Currently, the notebook has a "quit worksheet" function that kills the background sage engine. Currently, this leaves the browser on the worksheet in question. I find that confusing: If I "quit" a worksheet, I expect that I leave the worksheet. Therefore, I think that the appropriate behaviour is that "quitting" a worksheet brings you to your index page (where it will not have the "active" attribute)
The fact that "active" worksheets are "not archived" worksheets is clashing terminology with a worksheet being "active" (there is a sage process associated to it) versus a worksheet being "not active".
The second use could be called "running" versus "not running" instead.
Component: notebook
Issue created by migration from https://trac.sagemath.org/ticket/1230
The text was updated successfully, but these errors were encountered: