Mariano,
That behavior was reported as a bug, see
http://code.google.com/p/pharo/issues/detail?id=5526
(see my comments)
Thanks
On Wed, May 23, 2012 at 7:48 AM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:
> Hi guys. Some time I ago, I submitted an issue that puts the progress bar
ter that.
Bill
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Stéphane Ducasse
[stephane.duca...@inria.fr]
Sent: Friday, May 25, 2012 9:12 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Progress bar in the to
I meant modal.
> Since when?
>
> Rule #1 of UI: never block UI.
> Because if you do, then we have no right to call it UI.
>
> do you know why we need this panic button (Alt-.) in our images?
> Exactly because every silly thing prefers to block UI at any point,
> even if it doesn't necessary.
st
On 24 May 2012 17:32, Stéphane Ducasse wrote:
> Indeed.
>
>> Is it possible to have an uniform way to present announcement. There
>> is already the growl-like announcements of tests used by the Nautilus
>> Browser done ob botton left. Maybe progress bar should be done in the
>> same screen area.
>
On 23 May 2012 14:33, Sean P. DeNigris wrote:
>
> Mariano Martinez Peck wrote
>>
>> I think it is much better since it does not disturb you.
>>
>
> Fine by me, but the progress bar usually blocks the UI anyway, only updating
> itself. Do we want it to drive the world instead? That way we can kee
Sean P. DeNigris wrote
>
> As I've been working on NewSystemProgressMorph
>
NewSystemProgressMorph feels ready...
The most significant change is that now, when you use methods like
String>>displayProgressFrom:to:during:, you have a real API for updating the
progress bar. Instead of sending sym
On 24/05/2012, at 18:06, "Sean P. DeNigris" wrote:
>
> Stéphane Ducasse wrote
>>
>> Now sometimes we should have a blocking UI.
>>
>
> As I've been working on NewSystemProgressMorph, I've been toying with
> whether the progress bar should be directly manipulated, as is the case now,
> or
Stéphane Ducasse wrote
>
> Now sometimes we should have a blocking UI.
>
As I've been working on NewSystemProgressMorph, I've been toying with
whether the progress bar should be directly manipulated, as is the case now,
or should just be another subscriber for progress announcements. This way i
Indeed.
> Is it possible to have an uniform way to present announcement. There
> is already the growl-like announcements of tests used by the Nautilus
> Browser done ob botton left. Maybe progress bar should be done in the
> same screen area.
Now sometimes we should have a blocking UI.
Stef
>
>
On Wed, May 23, 2012 at 7:37 PM, Guillermo Polito
wrote:
> And probably bottom right is less annoying, since people is used to start
> looking at the top right corner.
Is it possible to have an uniform way to present announcement. There
is already the growl-like announcements of tests used by the
And probably bottom right is less annoying, since people is used to start
looking at the top right corner.
On Wed, May 23, 2012 at 12:53 PM, Guillermo Polito <
guillermopol...@gmail.com> wrote:
> Maybe it can also be sticked to the background and not on top of my
> working window. That whay it w
Mariano Martinez Peck wrote
>
> I think it is much better since it does not disturb you.
>
Fine by me, but the progress bar usually blocks the UI anyway, only updating
itself. Do we want it to drive the world instead? That way we can keep
working on other things, but I'm guessing e.g. MC load
Maybe it can also be sticked to the background and not on top of my working
window. That whay it will disturb even less :D.
On Wed, May 23, 2012 at 12:48 PM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:
> Hi guys. Some time I ago, I submitted an issue that puts the progress bar
> not in
Hi guys. Some time I ago, I submitted an issue that puts the progress bar
not in the middle of the screen but on the top left. I think it is much
better since it does not disturb you.
Now it seems that, or my change got accidently lost or someoone else put
the previous behavior.
So...was that on
14 matches
Mail list logo