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

[Pharo-project] update 13195/Remove Simple Morphic
by Torsten Bergmann May 13, 2011

May 13, 2011

Looks like #13195 removes Simple morphic. I havent seen a post on this update number here on the list, so why was it removed when it was introduced recently? Is it moved from core to dev image? Also note that empty SimpleMorphic-XXX" class categories are still there. Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

2 1

Re: [Pharo-project] Need help with 1.3 Full Image
by Marcus Denker May 13, 2011

May 13, 2011

On Fri, May 13, 2011 at 10:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > I'm really surprised. I'm also surprised that you say that when you did not > even tried to port your tools to 1.2 during the release candidate phase and that people > tried and failed and you started to port your tool when 1.2 was released. > As a result, we will just never do a beta/rc1/rc2/rc3 phase again. When 1.3 will be released, it will be what used to be beta. And everyone who just uses releases will be therefore tricked into using it :-) Marcus -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

2 1

Re: [Pharo-project] Need help with 1.3 Full Image
by Marcus Denker May 13, 2011

May 13, 2011

On May 13, 2011, at 9:38 AM, Lukas Renggli wrote: >> I personally think this really wants to tell us something, but that's just me. > > Yes, indeed. Thank you for fixing all the things in Pharo 1.2. This is > really important. > > I really don't understand why Pharo is pushing so hard towards Pharo > 1.3 while even Pharo 1.2.1 is not really stable for daily work yet. Keep in mind that 1.2.1 is unchanged. Fixes are added to 1.2.2a, and due to a change in 1.2 (that was *a bad idea*!!!), you need to set the version number to 1.2.2a to see any updates. The first update of 1.2.2a fixes this wrong change. We should release 1.2.2 just to get this problem fixed and update updates again. Another thing I would like is to not have one rolling release for stable. that is, there is 1.2 update 12XXX And nothing else, fixes get pushed, images build by Hudson, no releases on that level. > The number of really critical bugs that appear in Pharo 1.2 every day There is no bug reported in 1.2 that is not already in 1.1: http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.2.2 > makes me wonder how many people are just stuck with Pharo 1.1? :-( Maybe we need a dedicated stable team? From my financing, it would be hard to justify working purely on 1.2... I can work on 1.3, because we want to change the system to be something really great. But maintaining 1.2 is hard to justify as a researcher.... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] About Releasing 1.2.2
by Marcus Denker May 13, 2011

May 13, 2011

Hello, We should do a 1.2.2 release very soon. I suggest this weekend for Core, and then the Agony beginns again to find someone who is willing to fix Full... 1) One Thing to do in Core 1.2.2: - http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.2.2 Issue 3732: Change #standardWindowExtent Was: default omni browser size bigger The problem is that the RealEstateAgent is made for 1996 iMacs.. so it actually gives out very small windows up to a tiny maximum, leading for OB to open witha very, very very ugly small screen. Workaround Fix: hack to return a minum windows that is large enough (war to go, I guess) Real fix: rewrite RealEstateAgent to do something sensible for today's screens. (for later) 2) One Thing to do in Full 1.2.2: - http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2.2-DevImage Issue 4166: Failing Tests: OBFakeBrowserTest (ConfigurationOfOmniBrowser needs update) This means someone needs to update the MetaCello config to load the right versions of OB (which need to be copied to the pharo OB repo, too) Wo wants do do these? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Small question in OSProcess
by Adrien BARREAU May 13, 2011

May 13, 2011

Hi all, I just have a little question: Is there a way to change the working directory of my terminal with something in OSProcess? I mean: - I know I can change the working directory of the current process with "OSProcess thisOSProcess chDir: '/'" but of course it does nothing on the terminal - "OSProcess thisOSProcess command: 'cd /'" does absolutly nothing I hope it's clean enough. Regards, Adrien.

3 2

[Pharo-project] New transcript questions and notes
by DougEdmunds May 13, 2011

May 13, 2011

