]> &api-questions;

XXX no answer for arch-overall

There are unit tests of API methods and assertions for proper use of the API.

1-1.5 man/month

The most common usecase of the API looks like this:

ProgressHandle handle = ProgressHandleFactory.creatHandle("My custom task");
...
// we have 100 workunits
// at this point the task appears in status bar.
handle.start(100);
...
handle.progress(10);
...
handle.progress(50);
...
// at this point the task is finished and removed from status bar
handle.finish();

It's good for tracking progress of long lasting tasks in the IDE.

yes

Not to my knowledge.

There are no settings currently. The API should be backward compatible.

1.4+

JRE should be enough.

Currently just openide, will also be dependent on module which will provide API for Status Line content. (not in current codebase yet)

No external dependencies.

Should run everywhere the same. There might be different LookAndFeel for each platform.

OpenIDE-Module-Module-Dependencies org.netbeans.progress/1 > 1.0

Just the module jar.

Yes.

Yes.

Anywhere.

No.

No.

No.

No.

No.

No.

No.

No.

The API can be called from any thread. However it is assumed that that the Progress indication starts, then progresses and then at last finishes.

Not applicable.

No DND.

Nothing.

No.

it will be registered as part of the StatusLine.

No.

No.

No.

No.

XXX no answer for perf-mem

No.

No.

XXX no answer for perf-scale

Events for the visual component will be collected and related events will be merged upon display.

No.

No.

No.

No.

No.

No.

No.

No.