For mac instal Alternate Directory1/26/2024 ![]() I'd just like to make it clear that my blog post wasn't in any way a dig at this bug. Opportunity to only copy one folder over instead of many. At least, that way it will give the user the Whatever to closer match products like Photoshop. Perhaps if the idea of leaving the plugins and features where they are will remain, it would be better toīuild the 'eclipse' download with a single 'Eclipse' folder, and have a suitable. ![]() Often involve trashing the entire folder and starting again. But note that upgrading such a product there does Your point re: Photoshop et al is well made, though. So I agree that at the time, the original decision to have them outside was correct, but now I think thereĪre better solutions available, especially with the update manager working. The standard version of all the plugins without having to worry about dependencies (or even run with You'd still have to open the plugins and featuresĭirectories individually, but you'd get the advantage that whenever you upgraded Eclipse, you'd also get Symlinks to the plugins and features directory outside. This also doesn't rule out having the plugins and features installed in the. Plugins and new-folders directiory separately. You'd have to open the 'plugins' and 'features' directory individually, then copy the contens of the new. New plugins, and your system would be equally as broken. So you'd end up with a 'features' and 'plugins' directory that *only* contained the For example, open a (say) zip file containing the plugins, andĭrag-and-drop the folders across - Mac's original implementation is to replace the entire folder, ) copying into the sameĭirectory may be equally as dangerous. ![]() Why should it not be possible to use the Update Manager to do the work for them, rather than having toįrom a 'dumb' user's point of view (would dumb users use Eclipse, though. users installed new plugins quite frequently and moving them into the hidden app bundle wasn't Of course, there is nothing to stop them being symlinked to within the. Part a) seems a logical choice, but then stops the user directly being able to see the plugins/featuresĭirectories. The Eclipse build environment automatically. The only way ofĪutomating this would be to have a Mac specific installer (.dmg) which may not be possible to create on The difficulty with part b) is that it would still involve a separate directory structure. ![]() In order to resemble a Mac app, the plug-in/feature/config folders should either be:Ī) Packaged within Eclipse.app, under Contents/Resources (see ĭocumentation/MacOSX/Conceptual/SystemOverview/AppPackaging/chapter_45_section_3.html forī) Installed into /Library/Eclipse/ or /Library/Application Support/Eclipse Separate folder for plugins, a separate folder for features, and a few other files/directories. app bundle, as opposed to outside the file itself.Īpart from anything else, this makes drag-n-drop install of the application much easier.Įclipse goes against that philosophy the download includes a folder that contains the Eclipse.app, a Most apps have resources that are built-in to the. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |