March 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Immutability, read-only objects
by Janko MivÅ¡ek March 29, 2011

March 29, 2011

Dear all, What is current status of immutable/read-only support in VM? Or more broader, object instvar change catching support (for which I mostly need immutability anyway)? Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

2 1

[Pharo-project] Issue 3878 in pharo: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: New Owner: ---- New issue 3878 by fernando...(a)gmail.com: #enableTextChange selector name is misleading, i propose changing the name to #canChangeText http://code.google.com/p/pharo/issues/detail?id=3878 It's sent by the TextEditor, to ask the morphs for permision to change the contents. Attachments: enableTextChange.1.cs 2.2 KB

1 5

[Pharo-project] Issue 3713 in pharo: Additional obsolete methods in PharoCore-1.2.image (2/15/11 9:08am)
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: New Owner: ---- New issue 3713 by DougEdmu...(a)gmail.com: Additional obsolete methods in PharoCore-1.2.image (2/15/11 9:08am) http://code.google.com/p/pharo/issues/detail?id=3713 I did a search through PharoV10.sources for comments which reported methods as 'obsolete'. I looked for them in Pharo, using the 2/15/11 9:08am image (from Pharo-1.2.zip). These methods are still in the 1.2 image: !Canvas methodsFor: 'drawing' stamp: 'ar 6/17/1999 01:30'! line: pt1 to: pt2 brushForm: brush "Obsolete - will be removed in the future"! ! !Canvas methodsFor: 'drawing' stamp: 'ar 6/17/1999 01:32'! point: p color: c "Obsolete - will be removed in the future"! ! !Canvas methodsFor: 'drawing-obsolete' stamp: 'ar 2/12/2000 18:11'! imageWithOpaqueWhite: aForm at: aPoint "Note: This protocol is deprecated. Use #drawImage: instead" self image: aForm at: aPoint sourceRect: (0@0 extent: aForm extent) rule: Form over. ! ! !Canvas methodsFor: 'drawing-text' stamp: 'ar 12/31/2001 02:40'! text: s at: pt font: fontOrNil color: c "OBSOLETE" ^ self drawString: s at: pt font: fontOrNil color: c! ! !Canvas methodsFor: 'drawing-text' stamp: 'ar 12/31/2001 02:40'! text: s bounds: boundsRect font: fontOrNil color: c "OBSOLETE" ^self drawString: s in: boundsRect font: fontOrNil color: c! ! !FontSet class methodsFor: 'installing' stamp: 'damiencassou 5/30/2008 14:51'! fontNamed: fontName fromLiteral: aString "NOTE -- THIS IS AN OBSOLETE METHOD THAT MAY CAUSE ERRORS. The old form of fileOut for FontSets produced binary literal strings which may not be accurately read in systems with support for international character sets. If possible, file the FontSet out again from a system that produces the newer MIME encoding (current def of compileFont:), and uses the corresponding altered version of this method. If this is not easy, then file the fontSet into an older system (3.7 or earlier), assume it is called FontSetZork... execute FontSetZork installAsTextStyle. copy the compileFont: method from this system into that older one. remove the class FontSetZork. Execute: FontSet convertTextStyleNamed: 'Zork', and see that it creates a new FontSetZork. FileOut the new class FontSetZork. The resulting file should be able to be read into this system. " ^ StrikeFont new name: fontName; readFromStrike2Stream: aString asByteArray readStream! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! classModified: anEvent "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! classMoved: anEvent "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! classRemoved: anEvent "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! methodModified: anEvent "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! methodMoved: anEvent "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! methodRemoved: anEvent "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! registerForNotifications "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! registerForNotificationsFrom: aNotifier "obsolete - remove this later"! ! !MCPackageManager methodsFor: 'system changes' stamp: 'ar 4/26/2005 22:17'! systemChange: anEvent "obsolete - remove this later"! ! !Process methodsFor: 'accessing' stamp: 'ar 12/7/2007 17:06'! offList "OBSOLETE. Process>>suspend will atomically reset myList if the process is suspended. There should never be a need to send #offList but some older users may not be aware of the changed semantics to suspend and may try the old hickadidoo seen here: (suspendingList := process suspendingList) == nil ifTrue: [process == Processor activeProcess ifTrue: [process suspend]] ifFalse: [suspendingList remove: process ifAbsent:[]. process offList]. Usages like the above should be replaced by a simple 'process suspend' " myList := nil! !

