[Idle-dev] [ idlefork-Feature Requests-661318 ] Configure autosave

[SourceForge.net]

Feature Requests item #661318, was opened at 2003-01-02 16:46
Message generated for change (Comment added) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=359579&aid=661318&group_id=9579

Category: None
Group: None
Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: Bruce Sherwood (bsherwood)
Assigned to: Kurt B. Kaiser (kbk)
Summary: Configure autosave

Initial Comment:
It is important to me and my students to be able to 
specify as a configuration option that autosave be in 
effect. That is, when I press F5 and I have made 
changes to the file, the file is overwritten with the current 
version, with no dialog box intruding. The value of 
autosave is that it reduces the likelihood of losing work 
in case of an interruption, and the value of eliminating 
the dialog box is that it increases interactivity and avoids 
a loss of focus due to the intrusion. The goal is to make 
full-program edit/run cycles as highly interactive as the 
interactive shell. The practically infinite un-do capability 
of IDLE makes autosave acceptable. And the 
knowledgeable can always if desired save a copy at a 
particular stage in the development process.

----------------------------------------------------------------------

>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-05-26 10:54

Message:
Logged In: YES 
user_id=149084

(I reconfigured the SF site to send RFE to the 
Idle-dev list.)

----------------------------------------------------------------------

Comment By: Kurt B. Kaiser (kbk)
Date: 2003-05-26 01:29

Message:
Logged In: YES 
user_id=149084

Completed and applied.  Thanks for the patch!!
configDialog 1.53  
ScriptBinding 1.22
config-main.def 1.16


----------------------------------------------------------------------

Comment By: Kurt B. Kaiser (kbk)
Date: 2003-05-17 21:45

Message:
Logged In: YES 
user_id=149084

Here's the equivalent in a context diff.

Also there was a spurious tab at lin 411 
frameEncoding.pack

which I included in the diff....

----------------------------------------------------------------------

Comment By: Bruce Sherwood (bsherwood)
Date: 2003-05-17 13:53

Message:
Logged In: YES 
user_id=34881

I've attached a version of configDialog.py containing controls 
for specifying whether to prompt for saving the file at the start 
of a run or just save the file without prompting (assuming the 
file has been saved to disk sometime in the past -- that is, 
the first run of an unsaved file should prompt to save to disk). 
Sorry, I don't know how to produce a diff package, but I did 
put "#bas" comments in front of each of my minor changes.

I wasn't sure how to properly initialize the new variable 
self.askSave, nor did I wander through the rest of idlefork to 
see where to use this variable when starting a run, on the 
assumption that you would be able to do this easily and 
quickly. I just wanted to spare you the annoyance of setting 
up the GUI aspects. Hope this helps.

----------------------------------------------------------------------

Comment By: Bruce Sherwood (bsherwood)
Date: 2003-01-30 12:13

Message:
Logged In: YES 
user_id=34881

I may not be remembering this correctly, but I thought there 
had been statements to the effect that although 0.9a2 would 
make the save dialog box the default, there would be a 
configuration mechanism to disable it. That's why I reported 
the new situation as a bug. I do agree that being able to kill 
subprocesses is vastly more important than this detail! 
However, for the (slightly?) longer run, this feature is very 
important to me, for the reasons I gave in my original request. 
It shouldn't matter whether one agrees or disagrees with my 
view of this. The point of configurability is to make it possible 
for people with different views to use the same tool. As you 
say, I do agree with the initial save dialog (before there is any 
file on the hard drive), and I much appreciate the 
improvements to the initial save dialog. I'm only objecting to 
the save dialog that intrudes on further saves after the initial 
one.

----------------------------------------------------------------------

Comment By: Kurt B. Kaiser (kbk)
Date: 2003-01-30 11:08

Message:
Logged In: YES 
user_id=149084

On Idle-dev you've agreed that the initial Save dialog is
acceptable as it teaches good habits:

http://mail.python.org/pipermail/idle-dev/2003-January/001475.html

The dialog which previously complained about an unsaved
program and aborted the Run has been enhanced so that it 
offers to save the file.  In addition, its OK is bound to "enter", 
so one keystroke will save the file and proceed with the Run.

If you don't want to see the dialog, just remember to hit the save
keybinding before F5.  This is not a big deal, and teaches good
habits.

Adding the option to automatically re-save the program to
the config GUI will take a bit of work (because it means fully
comprehending ConfigDialog.py) and I don't have as high
a priority on this as some of the other issues like killing the
subprocess correctly.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=359579&aid=661318&group_id=9579