Why not Lukas' proposal?
Other mails argued that we should not add save and quit because it
increases the menu size. But with Lukas' suggestion the number of
menu items stay the same, hence this argument does not hold.
Mike argued he needs save as new version at least once a day. This
is
No preference. Preferences are for the weak :)
We want to have design decision no absence of decision by preference
plague.
So guys come up with a good solution and we will use it but no
preference.
So I could not understand the proposals except this one:
-'Save'
which could also be from what I understand
-'Save and Quit'
-'Save ...' - 'Save', 'Save as ', 'Save as new version'
-'Quit'
On Jun 11, 2009, at 9:25 AM, Stéphane Ducasse wrote:
No preference. Preferences are for the weak :)
We want to have design decision no absence of
OK, here again the proposal of Lukas that I think is the best so far.
-
Save
Save as...
Save and quit
Quit
-
The behavior of Save as... would be modified to automatically pick
the next version number (but still lets you edit the file name). Like
this, Save as next version is
Hi,
I like very much the idea of Save as to provide the new version name
by default.
But, I have there is a usability problem with Save and quit being
spatially close to Quit. The difference between is quite large, and
you want to use them for very different scenarios:
- I want to use Quit
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
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
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
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
Tudor Girba a écrit :
Save
Save as...
Save and quit
-
Quit
Hi all,
I like this simple proposition.
We still have 'recover lost changes' in the case of unwanted quit
without saving.
alain
___
Pharo-project
Hm.
Isn't it as simple as this?
Author initialsPerSe isEmpty
Or is that too naive? ;-)
- on
On Jun 11, 2009, at 14:12, Michael Roberts wrote:
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
You can remove that from the menu using the os-x mac menu api
that is used to modify the menu at startup time, so at startup time an
additonal
step is needed.
It's left there because some people wanted a way to quit the image
without any squeak image involvement, it could of course be made a
OK, here again the proposal of Lukas that I think is the best so far.
-
Save
Save as...
Save and quit
Quit
-
The behavior of Save as... would be modified to automatically pick
the next version number (but still lets you edit the file name). Like
this, Save as next
I like this one too.I don't like Save .. Save, Save as.. etc, to much
cliks (or moves) just to save
On Thu, Jun 11, 2009 at 9:17 AM, Alain Plantec alain.plan...@free.frwrote:
Tudor Girba a écrit :
Save
Save as...
Save and quit
-
Quit
Hi all,
I like
Oscar Nierstrasz wrote:
Hi Folks,
Is there any reason why save and quit is commented out of the world
menu? It is what I want to do 90% of the time.
Would be nice to have it back by default.
+10
___
Pharo-project mailing list
IIRC, you get the option to save whenever you try to quit.
So save and quit didn't really make sense, as it'd save, then ask you if
you wanted to save again before actually quitting...
Cheers,
Henry
Oscar Nierstrasz skrev:
Hi Folks,
Is there any reason why save and quit is commented out of
this is why it was removed.
in fact there is no quit
On Jun 10, 2009, at 1:46 PM, Henrik Johansen wrote:
IIRC, you get the option to save whenever you try to quit.
So save and quit didn't really make sense, as it'd save, then ask
you if
you wanted to save again before actually quitting...
Nope.
If I uncomment it, it works exactly as I want, which is to save and
quit without any further prompting.
- on
On Jun 10, 2009, at 13:46, Henrik Johansen wrote:
IIRC, you get the option to save whenever you try to quit.
So save and quit didn't really make sense, as it'd save, then ask
Oscar Nierstrasz wrote:
Nope.
If I uncomment it, it works exactly as I want, which is to save and
quit without any further prompting.
+10, I hate that this was removed and always go and put it back in. I
don't want to go through a two step process every time.
--
Ramon Leon
well there is tension between long menus and short menus.
and if we have already three items just to save we will end up been
squeakish.
So except if there is a huge pression or a cool argument we would like
to keep save/quit and not have save/quit/save and quit
Oscar Nierstrasz wrote:
Stéphane Ducasse wrote:
well there is tension between long menus and short menus.
and if we have already three items just to save we will end up been
squeakish.
So except if there is a huge pression or a cool argument we would like
to keep save/quit and not have save/quit/save and quit
So except if there is a huge pression or a cool argument we would like
to keep save/quit and not have save/quit/save and quit
I am also in favor of adding Save and quit.
Get rid of Save as new version instead, I never use this one.
Speaking of it, Save as... could be made a bit smarter and
On Wed, Jun 10, 2009 at 5:13 PM, Lukas Renggli reng...@gmail.com wrote:
So except if there is a huge pression or a cool argument we would like
to keep save/quit and not have save/quit/save and quit
I am also in favor of adding Save and quit.
Get rid of Save as new version instead, I never
Love the minimal menus in Pharo.
Squeakish menus make me squeamish.
Glad to not have Save and Quit
Could lose Save as New Version.
2009/6/10 Nicolas Chillo nchi...@gmail.com:
On Wed, Jun 10, 2009 at 5:13 PM, Lukas Renggli reng...@gmail.com wrote:
So except if there is a huge pression or a
On Jun 10, 2009, at 22:13 , Lukas Renggli wrote:
So except if there is a huge pression or a cool argument we would
like
to keep save/quit and not have save/quit/save and quit
I am also in favor of adding Save and quit.
Get rid of Save as new version instead, I never use this one.
Lukas Renggli wrote:
So except if there is a huge pression or a cool argument we would like
to keep save/quit and not have save/quit/save and quit
I am also in favor of adding Save and quit.
Get rid of Save as new version instead, I never use this one.
I use it at least once a day. You
What about auto-adaptative menus learning your habits.
X most used items on top.
Y often used items following.
Every other less used items in submenus.
Of course, a logical order could be preserved among the Y often used items.
That's already the spirit of Pharo world menu, except this is a bit
On Jun 10, 2009, at 2:56 PM, Michael Rueger wrote:
Nicolas Cellier wrote:
What about auto-adaptative menus learning your habits.
X most used items on top.
Y often used items following.
Every other less used items in submenus.
you mean the most horrible idea MS ever had, changing menus?
what about having a preference to enable/disable save and quite from menu?
On Wed, Jun 10, 2009 at 6:30 PM, Brian Brown br...@ablelinktech.com wrote:
On Jun 10, 2009, at 2:56 PM, Michael Rueger wrote:
Nicolas Cellier wrote:
What about auto-adaptative menus learning your habits.
X most
How to customize the menus?
Customization == Preference, OK these are synonyms.
Among the propositions so far:
1) override a method
2) some specific hard-wired Preferences
3) automatic
some drawbacks:
1) require maintenance at each update
2) why a Preference for an item and not another ?
3)
30 matches
Mail list logo
