December 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Printing hexadecimal values of a string
by Geoffroy Couprie Dec. 20, 2010

Dec. 20, 2010

Hello all, I get a strange behaviour while trying to print hexadecimal values of a string. Context: I get a SHA1 hash from a binary stream, store it into a string, and I want to display that string (using asHex). Problem: for values inferior to 16, the leading zero is ignored. (15 -> 'F' instead of '0F'). I could modify SmallInteger>>printStringBase: to always include the leading zero, but I fear I'm going to break a lot of code doing that. Is there a better way to fix my problem? apart from using directly the following: aStream do:[:val | val printStringBase:16 nDigits:2] Best regards, Geoffroy

6 12

[Pharo-project] What to do with the PharoOne click encoding ?? Fwd: Issue 3205 in pharo: monticello's error on Linux
by Mariano Martinez Peck Dec. 20, 2010

Dec. 20, 2010

I noticed this problem several times also. I even remeber once I asked why the shell script was sending -encoding utf8 how we can fix it ? can we just ommit it ? what happens when we run a normal vm with a normal image? I guess we don't send any particular encoding there... cheers mariano ---------- Forwarded message ---------- From: <pharo(a)googlecode.com> Date: Mon, Dec 20, 2010 at 11:48 AM Subject: Re: [Pharo-project] Issue 3205 in pharo: monticello's error on Linux To: pharo-project(a)lists.gforge.inria.fr Comment #2 on issue 3205 by sanchezlsp: monticello's error on Linux http://code.google.com/p/pharo/issues/detail?id=3205 Thank you. That works.

1 0

Re: [Pharo-project] Issue 2705 in pharo: Collection enh for Cog
by Marcus Denker Dec. 20, 2010

Dec. 20, 2010

On Dec 20, 2010, at 4:10 PM, Levente Uzonyi wrote: > On Mon, 20 Dec 2010, pharo(a)googlecode.com wrote: > >> >> Comment #5 on issue 2705 by marcus.denker: Collection enh for Cog >> http://code.google.com/p/pharo/issues/detail?id=2705 >> >> I will add just copyUpThrough: >> >> > > #fold: is sent by the Cog VMMaker code, so you either implement it, modify the Cog VMMaker code or you won't be able to build a Cog from a Pharo image (building such an image is a tedious task anyway). We will encounter (and fix) these things when we do the VM auto-build setup. Maybe we then just load a pre-load for things like that. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 2705 in pharo: Collection enh for Cog
by pharo＠googlecode.com Dec. 20, 2010

Dec. 20, 2010

Comment #2 on issue 2705 by marcus.denker: Collection enh for Cog http://code.google.com/p/pharo/issues/detail?id=2705 Next action: - take the code here and make a .cs or Slice out of it

2 5

Re: [Pharo-project] Issue 2247 in pharo: MessageNotUnderstood: NewInspector class>>openOn:withEvalPane:withLabel:
by pharo＠googlecode.com Dec. 20, 2010

Dec. 20, 2010

Comment #3 on issue 2247 by vonbecmann: MessageNotUnderstood: NewInspector class>>openOn:withEvalPane:withLabel: http://code.google.com/p/pharo/issues/detail?id=2247 i tried this issue in Pharo image: Pharo Pharo core version: Pharo-1.1.1--Latest update: #11414 Virtual machine used: 'Squeak3.10.2 of 11 February 2010 [latest update: #9314]' Class browser used (if applicable): OBSystemBrowserAdaptor and it is not working. any idea? Attachments: PharoDebug.log 30.8 KB

1 2

[Pharo-project] [update 1.2] #12283
by Marcus Denker Dec. 20, 2010

Dec. 20, 2010

12283 ----- Issue 2690: dropping a cs file and cancelling the chooser raises and exception Issue 2705: Collection enh for Cog -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 2690 in pharo: dropping a cs file and cancelling the chooser raises and exception
by pharo＠googlecode.com Dec. 20, 2010

Dec. 20, 2010

Comment #5 on issue 2690 by marcus.denker: dropping a cs file and cancelling the chooser raises and exception http://code.google.com/p/pharo/issues/detail?id=2690 For 1.2, I would just fix the nil check. I will add a new entry for cleaning up DefaultExternalDropHandler vs ExternalDropHandler Attachments: FixFor2690.1.cs 597 bytes

1 1

[Pharo-project] Issue 3467 in pharo: Clean up ExternalDropHandler vs. DefaultExternalDropHandler?
by pharo＠googlecode.com Dec. 20, 2010

Dec. 20, 2010

Status: Accepted Owner: marcus.denker New issue 3467 by marcus.denker: Clean up ExternalDropHandler vs. DefaultExternalDropHandler? http://code.google.com/p/pharo/issues/detail?id=3467 We fixed Issue 2690 by just fixing the nil check. But maybe we should clean up the dophandlers? Comment 1 by project member snoobabk(a)yahoo.ie, Aug 05, 2010 Error was happening because of incorrect nil check and it happens for any file dropped which has more than one service registered. Instead of fixing nil check, decided to rather remove class DefaultExternalDropHandler as it was doing same checks as ExternalDropHandler class. Because of this it would bring up the same chooser if the first chooser was cancelled. It also delegated to the same default behaviour i.e. fileStream edit. To add more handlers use ExternalDropHandler class>>registerHandler:. (see ExternalDropHandler class>>initialize see SLICE-Issue-2690-DropHandlerChooserCancelFix-CarloTeixeira.1

1 0

[Pharo-project] Issue 3460 in pharo: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812
by pharo＠googlecode.com Dec. 20, 2010

Dec. 20, 2010

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2-DevImage New issue 3460 by marcus.denker: [Failing Test] ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812 http://code.google.com/p/pharo/issues/detail?id=3460 ToolsTest.Inspector.WeakSetInspectorTest.testSymbolTableM6812

1 2

Re: [Pharo-project] Are we tagging 1.2 dev issues?
by Marcus Denker Dec. 20, 2010

Dec. 20, 2010

On Dec 20, 2010, at 4:27 AM, Guillermo Polito wrote: > I found only 5 in the issue tracker, hehe. Maybe those are the only reported by now, maybe not. > > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.2-DevImage… > Yes, these are the only reported issues (issues for 1.2 that are related to the packages or packaging of the full image). I am sure there are ore bugs... we have 21 failing test. 9 of those are from Core, but 12 from dev. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 2