I agree with Oscar. one of the challenges is how does the image know it has any active changes? it's not as easy as editing a document say. This could be an interesting technical challenge. Ideally you would ask for 'quit' and if there are no changes, it would not save. if there were it would prompt you to save them. However, in absence of such sophistication in our object world I would at least lay the menu out a little more safely. thanks Mike On Thu, Jun 11, 2009 at 12:22 PM, Oscar Nierstrasz<oscar@iam.unibe.ch> wrote:
No.
Sometimes we want: - Save and Quit and sometimes we want - Quit without saving
but they should not be located where we can too easily click the wrong thing.
They should not be next to each other, and they should not be in the default location of a File Menu.
I know, I have done this too, more than once.
- on
On Jun 11, 2009, at 13:11, Stéphane Ducasse wrote:
you mean
quit    should be always    asking to save?
On Jun 11, 2009, at 12:21 PM, Michael Roberts wrote:
whilst we are debating 'quit' can we move 'Quit do not save' so it is not the first item in the native OS X File menu. Â I have accidentally clicked it a few times and it is a disaster. Â It is also quite different from platform semantics where are you would normally be prompted if a quit would discard changes. Â It should be at the bottom of the menu at the very least. Â Dare I ask if we need it at all...
thanks Mike
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project