[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-09-21 Thread William Stein
On 9/21/07, Hamptonio <[EMAIL PROTECTED]> wrote: > Were any of these ideas ever implemented? I am occaisonally messed up > by the worksheet quietly restarting without my realizing it. (In that No work has been done on this. I've made this http://trac.sagemath.org/sage_trac/ticket/735 so it do

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-09-21 Thread Hamptonio
Were any of these ideas ever implemented? I am occaisonally messed up by the worksheet quietly restarting without my realizing it. (In that regard I believe there is a minor bug: when the notebook restarts, it does not add the red bars on the left to indicate an un-executed cell.) I used to use t

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-22 Thread William Stein
On 8/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> (By the way, I think it's a known bug that if I hit the save button, > >> then things I've entered into a cell don't get saved if I didn't hit > >> shift-enter.) > >> > > > > That is not a bug - it is by design. We may consider changin

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-22 Thread boothby
>> (By the way, I think it's a known bug that if I hit the save button, >> then things I've entered into a cell don't get saved if I didn't hit >> shift-enter.) >> > > That is not a bug - it is by design. We may consider changing this > behavior though. I think this is a poor idea, interface-wi

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-21 Thread William Stein
On Aug 21, 2007, at 9:00 PM, Dan Christensen <[EMAIL PROTECTED]> wrote: > > "William Stein" <[EMAIL PROTECTED]> writes: > >> On 8/21/07, Dan Christensen <[EMAIL PROTECTED]> wrote: >> >>> Hmm, a quick test using two tabs in one browser shows that even if >>> I save changes in one tab, if I reloa

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-21 Thread Dan Christensen
"William Stein" <[EMAIL PROTECTED]> writes: > On 8/21/07, Dan Christensen <[EMAIL PROTECTED]> wrote: > >> Hmm, a quick test using two tabs in one browser shows that even if >> I save changes in one tab, if I reload the page in the other tab >> the changes don't always appear. But if I close the

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-21 Thread William Stein
On 8/21/07, Dan Christensen <[EMAIL PROTECTED]> wrote: > > I wish. That would be nice. Instead, you'll eventually get a warning in red > > that another browser is viewing the same page. Otherwise things are exactly > > the same. > > Just to be clear, can I at least "take over" the worksheet from

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-21 Thread Dan Christensen
"William Stein" <[EMAIL PROTECTED]> writes: > On 8/20/07, Dan Christensen <[EMAIL PROTECTED]> wrote: > >> I'm also curious what happens if I leave a browser open to a worksheet >> in my office, and then open the worksheet again from home. Do they >> somehow synchronize? > > I wish. That would be

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-20 Thread William Stein
On 8/20/07, Dan Christensen <[EMAIL PROTECTED]> wrote: > Nils Bruin <[EMAIL PROTECTED]> writes: > > > This makes me think that a checkbox "this worksheet is persistent" > > might be better. > > This sounds good to me. > > I'm also curious what happens if I leave a browser open to a worksheet > in

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-20 Thread Dan Christensen
Nils Bruin <[EMAIL PROTECTED]> writes: > This makes me think that a checkbox "this worksheet is persistent" > might be better. This sounds good to me. I'm also curious what happens if I leave a browser open to a worksheet in my office, and then open the worksheet again from home. Do they someh

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-13 Thread Hamptonio
I agree. I think a big selling point for sage is using the notebook for teaching. A related thing I would love to have someday is the ability to control which users can see which worksheets, in a fine- grained sense. E.g., I would like to be able to assign students to small groups, and have eac

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-10 Thread Jonathan Bober
> > > Obviously, this option should not exist on servers that serve a wide > > range of users. > > It's really for people doing big computations on their own set of > > computers. > > OK. Just a thought - it might be even better to have this option available or not on a per-user basis. In fact

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-10 Thread William Stein
On 8/10/07, Nils Bruin <[EMAIL PROTECTED]> wrote: > > [...] Would the following work for you? [...] > >[Save] [Save & Close] [ Close & Leave Running ] [Discard Changes] > > Since you ask explicitly, yes that would work. The magical behaviour > before > was really surprisingly friendly, but ra

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-10 Thread Nils Bruin
> [...] Would the following work for you? [...] >[Save] [Save & Close] [ Close & Leave Running ] [Discard Changes] Since you ask explicitly, yes that would work. The magical behaviour before was really surprisingly friendly, but rather unpredictable in resource usage. Keep in mind that it i

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-10 Thread Justin C. Walker
On Aug 10, 2007, at 4:47 AM, William Stein wrote: > On 8/9/07, Nils Bruin <[EMAIL PROTECTED]> wrote: [snip] > One question is whether this button should appear for the public > server or not. And, if it does, if it should still have some > timeout, e.g., some number of hours. I like the solutio

[sage-devel] Re: Quitting ignored worksheet vs. long computations

2007-08-10 Thread William Stein
On 8/9/07, Nils Bruin <[EMAIL PROTECTED]> wrote: > I understand the necessity to quit ignored worksheets in many cases, > to save resources. However, it does kill a highly desirable behaviour > that existed before: > 1) start very long computation at work > 2) kill browser, log out (process stil