Issue 74596 - OOo should associate itself with extension-provided file types
Summary: OOo should associate itself with extension-provided file types
Status: ACCEPTED
Alias: None
Product: utilities
Classification: Unclassified
Component: code (show other issues)
Version: OOo 2.0.4
Hardware: All Windows, all
: P3 Trivial (vote)
Target Milestone: OOo 3.x
Assignee: AOO issues mailing list
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-16 10:58 UTC by tml
Modified: 2013-02-07 21:42 UTC (History)
2 users (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 tml 2007-02-16 10:58:56 UTC 
After installing/deinstalling (or enabling/disabling) in Tools:Package Manager
an extension (.oxt file) that handles some otherwise unknown to OOo file type,
OOo should associate/disassociate itself in Windows as the handler for that file
extension. If possible, this should be done in other desktop environments, too,
of course.
Comment 1 shaunmcdonald131 2007-02-17 08:56:42 UTC 
Will need to look into this for the Mac, could be tough to do dynamic file
format entries.
Comment 2 Martin Hollmichel 2007-06-15 11:28:16 UTC 
reassign
Comment 3 joachim.lingner 2007-06-25 11:02:02 UTC 
For the Extension Manager a filter is just another extension. It does not know
the difference. So this should be implemented by someone who listens to changes
of the "filter configuration".
Comment 4 andreas.schluens 2007-06-25 13:09:22 UTC 
AS->JL: As discussed with KSO and you ... if we implement those feature it must
be a feature of the package manager itself.
Comment 5 joachim.lingner 2007-06-25 13:39:37 UTC 
.
Comment 6 joachim.lingner 2007-06-25 13:40:14 UTC 
.
Comment 7 Mathias_Bauer 2007-12-04 14:47:44 UTC 
according to release status meeting -> target 3.x