Issue 91752 - Add the Export option to the Extension Manager
Summary: Add the Export option to the Extension Manager
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: OOo 3.0 Beta 2
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-07-17 09:53 UTC by dmpop
Modified: 2014-02-14 11:13 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description dmpop 2008-07-17 09:53:26 UTC
Prior to version 3.0, the Extension manager had the Export option that allowed
user to export any installed extension as an .oxt package. This feature was
removed in 3.0. I develop an extension called
Writer's Tool, and the Export feature has always been extremely useful for me.
Using it, I could modify the macros in the extension, and then quickly export it
as an .oxt package. Without the Export feature, modifying the existing extension
and then saving it as an .oxt package becomes a major inconvenience. Unless
there is another way to export an installed extension, I vote for bringing the
Export feature back to the Extension Manager.
Comment 1 ab 2008-08-01 13:50:28 UTC
This has nothing to do with scripting, but with extensions in general

ab->jl: Please have a look
Comment 2 joachim.lingner 2008-08-01 14:09:25 UTC
@bh: Maybe the macro development work flow would be a reason for an export.
Comment 3 bettina.haberer 2010-05-21 14:44:11 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements". 
Comment 4 Edwin Sharp 2014-02-14 11:13:49 UTC
Confirmed with
AOO410m1(Build:9750)  -  Rev. 1565724
Win 7