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

[Pharo-project] [update 1.2] #12317
by Marcus Denker Jan. 21, 2011

Jan. 21, 2011

12317 ----- Issue 3564: Comparison of source references (for sorting) Issue 3179: Failing Tests for Monticello -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3419 by marcus.denker: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing http://code.google.com/p/pharo/issues/detail?id=3419 TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

1 7

[Pharo-project] [update 1.3] #13007
by Marcus Denker Jan. 21, 2011

Jan. 21, 2011

13007 ----- Issue 3520: Workspaces do not recognize previously evaluated temps -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Gofer issue
by Torsten Bergmann Jan. 21, 2011

Jan. 21, 2011

Lukas wrote: >Looks good, but instead of duplicating the documentation I would >rather just return the class comment from the help method. Feel free to do so. I just wanted to point you to the fact that you can already use the pier style notation to document stuff. Hope we will now see more docu popping up. And it is now possible to easily extend the help system with other pragma/non pragma based help types. We could have others like <rssHelp: 'url'> and the like in the future. Some more notes on WikiStyleHelp: Currently it uses pier in <wikiStyleHelp:> as default since Alain provided the code for that but in the future I would like to see more syntaxes. Thats already prepared since you can also write <wikiStyleHelp: 'bookName' syntax: #pier Bye T. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

1 0

[Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: Accepted Owner: stephane...(a)gmail.com CC: Benjamin...(a)gmail.com, aplan...(a)gmail.com Labels: Milestone-1.2 New issue 3556 by stephane...(a)gmail.com: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: http://code.google.com/p/pharo/issues/detail?id=3556 Can somebody try by defining these methods !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! stylerStyled: styledCopyOfText textMorph contents runs: styledCopyOfText runs . "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" textMorph updateFromParagraph. selectionInterval ifNotNil:[ textMorph editor selectInvisiblyFrom: selectionInterval first to: selectionInterval last; storeSelectionInParagraph; setEmphasisHere]. textMorph editor blinkParen. self scrollSelectionIntoView ! ! !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! stylerStyledInBackground: styledCopyOfText "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" textMorph contents string = styledCopyOfText string ifTrue: [self stylerStyled: styledCopyOfText]! ! I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: this is probably with a MC problem because in Issue 3486: PluggableTextMorph should be able to support text styling we payed attention to have it. http://code.google.com/p/pharo/issues/detail?id=3486 Benjamin can you have a look?

1 5

Re: [Pharo-project] Issue 3464 in pharo: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Updates: Summary: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory Comment #1 on issue 3464 by marcus.denker: [Failing Test] ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3464 (No comment was entered for this change.)

1 1

[Pharo-project] [update 1.3] #13006
by Marcus Denker Jan. 21, 2011

Jan. 21, 2011

13006 ----- Issue 3556: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] MacMenubarPlugin does not work on Cog?
by Mariano Martinez Peck Jan. 21, 2011

Jan. 21, 2011

Hi. I am testing a Pharo image from here: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… and the Mac host menu doesn't appear at all. I checked with SmalltalkImage current listLoadedModules SmalltalkImage current listBuiltinModules and MacMenubarPlugin is included. However, evaluating "HostSystemMenusMacOSX new " will throw a 'primDeleteMenu: failed' Why the image doesn't throw any error??? Look in HostSystemMenus >> startUp: resuming resuming ifFalse: [^self]. self clearDefault. [self setDefaultMenuProxyClass] ifError: []. So....indeed, setDefaultMenuProxyClass is throwing an error...but we are puting it under the carpet. Anyway, does someone know why this is not working in Cog? because In the standard VM in works perfect. Cheers Mariano

1 0

[Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows
by pharo＠googlecode.com Jan. 21, 2011

Jan. 21, 2011

Status: New Owner: ---- New issue 3458 by mmk.bbt: bug in the class MultiByteFileStream when Pharo running under Windows http://code.google.com/p/pharo/issues/detail?id=3458 PharoCore-1.2beta-12272, Windows Steps to reproduce: (MultiByteFileStream new) wantsLineEndConversion: true; open: 'c:\temp\1.txt' forWrite: true; cr; close. File c:\temp\1.txt contains 3 characters (cr lf lf) instead of two (cr lf). This is due to the fact that the method MultiByteFileStream>> nextPut: There is a double conversion of Cr to CrLf. I think this can be corrected as follows: " MultiByteFileStream>> nextPut: aCharacter aCharacter isInteger ifTrue: [^ super nextPut: aCharacter]. (wantsLineEndConversion == true and: [lineEndConvention notNil]) "# doConversion is inlined here" ifTrue: [ aCharacter = Cr ifTrue: [converter nextPutAll: (LineEndStrings at: # cr) toStream: self] ifFalse: [converter nextPut: aCharacter toStream: self]. ^ aCharacter]. ^ Self converter nextPut: aCharacter toStream: self " Sincerely, Maxim Paste or attach stack trace if applicable (look at the file PharoDebug.log located in the same directory as your image):

1 7

Re: [Pharo-project] [update 1.3] #13005
by Marcus Denker Jan. 21, 2011

Jan. 21, 2011

On Jan 20, 2011, at 10:41 PM, Igor Stasenko wrote: > we're already in 1.3??? > wow... i didn't noticed.. > guys, where is official announcement of new version release? :) no release yet... 1.2 is frozen, but Full does not even build since a week (see https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ ), there are bugs 1.2 http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 1.2 Full http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage (it would actualy be nice if more people would actively help ro reduce these... else there will be never a release. simple as that.) But the stuff for 1.3 starts to accumulate so rapidly that we need to get a way to integrate some of it already, else we are swamped. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0