- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Save and quit menu

by Mathieu Suen

Yeap! that is why I found the quit button useless. Either you want to save and quit or save do not quit(menu: file -> quite do not save). On Oct 4, 2008, at 1:42 AM, Antony Blakey wrote: > > On 03/10/2008, at 11:58 PM, David Mitchell wrote: > >> If you quit without Saving, a dialog appears. > > Which is fine unless moving the mouse or triggering the quit causes > a change in the image, in which case you cannot quit without being > presented with a dialog, even though you haven't 'changed' anything. > > Antony Blakey > ------------- > CTO, Linkuistics Pty Ltd > Ph: 0438 840 787 > > Some defeats are instalments to victory. > -- Jacob Riis > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Mth ___________________________________________________________________________ Yahoo! Mail rï¿½invente le mail ! Dï¿½couvrez le nouveau Yahoo! Mail et son interface rï¿½volutionnaire. http://fr.mail.yahoo.com

Oct. 4, 2008

Re: [Pharo-project] [update] 10086

by Michael Roberts

I've update to 10086, but when I was going to publish some new changes I have noticed differences between my image and the repository. e.g BalloonMorph, MenuMorph, StandardScriptingSystem, SystemProgressBarMorph all have their classVariables reversed. This expected? thanks, Mike On Sat, Oct 4, 2008 at 9:00 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Neatttttttttt! > > As soon as I have finish with my floor (somebody asked me what it was: > removing the wood layer, hooving the dust, putting wollrock, painting with > xylophene, reputting the wood) > I will really extract etoy :) > then gary fixes and check keith kernel extensions > > Stef > > On Oct 3, 2008, at 10:19 PM, Marcus Denker wrote: > >> Issue 214: [enh] executeMethod via primitives >> - moves the *executeMethod: method to protoObject >> - uncomments the commented primitive for faster execution >> Issue 211: undeclared fix for 10084 >> - fixes one remaining reference to CurrentProjectRefactoring >> Issue 210: [ENH] CompiledMethod explorer >> Issue 206: [ENH] simplify unreferencedInstanceVariables, >> allUnreferencedInstanceVariables >> - add test for and simplify Behavor>>#whichSelectorsAccess: >> - simplify Behavior>>#unreferencedInstanceVariables >> - simplify and remove #isDoIt check from >> Behavior>>#allUnreferencedInstanceVariables >> Issue 196: remove #hash from Association >> Issue 212: random cleans >> - KillNewWorld: remove class NewWorldWindow >> - InspectorTileRemove: remove the menus from inspector for tiles >> - delPlayerSurrogate.1: remove class PlayerSurrogate >> - CleanExplanation: remove more code related to the "explain" >> functionality >> - UnsentMessages: remove some unsent messages >> >> Postscript: >> >> Vocabulary allStandardVocabularies removeKey: #unknown. >> PartsBin allInstances do: [:pb| pb submorphs do: [:sm| (sm target >> name=#AnObsoleteGeeMailMorph) ifTrue: [ pb removeMorph: sm ]]]. >> Preferences removePreference: #thoroughSenders. >> Preferences removePreference: #dragNDropWithAnimation. >> Set rehashAllSets. >> >> -- >> Marcus Denker -- denker(a)iam.unibe.ch >> http://www.iam.unibe.ch/~denker >> >> >> _______________________________________________ >> 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 >

Oct. 4, 2008

[Pharo-project] More full screen refactoring

by Michael Roberts

Hi Marcus, issue: 186, I'm not sure why fullScreen.2.cs did not work? Can you check SLICE-fullScreenRefactoring-mike.roberts.1 in the inbox. thanks, Mike

Oct. 4, 2008

Re: [Pharo-project] does anybody got the changes to the old browser to add traits?

by Adrian Lienhard

At some point in the past, methods from traits were also shown in italic. I added this to the old browser because it is the most fundamental info (else you always override methods from traits when changing a method in a class). I think we should add this back too. Adrian On Oct 4, 2008, at 12:02 , StÃ©phane Ducasse wrote: > Then I would like to know where are the addtrait menuitem that were > once > in the old browser? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 4, 2008

[Pharo-project] does anybody got the changes to the old browser to add traits?

by StÃ©phane Ducasse

Then I would like to know where are the addtrait menuitem that were once in the old browser? Stef

Oct. 4, 2008

[Pharo-project] How to define a trait with packagebrowser?

by StÃ©phane Ducasse

Hi in pharo10086 + ScriptLoader loadTools I would like to know how to define a trait. I thought that traits integration was in. Stef

Oct. 4, 2008

