- Pharo-dev - lists.pharo.org

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

by StÃ©phane Ducasse

Apparently I do not have it. can you check the universe? On Oct 4, 2008, at 4:49 PM, David RÃ¶thlisberger wrote: > >> I would like to know how to define a trait. I thought that traits >> integration was in. > > In the context-menu of a class don't you get the button 'new trait > template'? Then you can define the trait as you define a class. > > TraitsIntegration is integrated, I took the code of Juraj and put it > into OB-Enhancements, so that we only have to load one package now > to get it. Same is true for SUnitIntegration btw. > > David > > _______________________________________________ > 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] [update] 10087

by Marcus Denker

Issue 80: 7130 PluggableListMorphFix Issue 41: 7091 PluggableListMorphfix (M4719) Issue 98: 7152 Form-isAllWhiteandFormTest-ar Issue 57: 7107 IntervalReverseDoFix (M6438) -> used Nicolas fix from http://bugs.squeak.org/view.php?id=6456 Issue 202: Pier-Model can not be loaded into Pharo (please no question about "we need a prebuilt image, we need a TT/ Plymorph image. If you want to ask that question, just pretent that I did not do this update...) -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 4, 2008

Re: [Pharo-project] Save and quit menu

by Simon Kirk

Quit and ask to save if things are changed is by far the most logical and simple combination. On the other hand, as Antony pointed out, the image seems to think there's been a change for almost any action, so even if you've just pressed save, if you then quit you get asked to save again! S On 4 Oct 2008, at 17:47, Gary Chambers wrote: > I liked save and quit, not had a problem with Squeak not actually > saving... > Still fewer menu options is good. Not seen many other applications > with a save+quit... perhaps if the "X" (aka close on host window) > fed back to the dialog, all would be good. > > 2c (or 10p in rip-off-Britain) :-) > > Gary. > > ----- Original Message ----- From: "Mathieu Suen" <mathieusuen(a)yahoo.fr > > > To: "An open mailing list to discuss any topics related to an open- > sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> > Sent: Saturday, October 04, 2008 1:00 PM > Subject: Re: [Pharo-project] Save and quit menu > > >> 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 >> >> >> _______________________________________________ >> 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 ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

Oct. 4, 2008

Re: [Pharo-project] Save and quit menu

by Gary Chambers

I liked save and quit, not had a problem with Squeak not actually saving... Still fewer menu options is good. Not seen many other applications with a save+quit... perhaps if the "X" (aka close on host window) fed back to the dialog, all would be good. 2c (or 10p in rip-off-Britain) :-) Gary. ----- Original Message ----- From: "Mathieu Suen" <mathieusuen(a)yahoo.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Saturday, October 04, 2008 1:00 PM Subject: Re: [Pharo-project] Save and quit menu > 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 > > > _______________________________________________ > 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] More full screen refactoring

by Michael Roberts

ok, issue: 216. thanks, Mike

Oct. 4, 2008

Re: [Pharo-project] More full screen refactoring

by Marcus Denker

On 04.10.2008, at 13:37, Michael Roberts wrote: > Hi Marcus, > > issue: 186, I'm not sure why fullScreen.2.cs did not work? When I file it in and select "Fullscreen on", I got a DNU. This might have been caused by either the bytecode bug or that I just filed on the .2, not .1 before. No idea. The simplest thing is in a case like this: Add a new entry in the bugtracker with a new changeset that works (or a pointer to a slice in the inbox). Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 4, 2008

Re: [Pharo-project] [update] 10086

by Marcus Denker

On 04.10.2008, at 13:53, Michael Roberts wrote: > 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? > No. I don't know the cause for this.... this already happended when doun 3.9 with Monticello. Annoying. Marcus > 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 4, 2008

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

by David RÃ¶thlisberger

> I would like to know how to define a trait. I thought that traits > integration was in. In the context-menu of a class don't you get the button 'new trait template'? Then you can define the trait as you define a class. TraitsIntegration is integrated, I took the code of Juraj and put it into OB-Enhancements, so that we only have to load one package now to get it. Same is true for SUnitIntegration btw. David

Oct. 4, 2008

[Pharo-project] Performance observation

by Bill Schwab

Hello all, As part of some catch-up work from a couple of weeks ago, I'm using my 1.8 GHz/500MB Ubuntu box and a remote desktop client to do some configuration on a win2k3 VM running on a blade server on campus. By many standards, I am using a pig-slow machine jumping through lots of hoops to reach a machine that has only part of a CPU at the other end. One striking thing is that the remote desktop client on Ubuntu is putting its Windows XP counter part to shame for speed for most things; the XP client drags on everything; this is generally (almost) snappy, and much nicer to use as result. The XP box in my office, IIRC, is a 3.x GHz machine (faster than what I am using now to be sure); it too might have "only" 500MB of RAM - I can check that later if it matters. The client is clearly optimizing window moves and at least some scrolling operations, uncoverings, etc. Pharo running over there looks comparatively slow, no doubt because ever windowing operation is seen as a change to the on main window. I do not know what to make of it, other than it might be a argument in favor of one native window per system window. Just thought I'd mention it. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

Oct. 4, 2008

Re: [Pharo-project] [update] 10086

by Bill Schwab

Hello all, I have no idea on the answer to Mike's question, but this reminds me of an RB problem that arose in Dolphin. I do not recall the circumstances, but the _instance_ variables were being sorted (alphabetical order IIRC), which is really bad given the way Dolphin's STB (serialization) relies on iv order. OA fixed it long ago. Bottom line: the order of instance variables might be important, and IMHO should not be changed unless the programmer does or requests it. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> mike(a)mjr104.co.uk 10/04/08 7:53 AM >>> 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 > _______________________________________________ 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