My usability problem was that I didn't understood that I need to
"accept" changes in text fields. Somehow I didn't make the connection
to method source panes (for which I think the feedback whether a
method was saved is important). Therefore, also reverting to the
default value did not work
Adrian Lienhard a écrit :
> Hi Alain,
>
> Nice to see you making progress!
>
thank you Adrian
> I've taken a quick look at the GUI and the code. Here some feedback:
>
> - When I change a value, why do I get a red border (for me this
> indicates that the change is invalid)?
>
no, there is no
- Original Message -
From: "Adrian Lienhard"
To: "Pharo Development"
Sent: Saturday, March 14, 2009 12:48 PM
Subject: Re: [Pharo-project] Setting package test
> Hi Alain,
>
> Nice to see you making progress!
>
> I've taken a quick look at
Hi Alain,
Nice to see you making progress!
I've taken a quick look at the GUI and the code. Here some feedback:
- When I change a value, why do I get a red border (for me this
indicates that the change is invalid)?
- Set to default doesn't do anything
- Dropdown lists are displayed at the wron
sound good.
I really like the idiom to have a class var on a package this is
really a nice way to let the dev
think that a preference is not a system global variable (aka old
preference) but a local to the package references.
This way we will be able to slowly arrive to have preference as a top
I know the Mac, Windows, and even OS/2 style prefers ellipses to
indicate that command button will not immediately perform an action
but will instead open a dialog box.
That is, prefer
Fonts...
to
Dialog for Fonts
On Fri, Mar 13, 2009 at 7:38 PM, Alain Plantec wrote:
> Hi all,
> Preference is
