On 27-Jun-2013, at 11:43 AM, Mickael Istria <[email protected]> wrote: > On 06/27/2013 05:37 PM, Brian de Alwis wrote: >> So you could open the file outside of a project (File > Open File…). > It could work, but it's not the most natural IMO. > The use-case I have in mind is a big Maven repos with some Java projects, and > I sometimes just want to tweak a pom or a message file in a project I already > have (closed) in my workspace.
You could add a menu item targeted to closed projects to select a file for Open With. >> A slightly different approach would be to make the project natures >> toggleable. So you mark this project as no longer being a Java project. >> These overrides should be stored as a workspace preference rather than a >> project preference. > That's interesting. But if we have this, doesn't it make the concept of > closed projects useless from a end-user perspective? Temporarily removing a nature just changes the abilities provided on that project (e.g., removing PDE nature turns the project into a normal Java project), whereas closing a project removes it from consideration. You can delete a project without removing the content to remove it from your project list. Does that mean closed-projects are useless? Brian. _______________________________________________ platform-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/platform-dev
