Issue 38333 - Provide UI feedback when starting java wizards
Summary: Provide UI feedback when starting java wizards
Status: ACCEPTED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-02 16:09 UTC by berend.cornelius
Modified: 2017-05-20 11:31 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description berend.cornelius 2004-12-02 16:09:29 UTC 
The first startup of the java wizards from the wizards menu (menu sequence
file/wizards) is very slow. As described in bug #111425#  (Sun internal bug)
this process can't be speeded up. As discussed with CJ from User Experience we
should at least provide some user interface feedback. Therefor we must
deactivate the mousepointer and change its symbol to a sandbox. As soon as the
"trigger" method of the respective wizard is "entered" the mouse pointer is to
be resetted again.
BC->MBA: I hope it's OK to send the task to you first so you can find an
appropriate owner for it.
Comment 1 Mathias_Bauer 2004-12-02 16:55:19 UTC 
Not really. :-)

What needs to be done depends on the Wizard. Some of them are called by "slots",
or "dispatches" some not (IIRC they use command like "service:..." or "job:...").

For the Wizards called by "slots" or "dispatches" the code for the mouse pointer
must be added in the applications that are starting the wizard.
I assume you know much better then I which application belongs to which wizard,
so please fetch the technical leads of those applications and discuss how to
proceed.

Wizards that are called directly from a "service" URL or something similar have
just a bad luck: there is no way how we could show some feedback, because this
is just a low level service, no UI code.
Comment 2 berend.cornelius 2004-12-02 17:11:10 UTC 
BC->OS: can you discuss with mba if we you can provice UI feedback?
Comment 3 berend.cornelius 2004-12-03 09:43:17 UTC 
.
Comment 4 berend.cornelius 2004-12-03 09:45:24 UTC 
BC: I erroneously set the bug to Resolved/Fixed.
Comment 5 berend.cornelius 2004-12-03 09:45:51 UTC 
.
Comment 6 Oliver Specht 2004-12-03 10:09:53 UTC 
->bc/tv: The only solution I can see is that there has to be an instance inside
the office (maybe in sfx2) that dispatches the calls to the wizards. 
In such an instance it would be possible to show an hourglass. 
But that's nothing that has to be done by the applications.
Comment 7 tom 2005-01-11 14:42:03 UTC 
TV: Set to Target OO.o 2.01
Comment 8 christof.pintaske 2005-05-27 14:12:05 UTC 
this requires too much work without real win in functionality. We will tackle
this one in the next release
Comment 9 christof.pintaske 2005-05-27 14:12:43 UTC 
changed target
Comment 10 tom 2006-05-22 10:41:54 UTC 
TV: It would be good to have a waiting cursor for the time the JRE is being
started. Additionally I could implement a waiting cursor for the time the wizard
initializes (during Java runtime).
Comment 11 jsc 2006-08-02 12:01:00 UTC 
adapt target -> vacation

Please verify this issue and set a new appropriate target
Comment 12 tom 2006-10-23 10:46:43 UTC 
TV->JSC: Would be good if this could be fixed for OO.o 3.0
Comment 13 kai.sommerfeld 2006-10-24 08:05:12 UTC 
=> Feature, => 2.x
Comment 14 jsc 2006-10-24 08:56:14 UTC 
jsc -> kso: if you think this is a feature than you have probaly an idea how and
who should fix this.
Comment 15 kai.sommerfeld 2006-10-24 10:04:48 UTC 
Okay, I will find a proper owner for this feature.
Comment 16 kai.sommerfeld 2007-11-22 15:44:23 UTC 
No time to fix this in 2.x time frame. => 3.0
Comment 17 kai.sommerfeld 2007-12-10 13:30:16 UTC 
.
Comment 18 Marcus 2017-05-20 11:31:41 UTC 
Reset assigne to the default "issues@openoffice.apache.org".