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

[Pharo-project] Issue 3945 in pharo: Remove squeakland plugin methods from SystemVersion
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3945 by marcus.d...(a)gmail.com: Remove squeakland plugin methods from SystemVersion http://code.google.com/p/pharo/issues/detail?id=3945 Remove squeakland plugin methods from SystemVersion Attachments: CleanPlugin.1.cs 507 bytes

1 1

[Pharo-project] Issue 3946 in pharo: remove some more uniclasses/player related code
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3946 by marcus.d...(a)gmail.com: remove some more uniclasses/player related code http://code.google.com/p/pharo/issues/detail?id=3946 remove some more uniclasses/player related dead code Attachments: Clean.1.cs 615 bytes

1 3

[Pharo-project] Issue 3947 in pharo: remove #floodFill:
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3947 by marcus.d...(a)gmail.com: remove #floodFill: http://code.google.com/p/pharo/issues/detail?id=3947 Form removeSelector: #floodFill:at:! Form removeSelector: #floodFill:at:tolerance:! ... references non-existing class. Not called. Attachments: FloodFill.1.cs 180 bytes

1 1

[Pharo-project] Issue 3949 in pharo: Coverage for Cog
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: FixProposed Owner: renggli Labels: Milestone-1.1.2 New issue 3949 by renggli: Coverage for Cog http://code.google.com/p/pharo/issues/detail?id=3949 The fix below makes sure that the coverage method is properly flushed from the method cache. It doesn't seem to yet fix all problems of the coverage tool on Cog but it definitely works better: Name: SUnitGUI-lr.71 Author: lr Time: 3 April 2011, 11:02:41 am UUID: 8098bb1d-fd66-49a3-810c-7e536fff05c7 Ancestors: SUnitGUI-StephaneDucasse.70 - make sure that the coverage tools properly flushes the method cache

1 2

[Pharo-project] Pharo 1.3 process
by laurent laffont April 3, 2011

April 3, 2011

Hi, as I'm a little lost on Pharo 1.2 (1.2.1 full was announced but I haven't seen 1.2.0, no big party, no 1 million download contest, BBC announcement... :) I wonder how we can improve the process for 1.3. I'm thinking about: - not starting Pharo 1.4 too soon as I feel it will steal energy from Pharo 1.3. - freezing early to have shorter release and have less stuff to fix with maximum energy (it seems energy go down quickly in the fixing period) - a failing test should be highest priority: it's easier to fix a broken feature/test as soon as it appears - one guy should drive the release (I feel that Mariano did this for Pharo 1.1 and we know who we should talk to). Any idea ? Laurent.

2 1

Re: [Pharo-project] [ANN] For testing: 1.2.1 One-Click
by Marcus Denker April 3, 2011

April 3, 2011

On Apr 3, 2011, at 6:17 PM, Schwab,Wilhelm K wrote: > Out of the box, system browsers are opening with a scroll bar between the lists and code pane. Click on it, and the bar disappears. > Yes, a known bug open since Feb 24, 2011. http://code.google.com/p/pharo/issues/detail?id=3754 > Curious which vm was in use, I tried: > > SmalltalkImage current vmVersion 'Squeak3.10.2 of ''5 June 2008'' [latest update: #7179]' > > Looks weird?? Ask the vm itself. In a terminal (I think in the correct place): > Yes, we just use the same VM than in the 1.1 OneClick. If someone can do better, please do. I can not, I am exhausted.... > ./squeakvm -version > 4.0.3-2202 #1 XShm Tue Apr 13 11:56:47 PDT 2010 gcc 4.3.2 > Linux vps2.piumarta.com 2.6.18-028stab053.10-ent #1 SMP Thu Feb 28 20:34:08 MSK 2008 i686 GNU/Linux > plugin path: /somewhere/Contents/Linux/ [default: /somewhere/Pharo-1.2.1/Contents/Linux/] > > Ubuntu Lucid. > > oCompletion is not going away easily. No denigration of the hard work that went into it, I want to simply turn it off, read what it otherwise can't help covering, and type myself. > Yes, the details in interaction of both ecompletion and the magical treatment of special characters ()'' should be improved... One of the first steps to do this is to actually use these things on a daily basis. With the Core vs. Full image, there is the huge problem that after the first 100 updates are in the unstable, I use the unstable. And there is no Full for unstable, bug report from Mar 20, 2011: http://code.google.com/p/pharo/issues/detail?id=3837 The thing is that all things, even the smallest tiniest triviality, happens if someone *does* it. Nothing happens by itself. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] Issue 3645 in pharo: Update Hudson One-Click build files for 1.2
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3645 by marcus.d...(a)gmail.com: Update Hudson One-Click build files for 1.2 http://code.google.com/p/pharo/issues/detail?id=3645 -> current VM Please list everything else...

1 5

Re: [Pharo-project] who is using softSqueak and standard Squeak
by Marcus Denker April 3, 2011

April 3, 2011

On Apr 2, 2011, at 9:55 AM, laurent laffont wrote: > Patrick, > > I think we should have a ConfigurationOfPharoThemes with all the themes you have made + current ones. I can help (may be a good subject for a our weekly coding-dojo) > > PharoCore should have only one theme I think. > And in turn this means that pharo full has *all* of them? Nonono... it has already *far* too much stuff nobody cares about. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] Issue 3911 in pharo: Change updater to allow updating a release image
by pharo＠googlecode.com April 3, 2011

April 3, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3911 by marcus.d...(a)gmail.com: Change updater to allow updating a release image http://code.google.com/p/pharo/issues/detail?id=3911 right now (1.2 and 1.3), the update logic checks for some character in the version number to allow updating and image. Now the fact is that people only look at released images. Leading to lots of suggestions of fixes directly after a release, but no way to update that release. Allowing the update process to update release images will remove a *significant* amount of work from the release manager who now needs to do a complete release cycle even for point releases (1.2.1a followed by 1.2.1 folowed by 1.2.2a followed by 1.2.2... with lots of manual intervention).

1 5

Re: [Pharo-project] syntax highlighting for (stateful) traits (non-local methods)
by Marcus Denker April 3, 2011

April 3, 2011

On Apr 3, 2011, at 1:29 PM, Alexandre Bergel wrote: > I guess that what Stef meant is the following: > One of the problems when sharing code among mixin and stateful-trait application is that the physical layout of instances varies between mixin applications. (Section 6.5 of Yes, and the physical layout is now modeled as objects. (See Hierarchy of AbstractLayout). > > We have T.y and C.x > T has a method #getY, for which its bytecode returns the first slot (i.e., y). If C uses T, the #getY needs to be adapted to return the second slot right? > Yes. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0