Yes, I want all of the good stuff. Let's always remember that when the platoon soldiers stop complaining, it is time to watch your back for a knife. Looks like we are a long way from there. Phil This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaig...> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, Mar 25, 2016 at 10:27 PM, stepharo <stepharo@free.fr> wrote:
So guys, you do not want Xtreams (and prefer to use Streams that have been "designed" decades ago) ;D ? no bootstrapped core (clement you do not want to have a mini image :) ? and a new UI frameworks?
I personnally want to have new widgets, a real UI builder and massively cleaning Spec. Now I would like to have multiple tool sets - I understand that people like the new debugger (I do not like it) - I want the possibility to have a mini tools tool set.
If you want to clean Pharo you can start cleaning Komitter stupid use of state pattern generating a lot of garbage instead of having a single animated morph.
We should clean Versionner- I have the impression that half of the classes are not mandatory.
Stef
2016-03-25 18:18 GMT+01:00 Hilaire <hilaire@drgeo.eu>:
Not exactly related to Announcement, but I remember when I first port DrGeo to Squeak (at that time Pharo did not exist) I used a lot of change/update when objects in the canvas changed. It was terribly slow, and later opted for a top-down update in the list of object.
So some sometime what look like a cool stuff (decoupled objects) is just a drag.
Regarding optimizing, I share my opinion here months ago, I think Pharo need consolidation releases: no new features, only bugs fix and speed improvement. There are enough new features in Pharo for a couple of years, but the product need to *be* solid and *feel* solid.
+1
Hilaire
Le 25/03/2016 12:33, Stephan Eggermont a écrit :
On 25-03-16 11:49, Nicolai Hess wrote:
Morphic drasticallly slower ? I would expect morphic code is mostly the same in pharo and squeak. If pharo is slower, this is a good starting point for optimising. Can you gives some hints? I do not have the impression that morphic is so much slower. We had/have a problem of too many announcements being send and too many redraws happening.
Stephan
-- Dr. Geo http://drgeo.eu