2016-03-25 22:27 GMT+01:00 stepharo <stepharo@free.fr>:

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 want a clean and stable core.

The way Rubric and GT-Tools were pushed into the core was a mess.

Rubric is a big bad bunch of badly documented code with lots of copy-paste garbage - we should do better.

And since it was included I hear it was abandoned by alain and TxText is the next.

I see up to no development for TxText.

The same for Athens, bugs or requests for conclusins I entered in FogBugz are, or will be closed (timout)

because no one cares.

Instead Athens is used as it is or change by others�� just for its own projects (roassal, Bloc, Brick).

��

I personnally want to have new widgets, a real UI builder and massively cleaning Spec.

me too, but what is the purpose of spec, if we replace all tools based on spec (debugger/inspector/...) with GT-Tools?

��

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

I fix bugs, there are many bugs.

��

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.

Our tools are in a much more worse state than in Pharo 4, not clean, not stable.

We are in code freeze since 6 weeks, and there are still many new changes instead of only bug fixes.

��

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