Re: [Pharo-project] History and SUnit

by StÃ©phane Ducasse

Keith you should have a look at Assess or Assessment (I do not remember) a complete rewrite of Sunit by andres valloud. He presented it at esug and the point is really to be able to extend: broken, benchmarks... This is on my long todo. But it makes a lot of sense. Stef On Oct 3, 2008, at 11:04 PM, Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> Thanks keith >> After I really wonder if we need all that. >> I would be really interested in understanding what are the 20% nost >> useful features >> and focus on them. >> >> Stef > 1. The old suite building code was a mess and had lots of duplication > for very little functionality. Here we get much more for less code. > > For the rest, I suggest looking at the feature set backwards, start > with > the basic uber-use case* and see what features are needed to support > it. > > * I implemented much of this for my own project in st/x 10 years ago, > and have missed it ever since. > > 2. Use Case: Be able to run... > > "All tests or specifications for my project which are expected to > run on > this platform, this image version, and this vm... with the ability to > mark tests as 'expected failures', 'to do' , 'slow', 'long', 'uses > network' etc, and then be able to run a suite with or without the > marked > tests. > > btw: The next refactoring is to remove the whole notion of > expectedFailures from TestResult and further simplify things. I > asked on > squeak-dev over a year ago to ascertain whether there are any users of > this confusing feature, and I don't think there are any. > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 4, 2008

Re: [Pharo-project] [update] 10086

by StÃ©phane Ducasse

Neatttttttttt! As soon as I have finish with my floor (somebody asked me what it was: removing the wood layer, hooving the dust, putting wollrock, painting with xylophene, reputting the wood) I will really extract etoy :) then gary fixes and check keith kernel extensions Stef On Oct 3, 2008, at 10:19 PM, Marcus Denker wrote: > Issue 214: [enh] executeMethod via primitives > - moves the *executeMethod: method to protoObject > - uncomments the commented primitive for faster execution > Issue 211: undeclared fix for 10084 > - fixes one remaining reference to CurrentProjectRefactoring > Issue 210: [ENH] CompiledMethod explorer > Issue 206: [ENH] simplify unreferencedInstanceVariables, > allUnreferencedInstanceVariables > - add test for and simplify Behavor>>#whichSelectorsAccess: > - simplify Behavior>>#unreferencedInstanceVariables > - simplify and remove #isDoIt check from > Behavior>>#allUnreferencedInstanceVariables > Issue 196: remove #hash from Association > Issue 212: random cleans > - KillNewWorld: remove class NewWorldWindow > - InspectorTileRemove: remove the menus from inspector for tiles > - delPlayerSurrogate.1: remove class PlayerSurrogate > - CleanExplanation: remove more code related to the "explain" > functionality > - UnsentMessages: remove some unsent messages > > Postscript: > > Vocabulary allStandardVocabularies removeKey: #unknown. > PartsBin allInstances do: [:pb| pb submorphs do: [:sm| (sm target > name=#AnObsoleteGeeMailMorph) ifTrue: [ pb removeMorph: sm ]]]. > Preferences removePreference: #thoroughSenders. > Preferences removePreference: #dragNDropWithAnimation. > Set rehashAllSets. > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 4, 2008

Re: [Pharo-project] Linux VM with FreeType and closure bytecodes

by Igor Stasenko

2008/10/3 <bryce(a)kampjes.demon.co.uk>: > Igor Stasenko writes: > > Bryce, are you plan to build a windoze VM as well? > > Eventually, or ask for one to be built, and I'll need a Mac VM as > well. But I've neither a Windows or Mac build environment here, and it > could be a while before I set them up. > > If you've got the build environment you used for the FreeType VM then > just load the latest VMMaker package from the Exupery project on > SqueakSource and rebuild. If you build it, then we'll have it now. > > Oh, and how hard was it getting the FreeType libraries installed on > Windows? > piece of cake. You can look at README file in win32/plugins/FT2Plugin dir for instructions. You find it in FT2Plugin win32 sources zip file. > Bryce > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Oct. 4, 2008

Re: [Pharo-project] Save and quit menu

by Antony Blakey

On 03/10/2008, at 11:58 PM, David Mitchell wrote: > If you quit without Saving, a dialog appears. Which is fine unless moving the mouse or triggering the quit causes a change in the image, in which case you cannot quit without being presented with a dialog, even though you haven't 'changed' anything. Antony Blakey ------------- CTO, Linkuistics Pty Ltd Ph: 0438 840 787 Some defeats are instalments to victory. -- Jacob Riis

Oct. 3, 2008