- Pharo-dev - lists.pharo.org

Re: [Pharo-project] a plea for "save and quit"

by StÃ©phane Ducasse

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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2009

Re: [Pharo-project] a plea for "save and quit"

by Michael Roberts

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

June 11, 2009

Re: [Pharo-project] #IdentityIncludes: for FloatArray

by Nicolas Cellier

FloatArray is a raw array of bits interpreted as single precision (32 bits) floats. It does not contain any object pointer, only the content (value). At each access #at: will create a new Float (64 bits). So you have (self at: 1) ~~ (self at: 1). Does that explain? Nicolas 2009/6/11 Cyrille Delaunay <cyrille.delaunay(a)etudiant.univ-lille1.fr>: > > > try to inspect: > (FloatArray new:1)at: 1 put: 2.5 ; yourself > and print: > self identityIncludes: self anyOne > > It returns false. > Is it a 'normal' comportment ? > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2009

[Pharo-project] #IdentityIncludes: for FloatArray

by Cyrille Delaunay

try to inspect: (FloatArray new:1)at: 1 put: 2.5 ; yourself and print: self identityIncludes: self anyOne It returns false. Is it a 'normal' comportment ?

June 11, 2009

[Pharo-project] space analysis

by StÃ©phane Ducasse

> "SpaceTally new printSpaceAnalysis: 1 on: 'space.txt'".

June 11, 2009

Re: [Pharo-project] Fwd: First try of Pharo

by StÃ©phane Ducasse

tx torsten could you come up with a little text that we could put on the pharo-project web site to explain to people how to get the news without been flooded by emails :)? Stef > > > BTW: If you are afraid of the traffic on the mailinglist just > subscribe > but set option to not get emails. Then you can browse the archive > to read but still post questions. See [3] > > > [1] http://pharo-project.org/download > [2] https://gforge.inria.fr/frs/download.php/22410/setup_pharo_0.0.0.3.exe > [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-June/009617.html > -- > GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate und > Telefonanschluss > fÃ¼r nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2009

Re: [Pharo-project] a plea for "save and quit"

by Tudor Girba

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" and not save when I perform experiment changes on objects that I do not want to keep with me (for example when I have some expensive computation and then want to play with some variation at the end). - You would want to use "Save and quit" typically when you work on code and want to keep it The problem is that because they are close, it will be easy to click on the other one by mistake (it happens all the time with long menu and small fonts). So, if you really want to reintroduce "Save and quit" it should at least not be close to "Quit". A minimal defense would be a separator between "Save and quit" and "Quit": "Save" "Save as..." "Save and quit" ----- "Quit" But, here is another idea. In VisualWorks we introduced a small add-on that prompts you to save the image after publishing in the repository, and when closing the image. Like this we instill the good practice of publishing and saving the code so that even if the image crashes, you are in sync with the repository. So, as a result you can always quit without saving. Would it not be better to prompt for saving the image after you save something in a Monticello repository? Cheers, Doru On 11 Jun 2009, at 09:46, Adrian Lienhard wrote: > 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 not needed anymore. > > Adrian > > > On Jun 11, 2009, at 09:25 , StÃ©phane Ducasse wrote: > >> 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' >> -'Save ...' -> 'Save as', 'Save as new version', 'Save and Quit' >> -'Quit' >> >> >> So could you use this pattern to explain what you think/want? >> >> Stef >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

June 11, 2009

Re: [Pharo-project] a plea for "save and quit"

by Adrian Lienhard

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 not needed anymore. Adrian On Jun 11, 2009, at 09:25 , StÃ©phane Ducasse wrote: > 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' > -'Save ...' -> 'Save as', 'Save as new version', 'Save and Quit' > -'Quit' > > > So could you use this pattern to explain what you think/want? > > Stef > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2009

Re: [Pharo-project] a plea for "save and quit"

by StÃ©phane Ducasse

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 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' > -'Save ...' -> 'Save as', 'Save as new version', 'Save and Quit' > -'Quit' > > > So could you use this pattern to explain what you think/want? > > Stef > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2009

Re: [Pharo-project] a plea for "save and quit"

by StÃ©phane Ducasse

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' -'Save ...' -> 'Save as', 'Save as new version', 'Save and Quit' -'Quit' So could you use this pattern to explain what you think/want? Stef

June 11, 2009