February 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3
by Marcus Denker Feb. 24, 2012

Feb. 24, 2012

On Feb 24, 2012, at 10:25 AM, Schwab,Wilhelm K wrote: > Is the missing debugger on your list? I have found 1.3 (speaking as a friend here) to be unusable over this. I get some work done with it, and then debuggers stop opening, rendering the image useless (AFAIK). The list is what people reported. This is turn means: if people do not report a problem, it is not in the list of issues. Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] 1.4 and forward (was Netstyle experience)
by Schwab,Wilhelm K Feb. 24, 2012

Feb. 24, 2012

Stef, Reading this is encouraging. I have not forgotten about 1.4, I have simply been heavily distracted. SIXX is a concern, as I built a lot on top of it and (I *think*) need to get it loaded in order to evaluate Fuel vs. it. XML parsers are a big part of life for SIXX. Regardless of any change I might make, SIXX should be in the image to load "legacy" data (from last month<g>). I will try again soon. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Wednesday, February 22, 2012 3:50 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Netstyle experience (was Do not feed the trolls) On Feb 22, 2012, at 1:58 PM, Norbert Hartl wrote: > > Am 22.02.2012 um 13:28 schrieb GermÃ¡n Arduino: > >> Example: xmlrpc died before to born, worked only in 1.1.1, now I must find time to update it to zinc and 1.3 but with the fear that again will not work in 1.4. > > What are your building blocks except http and xml? If you were working on 1.1.1 then xml parser moved quite a bit and zinc appeared on the scene. The changes to adopt xml parser should be minimal. Zinc provides a facade that mimicks backward compatibility. So you could have an easy start. But to be honest the situation is soooo much better with having zinc that you might save some time in development if you use zinc straight away. > And about 1.4: Yes, it moves a lot but zinc and xml do not. Xml is stable since months and the change rate in zinc is also dropping. So you might expect them to be available until...let's say...3 months from now. :) Ok, just kidding, I think the will stay similar for quite some time. Exactly. Doru got **all** the moose tools in 1.4 and some of them like glamour rely a lot on UI changes. I doubt that xmlrpc got any impacted on Morphic change. We do not change XML (but the XML maintainers did) and Zinc is just much much much better than the old system so it should be not difficult to adapt especially if you ask. Stef

6 21

[Pharo-project] loading a SLICE
by Nicolas Cellier Feb. 24, 2012

Feb. 24, 2012

In my (broken ?) image, loading a SLICE does not load the dependencies... Is it expected ? Merging does merge the dependencies though... Nicolas

2 1

[Pharo-project] Increasing bots traffic
by Nicolas Cellier Feb. 23, 2012

Feb. 23, 2012

Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process Notice I did not say developing the development process ;) Nicolas

3 6

[Pharo-project] Sticky TestRunner Progress Morph
by Nicolas Cellier Feb. 23, 2012

Feb. 23, 2012

Is it only my 1.4 image or are the TestRunner Progress Morph sticky ? (they don't delete when tests are finished and obfuscate the debug window)

2 2

[Pharo-project] shadows problem with 1.4
by Hilaire Fernandes Feb. 23, 2012

Feb. 23, 2012

A change somewhere broke the Morph shadow feature in 1.4. Gary et al. do you have any idea? See http://code.google.com/p/pharo/issues/detail?id=5314 Hilaire -- Dr. Geo -- http://www.drgeo.eu

3 3

[Pharo-project] [update 1.4] #14350
by StÃ©phane Ducasse Feb. 23, 2012

Feb. 23, 2012

14350 ----- - Issue 5365: Adding to the system useful extensions from Ecompletion http://code.google.com/p/pharo/issues/detail?id=5365 - Issue 5364: Added to Shout the Ecompletion extensions http://code.google.com/p/pharo/issues/detail?id=5364

1 0

[Pharo-project] Pharo 1.4 Tests-Mac - Build # 227 - Still Unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Feb. 23, 2012

Feb. 23, 2012

1 2

[Pharo-project] Pharo 1.4 Tests-Unix - Build # 238 - Still Unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr Feb. 23, 2012

Feb. 23, 2012

1 2

[Pharo-project] extracted the Cmd-q autocompletion to it's own class
by Guillermo Polito Feb. 23, 2012

Feb. 23, 2012

So it can play with the same mechanism as O/ECompletion does. Attached is a changeset with a little class. I'm not sure how to package it yet, but I think it has to be packaged along with SelectorChooserMorph and others. It's related to this issue: http://code.google.com/p/pharo/issues/detail?id=439&q=cmd%20q&colspec=ID%20… Guille

2 1