January 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] 10208

by Alexandre Bergel

It updates perfectly. Alexandre On 19 Jan 2009, at 21:44, StÃ©phane Ducasse wrote: > - Enh Tool diff. > - Issue 444: Simple Morphic cleanup: Clean up Morph Remove > ownerThatIsA:orA: from Morph. > - more collection tests. > - Issue 445: AligmentMorphBob1 should be merged into AligmentMorph > - Minor cleaning of Bergel on StringHolder > > > More to come soon. > watch it > network > traits adrian fixes > smalldictionary fixes > > - I will try :) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

Re: [Pharo-project] {Spam?} Names for the pharo scripting syntax

by Alexandre Bergel

>> I would pick something that meant free (liberated) or light >> weight. I >> can't think of many at the moment but how about wisp or crest (of a >> wave) > > > crest is nice :) > Central Resistant Emancipating Smalltalk > > French: > Ã©cume I like crest and Ã©cume Alexandre > > >> >> >> Mike >> >> On Tue, Jan 20, 2009 at 7:48 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> We want a real scripting syntax not with !! >>> I will not reopen the story: wait and see. >>> This is since two years that we have that nearly ready but never >>> suceeded to release it. >>> >>> >>> On Jan 19, 2009, at 11:23 PM, Bill Schwab wrote: >>> >>>> Stef, >>>> >>>> My first reaction is "why is it not Smalltalk?" Not the name, but >>>> the language itself. Is there something I missed/should read to >>>> understand 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 >>>> >>>>>>> stephane.ducasse(a)inria.fr 01/19/09 4:16 PM >>> >>>> hi guys >>>> >>>> gwenael is polishing the scripting syntax of pharo (was called in >>>> another world sapphir). >>>> Now we are looking for a new for such a syntax. If you have ideas >>>> please let us know. >>>> Ideally we would like to have a connection with the sea/nature >>>> (peace >>>> and love sarcasm). >>>> >>>> I was thinking about >>>> zephir, >>>> thunder, >>>> storm, >>>> wave, >>>> wale, >>>> orcal, >>>> Maikai >>>> to be well, fine, in a state of goodness in hawaian >>>> MAILA : mÄ*ila (stative) to be clear, as of the sea >>>> atoll, >>>> maibai >>>> >>>>>> - Similar words used to describe coastlines are nice as well: >>>>>> "Tombolo" (my favorite and not a common word), "Lagoon", "Cover", >>>>>> "Cliff" and "Bay". >>>> >>>> from lukas >>>> >>>> I like atoll :) since faro is an atoll >>>> But I like Tombolo too. >>>> >>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

Re: [Pharo-project] Big problem with the implementation of traits

by StÃ©phane Ducasse

hi adrian I'm reading your fixes and I have one question in the following class: oldClass instanceVariableNames: instVarString unsafe: unsafe "This is the basic initialization message to change the definition of an existing Metaclass" | instVars newClass needNew copyOfOldClass copyOfOldTraitComposition copyOfOldClassTraitComposition | environ := oldClass environment. instVars := Scanner new scanFieldNames: instVarString. unsafe ifFalse:[ "Run validation checks so we know that we have a good chance for recompilation" (self validateInstvars: instVars from: oldClass forSuper: oldClass superclass) ifFalse:[^nil]. (self validateSubclassFormat: oldClass typeOfClass from: oldClass forSuper: oldClass superclass extra: instVars size) ifFalse:[^nil]]. "See if we need a new subclass or not" needNew := self needsSubclassOf: oldClass superclass type: oldClass typeOfClass instanceVariables: instVars from: oldClass. needNew ifNil:[^nil]. "some error" needNew ifFalse:[^oldClass]. "no new class needed" "Create the new class" copyOfOldClass := oldClass copy. oldClass hasTraitComposition ifTrue: [ copyOfOldTraitComposition := oldClass traitComposition copyTraitExpression ]. oldClass class hasTraitComposition ifTrue: [ copyOfOldClassTraitComposition := oldClass class traitComposition copyTraitExpression ]. newClass := self newSubclassOf: oldClass superclass type: oldClass typeOfClass instanceVariables: instVars from: oldClass. newClass := self recompile: false from: oldClass to: newClass mutate: false. "... set trait composition..." copyOfOldTraitComposition ifNotNil: [ newClass setTraitComposition: copyOfOldTraitComposition ]. copyOfOldClassTraitComposition ifNotNil: [ newClass class setTraitComposition: copyOfOldClassTraitComposition ]. self doneCompiling: newClass. SystemChangeNotifier uniqueInstance classDefinitionChangedFrom: copyOfOldClass to: newClass. ^newClass to get class: oldClass instanceVariableNames: instVarString unsafe: unsafe "This is the basic initialization message to change the definition of an existing Metaclass" | instVars newClass needNew copyOfOldClass | environ := oldClass environment. instVars := Scanner new scanFieldNames: instVarString. unsafe ifFalse:[ "Run validation checks so we know that we have a good chance for recompilation" (self validateInstvars: instVars from: oldClass forSuper: oldClass superclass) ifFalse:[^nil]. (self validateSubclassFormat: oldClass typeOfClass from: oldClass forSuper: oldClass superclass extra: instVars size) ifFalse:[^nil]]. "See if we need a new subclass or not" needNew := self needsSubclassOf: oldClass superclass type: oldClass typeOfClass instanceVariables: instVars from: oldClass. needNew ifNil:[^nil]. "some error" needNew ifFalse:[^oldClass]. "no new class needed" "Create the new class" copyOfOldClass := oldClass copy. newClass := self newSubclassOf: oldClass superclass type: oldClass typeOfClass instanceVariables: instVars from: oldClass. newClass := self recompile: false from: oldClass to: newClass mutate: false. self doneCompiling: newClass. SystemChangeNotifier uniqueInstance classDefinitionChangedFrom: copyOfOldClass to: newClass. ^newClass and change newclass newSubclassOf: newSuper type: type instanceVariables: instVars from: oldClass "Create a new subclass of the given superclass with the given specification." | newFormat newClass | "Compute the format of the new class" newFormat := self computeFormat: type instSize: instVars size forSuper: newSuper ccIndex: (oldClass ifNil:[0] ifNotNil:[oldClass indexIfCompact]). newFormat == nil ifTrue:[^nil]. (oldClass == nil or:[oldClass isMeta not]) ifTrue:[newClass := self privateNewSubclassOf: newSuper from: oldClass] ifFalse:[newClass := oldClass clone]. newClass superclass: newSuper methodDictionary: MethodDictionary new format: newFormat; setInstVarNames: instVars. oldClass ifNotNil:[ newClass organization: oldClass organization. "Recompile the new class" oldClass hasMethods ifTrue:[newClass compileAllFrom: oldClass]. oldClass hasTraitComposition ifTrue: [ newClass setTraitComposition: oldClass traitComposition copyTraitExpression ]. oldClass class hasTraitComposition ifTrue: [ newClass class setTraitComposition: oldClass class traitComposition copyTraitExpression ]. self recordClass: oldClass replacedBy: newClass. ]. (oldClass == nil or:[oldClass isObsolete not]) ifTrue:[newSuper addSubclass: newClass] ifFalse:[newSuper addObsoleteSubclass: newClass]. ^newClass Now I was wondering why you did not change newClass := self recompile: false from: oldClass to: newClass mutate: false. too Stef