Using Pharo1.3a Latest update: #13193 Are there any plans to give the new transcript window a mouseable menu? If not, buttons for select all and copy would be nice. -- Nothing seems to be happening when clicking 'log to file'. What is the name of the file? Where is it? -- When checking/unchecking/checking 'log to file' will the second checking add to the end of an existing file, or will it start a new one, or wipe out old one and start it over? -- This code does not work right with the new transcript: 1 to: 30 do: [: x | Transcript cr; show: x. (Delay forSeconds: 0.2) wait.]. a) Try it in 1.2 (old transcript) to see how it should work. Old transcript, there's a delay between each line printed. 1.3 (new transcript) there's a total delay first, then all the lines are immediately printed. b) If the length of the entries to the transcript exceeds the size of the window, the lines do not automatically scroll up to be able to see them. Instead, they are added outside of the visible window area. IMO, this must be changed so that whatever gets added to the end of the transcript is immediately visible. c) If cursor is at the bottom (with a vertical scroll bar visible), as soon as a new line is added, the transcript pops back to the beginning again, requiring scrolling to see new entries. This makes any kind of continual stream to the transcript impossible to view. Position the Transcript at the end of the output, then run the 1 to: 30 do: code line again -- it will pop you to the top, not the end. -- Will the vertical size of the header area (Clear, etc) be reduced? It is taller than needed. -- View this message in context: http://forum.world.st/New-transcript-questions-and-notes-tp3516546p3516546.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 2

[Pharo-project] Debugger and Exceptions model
by Igor Stasenko May 13, 2011

May 13, 2011

It would be cool to make debugger be aware of Exceptions, and then make exceptions to designate additional actions which user may perform in addition to "Proceed, Abandon, Debug, Create" Currently all this stuff is hardcoded.. But what i imagine, that if we make debugger to be aware of exceptions (of course if opening debugger is triggered by exception), a debugger could ask exception for additional actions to perform as well as whether immediately open full UI etc. For instance i always wanted that on SubclassResponsibility exception a Debugger can propose me to create a method in subclass, in same way as it proposing to create a method when you got DNU- by adding a 'Create' button. Here the changeset which allows me to do that. But it would be really nice someday to delegate such things to exceptions. -- Best regards, Igor Stasenko AKA sig.

1 0

Re: [Pharo-project] Problem with CompiledMethodTrailer
by Marcus Denker May 12, 2011

May 12, 2011

On May 10, 2011, at 9:32 AM, Mariano Martinez Peck wrote: > > what is even worst, is that even after removing those correct CM, and doing a GC etc...they still don't disappear. > There is ScriptLoader new cleanUpMethods This is called from #cleanUpForRelease and normally should make sure there are no old methods. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

5 17

[Pharo-project] What we do with: "Embed source code for methods which get uninstalled from their classes" ???
by Mariano Martinez Peck May 12, 2011

May 12, 2011

So....we used to have arround CM instances wrong. There was a problem with the trailer and we fix it. http://code.google.com/p/pharo/issues/detail?id=4186 Then we did: http://code.google.com/p/pharo/issues/detail?id=4192 and, dev image took hous to finish: http://code.google.com/p/pharo/issues/detail?id=4200 because the Compiler recompileAll take ages because of the becomeFordward: it does for the #dropSourcePointer then igor solve it, it took less time, but we start to loose the source pointer of COmpiledMethods while loading stuff from MC. in addition, objects as methods started to fail because they do not implement #dropSourcePointer: http://code.google.com/p/pharo/issues/detail?id=4195 so...al users of #run:with:in: should also be broken now, like TestCoverage, etc.... so...what do we do? I would like to: 1) have a fast/normal recompileAll 2) not to loose source code If the only way right now is rollbacking #dropSourcePointer and rollbacking the implementation in objects as methods, please do it. Right now we are in the worst case. For example, today when I discover the bug of loosing sources...I commit my own package with a lots of methods with the decompiled source...it took time to fix it. So I think it is important to fix this. Cheers -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] [ANN] VB-Regex patch available
by Nicolas Cellier May 12, 2011

May 12, 2011

Reinout Heek recently published a patch in cincom store for some Regex pending bugs after a recent mail on vwnc list. I ported this 3-methods patch on Squeak based on latest http://www.squeaksource.com/Regex.htm I have no commit right, so I posted two copies: http://source.squeak.org/inbox/VB-Regex-nice.18.mcz http://www.squeaksource.com/PharoInbox/VB-Regex-nice.18.mcz Note that core Pharo version of Regex is some versions ahead and the patch requires further porting. Nicolas ------------------------------------------------------------------------- Port fixes from Reinout Heek from VW.Regex11 Regex11(1.3.1-soops1) - introduces fix Regex11(1.3.3) - merge above with 1.3.2 Blessing comment: Fixed RxmBranch to do greedy matching instead of first match passes. This entailed adding a collection copy to #currentState, so I expect this to slow down Regex11 a bit (not measured yet). This fixes a bug found a Soops: '.*(ABCD|BC)' asRegex matches: 'fooABCD' and Mantis bug 5391: '15' matchesRegex: '[1-9]|1[0-9]' See http://bugs.squeak.org/view.php?id=5391

3 4