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

[Pharo-project] [update 1.3] #13319
by Marcus Denker Oct. 28, 2011

Oct. 28, 2011

13319 ----- Issue 4934: Workspace Watch It menu entry action is broken http://code.google.com/p/pharo/issues/detail?id=4934 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.4] #14211
by Marcus Denker Oct. 28, 2011

Oct. 28, 2011

14211 ----- Issue 4937: Squeaksource 3 place for gofer http://code.google.com/p/pharo/issues/detail?id=4937 Issue 4934: Workspace Watch It menu entry action is broken http://code.google.com/p/pharo/issues/detail?id=4934 Issue 4936: Temporarily switching to the non-interactive UIManager http://code.google.com/p/pharo/issues/detail?id=4936 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] Text for 1.3 announcement?
by Marcus Denker Oct. 27, 2011

Oct. 27, 2011

On Oct 27, 2011, at 9:33 PM, Bernhard Pieber wrote: >> > What I always wanted to ask and did not dare until now: What is the meaning of a 1.3 tag? It *could* mean the following: > a) Those are the issues that are show stoppers before a release can be done. Yes, this is the meaning before the release is released. When a release gets close, we start to tag just the very important issues. With 1.2, we really managed to release when there where no issues tagged 1.2. With 1.3, there was just not enough energy left to do that. (yet, the issues left after the release where not of the kind of real show-stoppers, either.) We start with the next release at the point when a version gets frozen. Because lots of "trivial" changes accumulate in the tracker that can not be added to the to-be-stable version, yet not integrating will lead to a *huge* and unmanagable backlog. Thus even though 1.3 with 315 updates was released this week, there is a 1.4 with already 215 updates... (Or another number: 1.4 is 412 closed issues... the overall open issues is 427) But 1.3 is special, as we should have release it 4 months ago. > b) Those are known issues in 1.3. After the release, the issues tagged 1.3 are bugs found in 1.3 that are deemed to be fixed in 1.3. two cases are possible: 1) The bug is really something that lots of people will see, so we should fix it. 2) The reporter of the bug provides a perfect fix that can be harvested for 1.3 without any more work *and* where is is clear that it will not lead to more problems later *and* where the issue is deemed important If a company says "we use this in production" (e.g. Netstyle/CMSbox provides fixes of that sort, as an example) > At first I thought it meant a). When you removed the "release candidate" status from the 1.3 download page I started to doubt this. ;-) > My next assumption was it meant b). Hence my humble suggestion. Now it seems it must mean something completely different. No, it means both, depending on if the release is done or not. In a perfect world, the release is done without any open issues (by moving them to the next release, mostly). We missed that window for 1.3, mostly because of the problem of having two images (full and core). With the maintainers of the non-core packages only looking at released pharo versions, this was doomed to fail (to release both core and full at the same time). With 1.4, this is fixed. There is only one image, so we will just release 1.4 when a) all tests are green b) there are no issues tagged 1.4 Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] aSet collect: answers aSet??
by Clara Allende Oct. 27, 2011

Oct. 27, 2011

Hi guys.. This morning some students came with an exercise like this: (Set with: 1 with: 2 with:3 with:4 with:5) collect:[:e | e even]. a Set(false true) But they don't want to get aSet, (regardless this particular example doesn't make sense)... the question is, why if I send collect: to aSet I get aSet and not aBag? What happens if I *want* repeated elements after the transformation? :( And when did this behavior change? -- "*Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.*" Linus Torvalds

9 14

[Pharo-project] the moose call
by Tudor Girba Oct. 27, 2011

Oct. 27, 2011

Hi, The other week I was at GOTO Aarhus. This was a great conference. And I got to talk about humane assessment with Moose. The presentation seemed to have captured some attention:http://martinfowler.com/bliki/gotoAarhus2011.html I think it's great that a project that was built mostly on the research side of the world can capture industry attention. This shows what can be achieved when innovation is married with long-term engineering effort. And it's not that we did not publish anything in the meantime either -- some more than 200 publications stand witness that science was not neglected. Even if I was the one presenting, the value of the work comes from many contributors. If we were to count, the effort around Moose totals more than 200 man-years of research and development. Moose has long passed the research prototype state. The philosophy behind Moose is to reinvent software and data analysis by making it accessible and tailorable. We lived this philosophy in one way or another, but it was never quite explicit. Now we have name for it: humane assessment. This is a new approach in the software engineering arena, and it can have a significant practical impact. So, here is my call. Invest in Moose. Let's change the status quo. Again from Smalltalk. How? â¢ Just play with it. Take an afternoon and load your system into Moose, build a browser, play with a visualization. And get back to us with questions, suggestions, documentation or code. â¢ Take an hour to read through humane-assessment.com. And get back to us. â¢ Help us reshape the http://moosetechnology.org webpage. â¢ Just get involved. There is always room for a contribution. You do not have to be a specialist. In fact, given that we aim to invent what does not yet exist, none of us are. Cheers, Doru -- www.tudorgirba.com "Don't give to get. Just give."

2 1

Re: [Pharo-project] Text for 1.3 announcement?
by Marcus Denker Oct. 27, 2011

Oct. 27, 2011

On Oct 25, 2011, at 8:24 PM, Bernhard Pieber wrote: > May I humbly suggest to at least add a link to known open issues for 1.3 right next to the release download? Then at least a newbie knows what to expect. > There is nothing different with 1.3 than with any other release we did. And the discussion was more about unknown bugs, not known ones. "You can not release because maybe I found a bug yesterday that I have not yet reported". To make is clear: there are 7 (seven) open issues tagged for 1.3: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 Most of which are not even show stoppers (are already a bug in 1.2, just cosmetic...) None is important enough to have seen any work done since the last sprint. In a way of course many reports on the issue tracker are describing an improvement or problem that could be related to 1.3: http://code.google.com/p/pharo/issues/list These are 421 issues. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] Issue 4696: Rename Smalltalk>>garbageCollectAndReport and Smalltalk>>bytesLeftString
by Bernardo Ezequiel Contreras Oct. 27, 2011

Oct. 27, 2011

Hi all, i would like to fixed this issue 4696<http://code.google.com/p/pharo/issues/detail?id=4696>. could we agree on the new names? read the issue and please add your propose. thanks.

1 0

[Pharo-project] Weird Settings filtering
by Mariano Martinez Peck Oct. 27, 2011

Oct. 27, 2011

Hi Alain. I found something weird with the filtering of the Settings browser. I installed keymapping by Gofer new squeaksource: 'ShortWays'; package: 'ConfigurationOfKeymapping'; load. (ConfigurationOfKeymapping project version: #bleedingEdge) load Now...if you open the settings browser you see the category "Keymappings". But if I go to the input field, type "keymap" and hit enter, I see a result that contains "Keymapping" but not its item. So...it seems that the settings searches in the items of the category but not in the category name. So I wonder.... show we show the list if a category name matches? thanks -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] Zinc and P2P
by Johannes Rasche Oct. 27, 2011

Oct. 27, 2011

Hi Sven or whoever feels concerned, I'm planning to use Zinc and have a question, which might sound trivial for networking experts: is it sufficient for Zn-Server to work if someone using Zn-Client knows my actual IP-adr (plus username and pw)? Thanks in advance Johannes Johannes Rasche mail: johannesrasche(a)me.com www: http://myNeat.net

4 6

[Pharo-project] [update 1.4] #14210
by Marcus Denker Oct. 27, 2011

Oct. 27, 2011

14210 ----- Issue 3432: Color>>fromString fix http://code.google.com/p/pharo/issues/detail?id=3432 -- Marcus Denker -- http://marcusdenker.de

1 0