Jan. 20, 2009

Re: [Pharo-project] Workspace Enhancement

by Alexandre Bergel

>>> Neat behaviour - I'll have to try it out (like, what happens when >>> you have 5 open workspaces - do they all have access to the same >>> list of history? Just something to try). >>> >>> What about contents of workspace variables? Are those stored in the >>> history as well? >> >> Actually, I seldom reuse variables across workspaces and have no more >> than 2 or 3 workspace at the same time. >> What would be the ideal scenario for variables? >> >> Thanks for your words, >> Alexandre The history for workspace contents has 5 slots. Slots are filled upon workspace deletion: when you close a workspace, its content is inserted in the history. Only the last 5 contents are remembered. Other are forgotten. It is easy to increase this limit although. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

Re: [Pharo-project] [MC] [ANN] Sourcetalk

by Alexandre Bergel

I guess that Stef emphasized the importance to not rely on previous versions. Alexandre On 20 Jan 2009, at 01:14, Damien Pollet wrote: > On Tue, Jan 13, 2009 at 09:54, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> but why saving the complete package is a problem. >> I hate to have a piece of code and not be able to use because another >> part is on nother server and down or gone. > > He meant, when you work on one package, how to commit only part of the > changes in the image, and keep the rest of the changes for a later > commit. > >> >> Stef >> >> On Jan 13, 2009, at 12:22 AM, Mariano Martinez Peck wrote: >> >>> >>> >>> On Mon, Jan 12, 2009 at 9:07 PM, Keith Hodges <keith_hodges(a)yahoo.co.uk >>>> wrote: >>> Mariano Martinez Peck wrote: >>>> Excelents both documents. I really like them! >>>> >>>> I am one of the SqueakDBX team and one reason I really hate >>> monticello >>>> is that when every time I want to save (commit) it commits full >>>> package. This is very annoying, >>> So switch it to diff mode. >>> >>> I think there is something I don't know about MC. Suppose I have a >>> whole package. I modified some clases. But I don't want to commit >>> some of those changes. If I see diff mode, I can see the diffs, but, >>> If I commit, I commit all. Not only the changes I want. To do that, >>> I have to override the rest of the changes so that not to commit >>> them. And, If I do this, I loose those changes. So, I have to backup >>> those changes in a file, then commit, and recover the changes again. >>> >>> I mean, I would like something like CVS or SVN where you can commit >>> what you want, no the whole package. >>> >>> I don't know If I could express myself. Sorry for my English. >>> >>> >>> >>> Keith >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2009

