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

Re: [Pharo-project] Issue 3594 in pharo: Expander needs tweaking to enable resize in a TableLayout

by pharo＠googlecode.com

Comment #7 on issue 3594 by marcus.d...(a)gmail.com: Expander needs tweaking to enable resize in a TableLayout http://code.google.com/p/pharo/issues/detail?id=3594 in 13020 TODO: 1.2

Jan. 26, 2011

[Pharo-project] [update 1.3] #13020

by Marcus Denker

13020 ----- Issue 3596: 2nd part Headless (3rd part) Issue 3594: Expander needs tweaking to enable resize in a TableLayout (part 2) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 26, 2011

Re: [Pharo-project] Issue 3596 in pharo: 2nd part Headless

by pharo＠googlecode.com

Comment #4 on issue 3596 by marcus.d...(a)gmail.com: 2nd part Headless http://code.google.com/p/pharo/issues/detail?id=3596 in 13020

Jan. 26, 2011

Re: [Pharo-project] Issue 3596 in pharo: 2nd part Headless

by pharo＠googlecode.com

Comment #3 on issue 3596 by marcus.d...(a)gmail.com: 2nd part Headless http://code.google.com/p/pharo/issues/detail?id=3596 13010

Jan. 26, 2011

Re: [Pharo-project] Issue 3596 in pharo: 2nd part Headless

by pharo＠googlecode.com

Comment #2 on issue 3596 by marcus.d...(a)gmail.com: 2nd part Headless http://code.google.com/p/pharo/issues/detail?id=3596 some more fixes Attachments: Headless.1.cs 332 bytes ContextPart-runSimulatedcontextAtEachStep.st 1.1 KB

Jan. 26, 2011

[Pharo-project] Easy access on pharo-project.org

by Torsten Bergmann

We have the shortcut to the collaborative book: http://book.pharo-project.org Would it be possible: 1. to access the build server https://pharo-ic.lille.inria.fr/hudson/ under a simple name like: http://hudson.pharo.org or http://ci.pharo.org (ci = continuos integration) 2. to access the issue tracker http://code.google.com/p/pharo/issues under http://issues.pharo-project.org or http://bugs.pharo-project.org 3. to access the wiki http://code.google.com/p/pharo/w/list under http://wiki.pharo-project.org 4. And the book page http://pharo-project.org/documentation/tutorials-books has no reference to the collaborative book http://book.pharo-project.org Thx T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Jan. 26, 2011

[Pharo-project] Issue 3597 in pharo: Fix RemoteString API

by pharo＠googlecode.com

Status: Fixed Owner: Benjamin...(a)gmail.com Labels: Type-Seed Milestone-1.3 New issue 3597 by Benjamin...(a)gmail.com: Fix RemoteString API http://code.google.com/p/pharo/issues/detail?id=3597 RemoteString >>#text used to return a String, and for each instance of RemoteString: each string = each text Looks weird ... Due to that, you had some message like: MyObject newString: classComment text Moreover, due to the use of text instead of string, you couldn't substitute a RemoteString and a String :) Attachments: FixRemoteStringAPI.1.cs 1.4 KB

Jan. 26, 2011

Re: [Pharo-project] Issue 3594 in pharo: Expander needs tweaking to enable resize in a TableLayout

by pharo＠googlecode.com

Updates: Status: Started Comment #6 on issue 3594 by tudor.gi...(a)gmail.com: Expander needs tweaking to enable resize in a TableLayout http://code.google.com/p/pharo/issues/detail?id=3594 I attach here a second changeset from Gary that deals with a special case of resizing. It also introduces Announcements for ExpanderMorph. I think we should integrate these as well. Attachments: ExpanderTweak.2.cs 7.0 KB

Jan. 26, 2011

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by Henrik Sperre Johansen

On 26.01.2011 08:13, HwaJong Oh wrote: > My last package is Balloon-hjo.72.mcz. > It is small testing& refactoring on Ballloon supporting collections. > > I wonder this type of work is acceptable? > > Best Regards Refactorings and more tests are certainly welcome! Here's a few comments: While I like keeping common functionality in one place, I'm not sure creating a new helper object for each at:/at:put: access is a good idea. Nor keeping the helper cached to avoid this. Have you considered using a Trait instead? To me it seems like a good use-case for one. To the tests: - setUp uses at:put:. testAt asserts the values set in setUp. Thus, is it not really just another at:put: test? Does it test something not covered by the other at:put: test(s)? - testAtPutLargeInteger uses a static integer. This is not ideal, as the range of SmallInteger depends on platform (I realize though, that it is large enough for it not to fail on 64bit as well). Using f.ex SmallInteger maxVal + staticInteger is more intention revealing. Although, max/minVal actually returns a constant at the moment rather than a platform-specific value, and thus would fail on 64bit. I'd consider this a bug which it'd be nice if a test exposed :) - testWriteXYEndianOn uses 256*256*256. etc. Probably down to preference, but I think they'd looks nicer using the bitShift: (or #<< if you prefer less parenthesis) operator. Cheers, Henry

Jan. 26, 2011

[Pharo-project] [update 1.3] #13019

by Marcus Denker

13019 ----- Issue 3583: Shout should only be active in code panes Issue 3594: Expander needs tweaking to enable resize in a TableLayout Issue 3590: AntiAliased fix Issue 3596: 2nd part Headless next: fix build server script to not kill the process when the image generates a log ;-) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 26, 2011