Community
Participate
Working Groups
The bug 4922 is about Eclipse <-> OS integration. In the curernt state that bug adds ability for the launcher/SWT/UI chain to open from a command line. For instance, for Windows, that looks like: <path>\eclipsec.exe -name Eclipse --launcher.openFile <qualified file name> What's missing is the ability for a plugin author to register file extensions that they can handle.
Isn't this usually handled by installers rather than the application itself?
"installers" here could be p2? This does require native code
It's different for every platform. On windows it's a registry key (see 'ftype /?'). On mac you use the plist file. I think every window manager is different on linux, but I could be wrong. There's some info on creating file associations for Ubuntu here: http://ubuntuforums.org/archive/index.php/t-51012.html. Looks Gnome specific though.
(In reply to comment #1) > Isn't this usually handled by installers rather than the application itself? Installers are applications too :-). I am speaking about adding Eclipse API to register file types, presumably backed up by platform-specific fragments. The APIs are to be used both by Eclipse-based "installers" and Eclipse-based "applications".
(In reply to comment #3) > It's different for every platform. Can we start by supporting 2 - 3 major cases (Windows and Mac?)and be open to community contributing fragments for other OSes?
(In reply to comment #5) > (In reply to comment #3) > > It's different for every platform. > > Can we start by supporting 2 - 3 major cases (Windows and Mac?)and be open to > community contributing fragments for other OSes? I'm not convinced we can fit this into 3.6, unless you think there is something really simple we can do. But I think there are lots of things we need to consider. * What happens if a file extension is already handled by another application on the system, would we override, ask the user what to do etc. * What happens if multiple Eclipse installations have the same bundle which is trying to register for the file extension. Which one wins. Do we keep asking the user questions like the browsers do (hey firefox/IE/etc. is not the default browser, you want it to be?). I think there are lots of these kinds of issues that we need time to think through.
This is closely related to the SWT Program class, which allows you to query what programs are registered for a given file extension.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