[Pharo-project] uiTheme Standard Squeak uses ~96% CPU

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=454&can=1&colspec=ID%20Type… Issue 454: uiTheme Standard Squeak uses ~96% CPU â¹ Prev 454 of 454 1 person starred this issue and may be notified of changes. Back to list Status: New Owner: ---- Add a comment andmake changes below Reported by wsgibson1967, Today (5 hours ago) I know. As much as I really like the Watery 2 uiTheme theme I also really like to use the Standard Squeak theme. I have found on both my Mac and Windows systems that when using the Standard Squeak theme with Pharo (core or dev) that the CPU usage will go very high. If a normal amount of windows are open the CPU usage goes upwards to 96%. I do not get this with the Watery 2 or Soft Squeak themes. In case this is useful, I am using TrueType fonts that are standard to each platform. To reproduce: 1) Change to Standard Squeak theme 2) Open two code browsers and select methods from any class (just opening browsers without drilling down to methods do not produce as much of an effect) 3) Open a Test Runner window 4) Open a Monticello Browser The CPU will increase to roughly 96%. I also would like to mention that you guys have done an INCREDIBLE job with Pharo! I am totally impressed with the amount of work done with Pharo as well as its quality. Thank you for stepping up to the challenge!

Jan. 20, 2009

[Pharo-project] Workspace Enhancement

by Torsten Bergmann

Why bother, a simple Smalltalk at: #MyVar put: anObject will do the job for you if required. Yes, this can lead to a leak if forgotten - but typically you will do this for testing purposes and you should not deploy your development image (use a clean image and a defined build process). SmalltalkMT always provided Workspace variables - but I never used them really. Less is sometimes more... Bye Torsten -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

Jan. 20, 2009

Re: [Pharo-project] [ANN] 10209 Watchit integration

by StÃ©phane Ducasse

I added your code to the bug entry On Jan 20, 2009, at 9:22 AM, Torsten Bergmann wrote: > Hi Stef, > >> Now it is nicely integrated in pharo. > > Not yet - why not open it in a separate window instead of a plain > morph on the desk? > This would be more consistent with inspect it, debug it and explore > it from the same menu. > You can also collapse the watch window and move it easily around... > > see code below. > > Bye > Torsten > > ----------------------------------------------------------------------------------------- > watchIt > > | result | > > self handleEdit: > [result := textMorph editor compileSelectionAsBlock. > ((result isKindOf: FakeClassPool) or: [result == #failedDoit]) > ifTrue: [^self flash]]. > (RectangleMorph new) > layoutPolicy: TableLayout new; > layoutInset: 3; > listDirection: #topToBottom; > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > addMorphBack: (StringMorph contents: textMorph editor selection); > addMorphBack: ((UpdatingStringMorph on: result selector: #value) > stepTime: 500; > maximumWidth: nil; > growable: true); > color: Color white; > borderColor: Color black; > openInWindow > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 20, 2009

Re: [Pharo-project] [ANN] 10209 Watchit integration

by StÃ©phane Ducasse

as a debugging tool I'm not sure that we want to have it more complex and with a window now I may be wrong so I will let the other give their point of view first On Jan 20, 2009, at 9:22 AM, Torsten Bergmann wrote: > Hi Stef, > >> Now it is nicely integrated in pharo. > > Not yet - why not open it in a separate window instead of a plain > morph on the desk? > This would be more consistent with inspect it, debug it and explore > it from the same menu. > You can also collapse the watch window and move it easily around... > > see code below. > > Bye > Torsten > > ----------------------------------------------------------------------------------------- > watchIt > > | result | > > self handleEdit: > [result := textMorph editor compileSelectionAsBlock. > ((result isKindOf: FakeClassPool) or: [result == #failedDoit]) > ifTrue: [^self flash]]. > (RectangleMorph new) > layoutPolicy: TableLayout new; > layoutInset: 3; > listDirection: #topToBottom; > hResizing: #shrinkWrap; > vResizing: #shrinkWrap; > addMorphBack: (StringMorph contents: textMorph editor selection); > addMorphBack: ((UpdatingStringMorph on: result selector: #value) > stepTime: 500; > maximumWidth: nil; > growable: true); > color: Color white; > borderColor: Color black; > openInWindow > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 20, 2009

[Pharo-project] [ANN] 10209 Watchit integration

by Torsten Bergmann

Hi Stef, >Now it is nicely integrated in pharo. Not yet - why not open it in a separate window instead of a plain morph on the desk? This would be more consistent with inspect it, debug it and explore it from the same menu. You can also collapse the watch window and move it easily around... see code below. Bye Torsten ----------------------------------------------------------------------------------------- watchIt | result | self handleEdit: [result := textMorph editor compileSelectionAsBlock. ((result isKindOf: FakeClassPool) or: [result == #failedDoit]) ifTrue: [^self flash]]. (RectangleMorph new) layoutPolicy: TableLayout new; layoutInset: 3; listDirection: #topToBottom; hResizing: #shrinkWrap; vResizing: #shrinkWrap; addMorphBack: (StringMorph contents: textMorph editor selection); addMorphBack: ((UpdatingStringMorph on: result selector: #value) stepTime: 500; maximumWidth: nil; growable: true); color: Color white; borderColor: Color black; openInWindow -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

Jan. 20, 2009