Ok, I'm interested since I'm working in an experimental extension. In 3.0, JobStartNotification is the only used exception. The other one, JobProgress, is only referenced from tests. I put a halt in #handleJobProgress: to check and it didn't stop. I would like to discuss about paralel jobs too. Martín On Mon, Jul 15, 2013 at 9:35 PM, Camillo Bruni <camillobruni@gmail.com> wrote:

Hi, this actually emerged from a discussion with Sean, because he didn't like exceptions based notifications :). But all in all there is no big change needed.

I think the UI will work anyway passively, there should be a refresh loop that checks 15-times per second the status of the active jobs and updates the UI progress bar accordingly.

So I think there shouldn't be many more changes? Maybe we can quickly have a look at it together...

On 2013-07-15, at 19:00, Martin Dias <tinchodias@gmail.com> wrote:

...

Hi,

I am looking into SystemProgressMorph and I found this flag in several methods:

self flag: 'When we go from Exceptions to announcements, delete this and use show:from:to:during:'.

I'd like to know more. I see that Jobs are implemented with both exceptions and announcements... what is the idea? to remove the exceptions and use only announcements?

Thank you for your help, Martín