I forgot to mention that i'm using windows
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I forgot to mention that i'm using windows
--
vim+zsh+tmux
I wrote a short blog post about my go dev environment http://bit.ly/1bsKWyw
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
I forgot to mention that i'm using windows
First of, instead of thinking try them and see what you like better.
-j
Descriptive names help bring code clarity. Yes, overly verbose long
names are not helpful but I'd much rather see checkingAccount than ca
or even account as a variable name.
Hi Joseph,
If auto-completion is your feature of choice, you should check out GoWorks. The code completion implementation in it is unique to that IDE, and was written from the ground up for speed and accuracy.
http://tunnelvisionlabs.com/products/demo/goworks
Thank you,
Sam Harwell
Disclaimer: I’m the author of GoWorks.
--

Hi Wes,
Thanks for the feedback and screenshot.
The goal with the current project detection was to eliminate the requirement that users take special steps to configure or create a special “project” for the IDE. If you could go into more detail about how you have your project structured, I could probably update the detection algorithm to work better with it.
1. Can you give a more detailed description of your working directories, as well as the relative paths from your working directory to any dependencies which are not part of the Go standard library?
2. What is the working directory where you compile your code? What commands do you execute to compile the code? Where is the output placed?
Thanks,
Sam
Hi Joseph,
While it’s not being actively developed right now, I have a great deal of interest in ensuring the current feature set remains usable for the majority of Go projects currently being developed. If some characteristic of it is not currently usable, I don’t mind putting in more time to make sure that gets addressed.
Without a corporate sponsor for the project, I don’t anticipate changing the licensing for the product (free, but closed source). I’m in the process of migrating all of my NetBeans extensions (including ANTLRWorks 2 and GoWorks) to distribution through the NetBeans Plugin Center for NetBeans 7.4 and higher. This simplifies the distribution and maintenance for me since the standalone build will no longer be dependent on a custom build of NetBeans (as it is currently). This transition should be complete prior to the NetBeans 8.0 release; until then the standalone release of GoWorks will continue to work.
I have made the following changes since Preview Release 7:
· I continued to improve performance and reduce memory usage of the background parser.
· Improved auto-indent support, especially in parenthesized blocks, e.g. import ( … )
· Added a Stop button to the Run window, and improved the progress bar display for build/run operations.
I spent some time working on a debugging implementation, but progress is extremely slow. I have very high standards regarding quality and performance before adding a feature to an IDE. For example, to meet these requirements in my Java debugger, I completely bypassed the JDWP used by virtually every other Java debugger and wrote my own communication layer directly on top of the JVM TI. The result vastly outperforms every other debugger I have ever used in Java (e.g. high-speed single-stepping through a program even with toString() evaluation enabled in the locals window). So far I have been unable to produce a similar experience for Go, but I remain hopeful that I’ll find a way to make it happen.
Thanks,
Sam
Hi Wes,
I did a bit of experimenting with this directory structure today, with the following results.
1.
GoWorks recognizes “/Users/wfreeman/gocode” as a project with a package structure like the following. I did not need to set the GOPATH environment
variable because GoWorks always configures that variable according to the location of the “project” you open.
2. GoWorks is not able to run the “go get” command. It needs to be able to do this, and it would be helpful if it brought up a balloon by the progress bar to inform you of that requirement if you open a project where dependencies are missing (such as your uci project, where uci_test.go relies on launchpad.net/gocheck).
3. If you right click on a specific package, you can click Compile Package to compile only that package.
a. I need to add an additional command Test Package to the same menu. Currently the Test command can only be executed against an entire project at once.
b. I need to add internal commands like Compile Current Package and Test Current Package that you can bind to a keystroke, allowing you to execute “go build” or “go test” while you are editing a file.
Would the changes mentioned above suffice for your needs? Is there any reason why you wouldn’t be able to open the gocode folder as a project? If the concern is simply the number of packages you now have, what about if you had commands “Treat as Library” and “Treat as Source Package”, where you could (for example) right click on “github.com.jordan-wright.email” and click “Treat as Library” to instruct GoWorks to show that package under the Libraries folder instead of the src folder. This feature could even be configured to automatically place any package obtained using “go get” as a library until the “Treat as Source Package” command was run on it.
The most troublesome item I’m facing is the implementation of ProjectFactory.isProject(directory). NetBeans expects this operation to return true if the directory is recognized as a project by your project system (in my case, a Go project). When you open a .go file and right click on the editor tab and select “Select in Projects”, it looks at each parent directory of the file until it finds one where isProject returns true.
Obviously it would be possible to instruct the IDE to treat each directory containing .go files as its own project. However, this would leave two extra challenges:
1. Currently GoWorks does not rely on the user to configure the GOPATH environment variable. To the contrary, GoWorks sets the value of this variable for the current process based on the location of your project. This decision is motivated by the fact that Windows-friendly applications should never require a user to understand or manipulate environment variables. If every folder containing .go files was treated as a project, import statements for packages that are not part of the standard library would not resolve.
2. Typically an “application” is a combination of the standard library of some set of additional packages. When the user opens a project, GoWorks should automatically locate the dependencies which are not part of the Go standard library.
I’m going to experiment with the following approach, and hopefully you can let me know how it works for you.
1. Implement isProject by saying a project is any folder containing .go files that also has an ancestor named “src”. This way, the GOPATH for the project can be automatically set to the folder containing the src folder, but you also have the ability to open a single package in isolation.
2. For any “import” statements in the project that do not resolve to a standard library module, show them as entries under the “Libraries” node for that project. If the package is not currently on disk under the expected src folder, show an exclamation mark on the icon for the node and provide a context menu entry to “Get Package” (which runs go get). The Libraries node itself could also include a new menu item “Get Missing Packages” to perform the go get operation on all missing packages.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
W dniu poniedziałek, 24 lutego 2014 08:59:10 UTC+1 użytkownik farah napisał:I'm new with go, and i'm looking for the best IDE, i'm thinking about intellij or LiteIDE,what's the best between them or do you have any other suggestion?thank you!