For the theme idea, I allways have in mind the structure used in
VisualWorks which is to have decorator wrappers (and a few specifics
like scrollbars) for each theme, and the core GUI stays the same.
Morphs aren't designed that way (except for scrollbars) so it looks
harder. But maybe
Le 26/09/2013 21:54, Sean P. DeNigris a écrit :
Goubier Thierry wrote
answer := UIManager default
chooseFileReference: 'Select a file'
path: aFileReference
pattern: '*.png'
name: nil
I can't tell if that captures the full options of fileDialogWindow without a
bit more
We have FileDialogWindow, which is a cool little class which implements all
the cool things you may want to do when selecting a file, for example:
- answer either a directory, file, file entry, etc.
- set an initial directory
- set the sorting block
Life is good.
rant
Then, we take the entire
On 2013-09-26, at 12:29, Sean P. DeNigris s...@clipperadams.com wrote:
We have FileDialogWindow, which is a cool little class which implements all
the cool things you may want to do when selecting a file, for example:
- answer either a directory, file, file entry, etc.
- set an initial
Camillo Bruni-3 wrote
Just image that the UIManager should also work on the CommandLine
After browsing UICommandLineManager#chooseFrom:lines:title:, I see where
we are headed - mimicking the headful interactions via stdin/out. Very cool!
Camillo Bruni-3 wrote
Returning any window on UIManager
-boun...@lists.pharo.org] de la part de Sean P.
DeNigris [s...@clipperadams.com]
Date d'envoi : jeudi 26 septembre 2013 20:24
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] UI Mess
Camillo Bruni-3 wrote
Just image that the UIManager should also work on the CommandLine
After browsing
Goubier Thierry wrote
answer := UIManager default
chooseFileReference: 'Select a file'
path: aFileReference
pattern: '*.png'
name: nil
I can't tell if that captures the full options of fileDialogWindow without a
bit more investigation, but that would be a great improvement
If you remember a while ago I was thinking that the theme could be managed like
settings (ie encapsulated in the widgets and that the widgets could encapsulate
their default for theme), but sadly I was wrong because a theme oftn requires
specific computation. So probably
we should have a
On 2013-09-26, at 15:50, GOUBIER Thierry thierry.goub...@cea.fr wrote:
Thanks, Sean, I'm happy that after Erwan suggestion of an issue, someone took
charge of cleaning that :)
My own position is that current Pharo has unified the filesystem issue with
FileReference, and that I'm not
