I really like this idea... in fact, you can sort of achieve the same things today by opening multiple instances of your project files. The only problem is that this takes up a huge amount of resources. This feature would be great as long as it doesn't require a new "instance" of IDEA running for each "workspace".
The question is, would the new workspace reside in a different frame, or be accessed via a tab on the side or bottom, or even from a drop down off the main toolbar? Another question: Would the workspace utilize the same source path, or would it have a separate source path? There are benefits to both. If you use a shared source path, files would be accessible from multiple workspaces without a duplication of config/resources. Using separate source paths would probably facilitate the "search in workspace" feature. Would it make sense to possibly have each workspace attached to different debugging sessions? This could be useful when working on apps that have to talk to each other. Would that even be possible? Just tryin' to help flesh out the details... sw > -----Original Message----- > From: Jon Steelman [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 09, 2002 5:23 PM > To: [EMAIL PROTECTED] > Subject: [Eap-features] Re: Usefulness of locking editor tabs? > > > Ok, I went ahead and placed a feature request in tracker named > Workspaces, and it's busy waiting for votes. > > http://www.intellij.net/tracker/idea/viewSCR?publicId=3682 > > Jon > > Chris Merrill wrote: > > Jon Steelman wrote: > > > >> I wanted something akin to multiple workspaces within a > project which > >> is not much more than a set of open files. In your case, > I'd open a > >> workspace for the special request, then flip back to my original > >> workspace after the request is over. > > > > > > I would love that!!! > > If I could create several of these, give them names and > > save them, I would use it _all the time_!!! > > > > I'm frequently working on two or three totally different > > parts of our software. For example, I'm adding some enhancements > > to our reporting GUIs when a high-priority customer issue > > arises regarding our data exporting code. I have to switch > > to a totally different and mostly unrelated set of classes. > > Then, when I'm done, try to remember which files I opened and > > close them all to get back to where I was before the interruption. > > > > As much as I love refactoring and quick-editing functions, this > > would save me more time (on a daily basis) then most of those > > other features. > > > > ********************************* > > Chris Merrill > > [EMAIL PROTECTED] > > ********************************* > > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://lists.jetbrains.com/mailman/listinfo/eap-features > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
