Hey all,
I've just started following go-uik and I am very impressed and happy about the idea's formed here.
When I watched the workflow pdf that John created I immediately had to think about a project that died out a few years ago (I think the creator sold it to Microsoft).
http://www.andrewbragdon.com/codebubbles_site.aspI think the bubble approach would be huge advantage when writing (go) code.
Ofcourse, there are some differences that should/could reflect in (an eventual) Go IDE approach.
For instance, I think it would be a good thing if every bubble had a expandable header (retracted by default) that has the package path and filename as title and contains the package statement and import() statement, which become visible/editable upon expansion.
That same idea of a expandable header can be used for the footer too, where errors concerning the showed piece of code (func def, type def, etc.) are showed.
etc. etc.
I think the IDE itself should manage the bubbles, virtual canvas etc., so that is not something that go-uik should implement. However, to achieve this, a certain flexibility is required by go-uik.
Creating a bubble-based editor will take a lot of development, so this is probably never going to be in a first release IDE.. However, it might be a good thing to keep the required flexibility in mind while developing go-uik.
Please share any thoughts on this IDE approach.
Sidenote: I'm planning to work create some go-uik widgets soon. As I'm fairly new to this project I'll probably start with reading the complete existing codebase.