Remote performance needs to have "I'm working" feedback such as cursor change

[LisaAlmarode]

I'm logged in to the server on linux from pharo windows. Some server operations take some time - this is not unacceptable. But Jadeite needs to let me know it's working since leaving it as the idle cursor for more than a couple of seconds makes you think it's ignoring you.

-- creating a new class, after the accept it shows the ordinary cursor and it takes maybe 10 seconds? more? for the class to show up in the list. If you think you must not have hit the right key and accept again, it will results in errors that the class already exists.

-- if you do something like find literal references or fine senders, you at least expect it might take a while. But it should display an hourglass or something so you know it got the command.

[ericwinger]

The classic way to show "I'm working" is to wrap code in a Cursor wait block which displays a wait cursor for the duration of the block. However, this turns out to be a particularly thorny problem in JfP because of Jadeite's use of RSR. RSR does all its work in forked threads. If you wrap a block of code in a Cursor wait block, the wait cursor won't show long if the block forks a process.

However, we might be able to create a custom "I'm working" window which appears when an operation is started. Then, we could signal a "operation completed" notification which the "I'm working" window would handle and know to close itself.

[LisaAlmarode]

Trying to test double click in hierarchy, onetime I got results but most of the time I'm staring at it wondering how long to wait before I give up. I think this might be needed for alpha, if it's too big a time sink.

[ericwinger]

Assigning @LisaAlmarode for testing and thoughts on the in progress display.

Progress indicator:

• is very visible per request
• is not be too intrusive
• is not be in a separate window that's easily lost
• is only on workspace, console, and browser. Don't know if it's really needed on all tools.
• shows on all windows at once (as showing progress on individual windows that issued the command was too hard for alpha and rsr's unique way of doing things)