Vitalts / golangide

Automatically exported from code.google.com/p/golangide
0 stars 0 forks source link

Feature Request: Custom Workspaces #81

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
First off, many thanks for an awesome IDE which is a perfect fit for Go.

One major PITA for all Go developers (regardless of IDE) is the need for custom 
"workspaces". Go gives us GOROOT/GOPATH/etc and leaves the rest to the 
developer and/or IDE. Indeed LiteIDE supports a custom GOPATH which I find very 
useful. But even that is not always enough. The general solution is to use 
custom scripts and/or symlinks which is self-defeating and often difficult to 
implement and manage, especially in MS Windows.

So let me propose what I think would be an awesome feature for LiteIDE. It 
comes in two parts:

1. Instead of having a single set of global options (for App, Env, Editor, 
Build, etc), allow these options to be saved in pre-defined "workspaces". Users 
who do not need this feature would use the "default" workspace.  

2. Opening a folder in the LiteIDE file menu should automatically load the 
"workspace" associated with that folder. This could be achieved using a 
liteide.cfg file in the folder's root directory which simply identifies the 
folder's workspace. If the config file is not present then the default 
workspace would be used. Note that a "folder" could contain a single project or 
multiple projects organised in a classic Go src/pkg/bin tree.

It is worth noting that the latest version of the Google App Engine SDK now 
supports GOROOT/GOPATH/etc. See: 
http://blog.golang.org/2013/01/the-app-engine-sdk-and-workspaces-gopath.html

My suggested feature would be ideal for anyone who wants to develop both GAE 
apps and stand-alone apps using the same IDE.

Original issue reported on code.google.com by vinc...@callanan.ie on 18 Jan 2013 at 1:46