-work argument seems to be being overridden/ignored

[Chownie]

As it's said above

[asa@kirito IntaLancer]$ golab -http -addr=:8910 -work="/home/asa/dev/Go/"
2013/06/17 02:31:11 found gocode at: /home/asa/go/bin/gocode
2013/06/17 02:31:11 starting http://:8910/
starting lab for: [/home/asa/go/src/pkg /home/asa/gopath/src]

The lab isn't started for the area I specify in -work and within the browser the areas it does look at aren't shown within the document browser window.

Here shown if I look in the documents tab it just shows the tray icon with the work documents

but then if I manually enter my home directory after #file in the url it shows me some more options but crucially still ignores the one I specified

[mb0]

the documents tab is showing the opened editor buffers (for this client). it shows the revision of the buffer as well as the state (saved or not). i want to show all opened documents there, but haven't added that yet.

sorry, for the confusion. I usually open the report view and click on one of the packages listed there to start navigating.

i think I should add a auto-complete-open-document box in this view, what do you think?

[Chownie]

My issue is that both the report and the document view don't actually show anything by default.

The report view does show items but only if I open them manually via #file in the URL bar. Until I do so every view is empty and there's no prompt or indication on how to actually interact with the UI

I think at the very least whilst either view is empty of content it should provide some kind of prompt on how to interact

[mb0]

golab uses goroot (from your go installation) and $GOPATH from your environment. in your case that is /home/asa/go and /home/asa/gopath. you can then specify on which packages you want to work with the work flag. these packages must be go packages in your gopath, they are recompiled and tested on changes and are shown in the reportview. you however specify /home/asa/dev/Go/ which is clearly not a path to a package in either your goroot or gopath. try this for example: golab -http -work=$GOPATH/src/github.com/mb0/lab/...

[Chownie]

Ah, so you can only work with installed packages, and not areas of sourcecode?

[mb0]

yes, because compiling and testing still uses the go tool and it needs to resolve package dependencies.

sorry, i didn't expect that "go package" needs further explanation. should i change or add some words in the readme?

[Chownie]

Some kind of indication of usage seems fair, I think

[mb0]

added information to the readme with reference to go help gopath