[Pharo-project] A new GUI visual designer

Stéphane Ducasse stephane.ducasse at inria.fr
Sat Feb 12 09:54:49 CET 2011


if you want to think that I'm an asshole and I do not want to have a better UI, you are free to think that.
Now this is not the case. So if you can read my mail with the eyes of somebody that fight daily to make the system
nicer, better, smaller....

>>>> So there is an engineering effort needed.
> oO did other pharo-development _not_ involve engineering?

Yes so who is standing up and saying ok I will allocate one month to make sure that this is well integrated?

>> How do they compare with announcements and event and #changed
> Had you read the Wiki, you would know.
> “convenient, lightweight and thread-safe callbacks”
> https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/signals
> https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/signals#FeatureComparison

Yes. Now the question is do we want that in addition to 
	- event,
	- announcement
	- changed

We are working ***HARD*** to remove event and system changenotifier.
Design is not layering, it is about bringing the right infrastructure in place.
So if signals are important/good then they should be not in competition to other but either integrated into 
or we should migrate the code to the other abstractions.

>> In the case of the UIBuilder of void,
> Void?
The nikname of the personn
>> there are new widgets that extend existing ones but 
>> It would be better to not subclass and get better widgets.
> Interesting, Because it is what polymorph has done for years.

Yes and this is why we do not want that.
Even for polymorph the goal is to merge everything and get one set of excellent widgets based on an excellent core.

>> May be fixing copy/postcopy,
> what?

in pharo we use postcopy

>> use of _,
> what?

we should not have _ 
rob vens told me that there are _ in the BUilder code

>> ...... references to Preferences,....
> Then, what about a -PharoCompat package?

I did not see it.

>> This kind of work.
> Pleas let me quote your initial mail:	
>>>> We cannot stack libraries.
> I'd like to understand that, please.

As I said, we do not want to have four ways to emit announcements, we need one cool widgets set (merging the best of what exist), in the past we had 4 different ButtonMorph. I want one excellent one. So to get there it will take engineering time.
Just to evaluate solution. 


More information about the Pharo-project mailing list