Opened 13 years ago

Closed 9 years ago

#7629 closed enhancement (wontfix)

Provide more comprehensive Progress Indicator

Reported by: David Schwartz Owned by:
Priority: high Milestone: future
Component: DojoX Widgets Version: 1.2beta
Keywords: ibm progress-indicator Cc:
Blocked By: Blocking:


  • Pause button label cycles b/w 'Pause' and 'Resume'
  • Layout is updated to respond to the presence/absence of particular elements (not all processes can be reversed or would have task-relevant info, for example)

Attachments (1)

progress-indicator.jpg (25.6 KB) - added by David Schwartz 13 years ago.

Download all attachments as: .zip

Change History (9)

Changed 13 years ago by David Schwartz

Attachment: progress-indicator.jpg added

comment:1 Changed 13 years ago by Adam Peller

I'm not sure what is being requested here... a dialog-based compound widget with a progressbar? This seems to conflict with Dijit design goals as the basis for a widget. As long as it is straightforward to construct this with the current APIs, either by wiring widgets together or adding HTML, I think this is a wontfix.

comment:2 Changed 13 years ago by David Schwartz

It was suggested that I create this ticket for Dojox, not Dijit, so that, if someone wanted to, they could create this useful, compound widget.

comment:3 Changed 13 years ago by Adam Peller

We usually don't hold tickets like this open unless it is either part of our development plan or there is a patch in place, otherwise it would be difficult to manage all the tickets. In this example, though, I'd like to think that it's trivial enough (and specialized enough) that it doesn't warrant its own module. It could be published as an example somewhere.

It's also possible that something like this exists in psych desktop.

comment:4 Changed 13 years ago by Adam Peller

Milestone: tbdfuture

Marking future, but we can pull this in if someone has the cycles to work on it. I still worry that this task is too application- and server-specific, and might make a better demo or example page than a reusable widget.

comment:5 Changed 13 years ago by David Schwartz

Not sure I understand 'too application- and server-specific' or what it 'might make a better demo or example page than a reusable widget'. Can you elaborate?

comment:6 Changed 13 years ago by Adam Peller

it's difficult to write a progress widget without defining some sort of transport, endpoint, schema, etc. to talk to in order to get the progress status. Without that, we have very simple client code to render a progress bar based on a simple API called update() which basically takes a new percentage. How to wire wire the widget up to a backend is left to the user (perhaps a 'working' client/server example might make an excellent demo in our widget gallery, however) Dojo generally tries to be server agnostic.

comment:7 Changed 11 years ago by Adam Peller

Owner: Adam Peller deleted

comment:8 Changed 9 years ago by bill

Component: DojoxDojoX Widgets
Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.