- Pharo-dev - lists.pharo.org

[Pharo-project] [TODO] Issues tagged 1.4
by Marcus Denker Oct. 30, 2011

Oct. 30, 2011

58 Issues are tagged "1.4" http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.4 The idea is that issues tagged 1.4 are the ones that we need to fix to get 1.4 in a releasable state. Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [TODO] Open bugs in 1.3
by Marcus Denker Oct. 30, 2011

Oct. 30, 2011

http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.3 Core: 4840 Schedule>>between:and:do can iterate over the wrong dates. 4753 Implementors browser doesn't show decompiled source 4745 Debugger opens when trying to get unimplemented calls External Packages: 4889 RBSearchTest has undefined iVar reference 4947 Imported Script Manager scripts disappear 4926 Trait Browsing -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.4] #14212
by Marcus Denker Oct. 30, 2011

Oct. 30, 2011

14212 ----- Issue 4948: Request for a clearer and faster #asFloat conversion http://code.google.com/p/pharo/issues/detail?id=4948 Issue 2975: faster non-primitive String primitives by using #basicAt: instead of #at: + #asInteger/#asciiValue http://code.google.com/p/pharo/issues/detail?id=2975 Issue 2228: dont try to set the position of the file if its not possible http://code.google.com/p/pharo/issues/detail?id=2228 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] Issue tracker states
by Marcus Denker Oct. 30, 2011

Oct. 30, 2011

On Oct 28, 2011, at 7:03 PM, Mariano Martinez Peck wrote: > THanks Marcus :) > Maybe we should put that explanation somewhere? > For example, in http://www.pharo-project.org/community/issue-tracking Yes, I will add it. Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] 1.3Core build moved to Jenkins
by Marcus Denker Oct. 28, 2011

Oct. 28, 2011

Hi, With https://pharo-ic.lille.inria.fr being decommissioned, we are moving everything to Jenkins: https://ci.lille.inria.fr/pharo/ 1.3 Core is now here: https://ci.lille.inria.fr/pharo/view/Pharo%201.3/job/Pharo%20Core%201.3/ please update all links! TODO: -> Full (building now) -> OneClick Scripts -- Marcus Denker -- http://marcusdenker.de

2 2

[Pharo-project] Porting to newer image
by Brian Brown Oct. 28, 2011

Oct. 28, 2011

Hello all, It's been a while since I showed my digital face around here ;) I've got a number of Seaside based web applications that I would like to move into newer pharo images and take advantage of the VM advances that have been made. My stuff is all running under Seaside 2.8/Kom/Dynamic Bindings, etc.... which presents several problems when trying to load into a 1.3 Pharo Core. For example, Dynamic Bindings extends BlockContext, but now BlockClosure is the class that is receiving messages previously intended for BlockContext. I'm sure there will be many more issues like this, so I'm looking for advice on how to proceed. Is there a new Kom/DynamicBindings that works with the newer closure images? Have folks gone to a different web server, and if so, can it work with 2.8? If I can get this all running in a newer image, then my next step would be to port it Seaside 3, but I'm playing serious catchup in the incredible amount of changes since I was using Seaside/Pharo. Thanks for any advice you can give me! - Brian

1 1

[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