Issue 93992 - annoying quirks around deploying and running an extension in OOo
Summary: annoying quirks around deploying and running an extension in OOo
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOO300m5
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-09-17 16:13 UTC by steffen.grund
Modified: 2013-08-07 15:31 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description steffen.grund 2008-09-17 16:13:19 UTC
I created an AddOn extension using the Netbeans plugin and use the new feature
of giving the .oxt as parameter for the Office start.

On Solaris Intel then the extension manager opens, then the Office, then the
message box from the extension manager asking if the extension should be
registered. So the user has to first click away the message box and then bring
the extension manager to the front to close it. Here a different order would be
nice: first the extension manager with its message box, then the Office.

Afterwards a writer document is open - which has only by chance any relevance to
the AddOn that is registered. The backing window seems to be a better
alternative as first view.

Furthermore, the AddOn is not active in that frame. Even if it is intended to be
used in a writer context, a new document has to be opened first. This can only
be avoided when the office is started after the extension manager finished, as
far as I can see - no idea if that is even possible. But then again, I think the
backing window is less confusing.
Comment 1 steffen.grund 2008-09-17 16:18:57 UTC
CCed: jsc
Comment 2 dirk.voelzke 2008-09-18 10:20:43 UTC
Comment 3 dirk.voelzke 2009-01-06 08:44:57 UTC
The deployment of extensions with netbeans has changed so there is no urgent
need to change anything now. Therefor changed target to 3.x