----- Original Message ----- From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project@lists.gforge.inria.fr> Sent: Friday, September 05, 2008 8:25 AM Subject: [Pharo-project] About UI enhancements
Questions ========
- Why the UITheme is responsible to open widgets. Why this is not the UIManager subclass because now a lot of the interface has to be duplicated in UITheme.
Answer because the theme is a variation which requires more subtle controls. Now I have the impression that it means that the UIManager is not well done then.
- Why in the following method basicNew is used and not new (which would call initialize anyway)?
Looks like a leftover required before the refactoring of the initialisation of FileDialogWindow... I'll check and change to just use new in these cases.
chooseDirectoryIn: aThemedMorph title: title path: path "Answer the result of a file dialog with the given title, choosing directories only."
|fd| fd := FileDialogWindow basicNew initialize; title: title; answerDirectory. path ifNotNil: [fd selectPathName: path]. ^(aThemedMorph openModal: fd) answer
To support better integration: ======================= We could merge UIManager subclasses MorphicUIManager and PSUIManager
PSPluggableListSpec should be merged into PluggableListSpec
I tried to understand the difference between standardWindow and pluggableWindow to see if it would make sense to merge them.
The "pluggable" subclasses support ToolBuilder as aside from the original classes. I guess all the pluggable variants could be merged into their superclasses and ToolBuilder pointed to the original classes.
I started to check all the extensions and yes there are some work but ideally removing the override would be good.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project