- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3888 in pharo: Move Digital Signatur code to System-Hashing package

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3888 by marcus.d...(a)gmail.com: Move Digital Signatur code to System-Hashing package http://code.google.com/p/pharo/issues/detail?id=3888 There are two implementations of SHA1 in the system. This changeset just moved the SHA1/DSA code into the Hashing package so it can be merged later. Attachments: DSA.1.cs 6.1 KB

March 27, 2011

Re: [Pharo-project] Issue 2360 in pharo: [Failing Test] nil out locals in a block if readBeforeWritten

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #14 on issue 2360 by nicolas....(a)gmail.com: [Failing Test] nil out locals in a block if readBeforeWritten http://code.google.com/p/pharo/issues/detail?id=2360 Name: SLICE-Issue-2360-SqueakCompilerEnh-Part2-nice.1 Dependencies: CompilerTests-nice.78, Compiler-nice.276 Part2: - correctly move 'locationCounter localsPool' in MethodNode ivar (they were undeclared) - use #notOptimizedIn: rather #than noteOptimized. - do not optimize a todo that would overwrite its limit (common changes with 3677) - connect the OptimizedBlockLocalTempReadBeforeWrittenVisitor to nilReadBeforeWrittenTemps in optimized blocks - add #testOptimizedBlockLocalNilling1 and #testOptimizedBlockLocalNilling2

March 27, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #11 on issue 3545 by marcus.d...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 (No comment was entered for this change.)

March 27, 2011

Re: [Pharo-project] Issue 514 in pharo: macintosh clipboard support is 1984 era, no utf-16

by pharo＠googlecode.com

Updates: Status: Closed Comment #13 on issue 514 by marcus.d...(a)gmail.com: macintosh clipboard support is 1984 era, no utf-16 http://code.google.com/p/pharo/issues/detail?id=514 moved to cog tracker: http://code.google.com/p/cog/issues/detail?id=20

March 27, 2011

Re: [Pharo-project] Issue 1142 in pharo: Pharo supports traits --- but the tools do not

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 1142 by marcus.d...(a)gmail.com: Pharo supports traits --- but the tools do not http://code.google.com/p/pharo/issues/detail?id=1142 added to: http://code.google.com/p/pharo/wiki/IdeasToImplement

March 27, 2011

Re: [Pharo-project] Issue 3885 in pharo: MultiNewParagraphWithSelectionColor should be moved to Deprecated13

by pharo＠googlecode.com

Updates: Status: FixToInclude Labels: Milestone-1.3 Comment #1 on issue 3885 by marcus.d...(a)gmail.com: MultiNewParagraphWithSelectionColor should be moved to Deprecated13 http://code.google.com/p/pharo/issues/detail?id=3885 (No comment was entered for this change.)

March 27, 2011

Re: [Pharo-project] Issue 3882 in pharo: Can't scale imported graphic

by pharo＠googlecode.com

Updates: Status: FixToInclude Labels: Milestone-1.3 Comment #2 on issue 3882 by marcus.d...(a)gmail.com: Can't scale imported graphic http://code.google.com/p/pharo/issues/detail?id=3882 (No comment was entered for this change.)

March 27, 2011

[Pharo-project] Immutability, read-only objects

by Janko MivÅ¡ek

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

March 27, 2011

Re: [Pharo-project] Issue 3882 in pharo: Can't scale imported graphic

by pharo＠googlecode.com

Comment #1 on issue 3882 by hilaire....(a)gmail.com: Can't scale imported graphic http://code.google.com/p/pharo/issues/detail?id=3882 try with: ImageMorph>>#isFlexMorph ^ true it works here.

March 27, 2011

[Pharo-project] Polymorph: DropListMorph event handling

by Daniel Lyons

Hi again, I want to thank everyone for your thoughtful responses to my last message. I'm trying to make a DropListMorph using UITheme for a piece of a GUI I'm working on. I am using a ListModel, and I register an event handler with model#when:send:to:. In the event handler, I see I get the new index value as an argument to my callback, but within the callback model#selectedItem is the old value. Is there an easy way to get the new value instead of the new index, other than by looking up the value in the model#list? Or am I missing something? Is this the correct event framework? I'm under the impression there are several different event frameworks and one of them is more right than the others. Is this the ordinarily correct way to use Polymorph? Thanks, â Daniel Lyons

March 27, 2011