| Summary: | [plan item] Complete Mac OS X port | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jim des Rivieres <jeem> |
| Component: | SWT | Assignee: | Silenio Quarti <Silenio_Quarti> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | 2sirius, alex.blewitt, andre_weinand, bob, boris, eclipse, gmendel, gr.eclipse, jed, kykimnyc, m.a.r.k, mwille, olale, public, Richard_Wilson, simon, ssahuc, stephan, thatnitind |
| Version: | 2.1 | Keywords: | plan |
| Target Milestone: | 3.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 26756, 56476, 57350 | ||
| Bug Blocks: | |||
|
Description
Jim des Rivieres
See also: bug 33637 (Printing) bug 30104 (Drag and Drop) bug 32438 (IME) bug 36999 (Accessibility) bug 36732 (Performance) I would like to chime in the following which makes Eclipse non-OSX-like: bug 42554 (glitch in duplicate dock icon) which is definitely non-Mac behaviour, and bug 26756 metadata shouldn't be relative to application install, it should be relative to user library. S Whether these should be directly owned by the SWT or not, I don't know, but they are definitely issues that affect the 'feel' of Eclipse on the OS X platform. Re #42554: The problem is that the Mac launching-API is severely limited and does not really support what we need for Eclipse. And since we try to be single source we don't want a Mac-specific Eclipse launcher. But you are invited to help us finding a solution that works both for Jaguar and Panther. The code lives in project platform-launcher :-) Re #26756: Storing metadata outside of workspace makes only sense for data that is independent from the workspace (e.g. CVS repository locations, keychain). But most of the stuff in .metadata is project (that is workspace) related and better should be kept in the corresponding workspace. However, on Mac OS X we could easiliy create the default workspace in the user's Document folder. Should we do this? (To try, change your Info.plist file and specify "~/Documents/workspace" instead of "workspace") In addition in recent build I've already moved the keychain file from .config to ~/.eclipse_keyring. However, it is debatable whether we always want to share the keyring across multiple workspaces. If you take another location for the user's workspace, use ~/Projects/Workspace instead of ~/Documents/workspace please. The Projects folder is also created by default for a new MacOS X user and is more inline with development 'projects'. Re #4, this issue should probably be discussed on bug 26756 since that's the main issue there. I'll add a link on that part. Please note however that any references to application data should be in a platform-specific location. Specifically, Projects isn't a directory recommended by Mac OS X, and nor is it created on the out-of- the-box install. It may be something that's configured for a specific system, but having re-installed OS X.3 on my box last night, it certainly doesn't create it there :-) Please try to incorporate the selection behavior of OSX double click and drag = word select, triple click and drag = line select This was a deferred item in 3.0. However, significant work was done in this area. Please enter individual bug reports for any outstanding issues. |