Community
Participate
Working Groups
It would be great if one could drag .java files and other to the Eclipse icon in the Dock (any of those would do:). Also it would be nice if one could set the "Default" app for .java files to Eclipse. Both of these issues are probably related to #53260
We have similar issues on Windows. You can't set Eclipse as the default app to open certain files by the OS.
Two things are required for the Mac: - we have to add a CFBundleDocumentTypes section to Info.plist - SWT needs to accept the corresponding Apple events (open) and make them available thru API
Out of curiosity, can the list provided by CFBundleDocumentTypes in the plist be contributed dynamically by the app once it's running?
IIRC, only if we rewrite the Info.plist and tell the Finder to re-read the application bundle and update its database. Will verify...
I'm just wondering if we can make this functionality contributed via an extension instead of hardcoding it...
(Incidentally, I have an ulterior motive - I was hoping to do something similar with dictionary support so that people could plug in Applescript handlers)
Kim, if there's going to be movement on this one you'll likely have to drive it. I'd be glad to discuss approaches and/or look at a patch but I'm simply not familiar enough with the Mac's dock area semantics to be much use...
Eric, I'll take this one for my bucket. This doesn't really have anything to do with trim or dragging in the eclipse sense.
Is this issue still being looked at? I was going to start looking into adding this ability, so if any knowledge about where to add the hook to listen for the appropriate carbon event is I would appreciate it.
http://wiki.eclipse.org/Platform_UI/How_to_Contribute Eclipse (SWT) has moved to Cocoa. Not sure if the necessary hooks are different in Carbon vs. Cocoa.
Prakash is now responsible for watching bug in the [Mac] component area.
*** Bug 141101 has been marked as a duplicate of this bug. ***
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.