1 5

[Pharo-project] Issue 3902 in pharo: Text field converter refactoring
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3902 by marcus.d...(a)gmail.com: Text field converter refactoring http://code.google.com/p/pharo/issues/detail?id=3902 From: Gary Chambers Subject: [Pharo-project] Text field converter refactoring Date: March 29, 2011 11:21:49 AM GMT+02:00 Hi all, I've refactored the ObjectStringConverter support to be more flexible and provide feedback in the UI (via corner triangle). Also, should be no more MNU's in, for example, ColorSelectorDialogWindow when numeric fields are made empty! Note that any fields in use need to be recreated. A save of the image (or otherwise) is required to reinitialize the EditorFindReplaceDialogWindow singleton. Attached cs. Attachments: TextFieldRegex.3.cs 7.9 KB

1 2

Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
by Marcus Denker March 29, 2011

March 29, 2011

On Mar 29, 2011, at 9:49 PM, Lukas Renggli wrote: > I don't care if we move to 6505, I will just have to update my build > server to use the new VM as well. So far I built with the old VM to > make sure that the images also work on older VMs. > It's actually good to build 1.2 with the old format... this simplifies life for people who don't want to update the VM (which can be difficult, e.g. because of plugins). Wit 1.3 we will be Cog only, StackVM and Jit, and retire the Squeak VM. And of course, for 1.3 we will automatize even more to have less things that need to be done by hand. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 1

[Pharo-project] Issue 3909 in pharo: ObjectStringConverter refactored
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: FixProposed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3909 by stephane...(a)gmail.com: ObjectStringConverter refactored http://code.google.com/p/pharo/issues/detail?id=3909 I've refactored the ObjectStringConverter support to be more flexible and provide feedback in the UI (via corner triangle). Also, should be no more MNU's in, for example, ColorSelectorDialogWindow when numeric fields are made empty! Note that any fields in use need to be recreated. A save of the image (or otherwise) is required to reinitialize the EditorFindReplaceDialogWindow singleton. Attachments: TextFieldRegex.3.cs 7.9 KB

1 1

[Pharo-project] Issue 3845 in pharo: Polymorph extension shortSummary is not programmed the object way
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: Accepted Owner: nicolas....(a)gmail.com New issue 3845 by nicolas....(a)gmail.com: Polymorph extension shortSummary is not programmed the object way http://code.google.com/p/pharo/issues/detail?id=3845 It is programmed with a sequence of self isThisOrThat ifTrue: [] ifFalse: [] Please don't do that. Just implement a shortSummary where due (with default behaviour ^summary) and use it ! With current shortSummary implementation, a MC with a postscript cannot be diffed.

1 2

[Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
by Marcus Denker March 29, 2011

March 29, 2011

https://gforge.inria.fr/frs/download.php/28417/PharoCore-1.2.1.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Issue 3852 in pharo: 1.2 Build is broken
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3852 by marcus.d...(a)gmail.com: 1.2 Build is broken http://code.google.com/p/pharo/issues/detail?id=3852 DuplicatedVariableError: stylingActive is already defined in Workspace Not clear why it suddenly tries to load different code.

1 1

Re: [Pharo-project] Issue 1894 in pharo: Rescue Sophie audio
by pharo＠googlecode.com March 29, 2011

March 29, 2011

Updates: Status: Closed Comment #1 on issue 1894 by marcus.d...(a)gmail.com: Rescue Sophie audio http://code.google.com/p/pharo/issues/detail?id=1894 Moved to http://code.google.com/p/pharo/wiki/IdeasToImplement

1 1