GoogleCloudPlatform / GoogleCloudPlatform/google-cloud-eclipse

Opening internal Eclipse browser Feels archaic and doesn't buy developer much

Open
#940 7 comments 0 reactions 0 assignees View on GitHub
enhancement p4 priority: p4
Dominant language
Java
Stars
90
Forks
52
PR merge metrics
No merged PRs in 30d

Description

I think clicking on the console urls and opening an internal Eclipse browser doesn't by the target audience developer much at all. That said, opening the internal browser by default after server starts as well has the same effect. I think it feels like a digression in development because it doesn't have access to development tools and adds an unneeded step to getting debugging going.

That said I do have a bias with the GWT Eclipse Plugin so I could have a prejudice here. Feel free to close this, I won't mind, I'm expression an opinion on workflow from my angle.

The target audience, web developers, I think will be expecting to be debugging in their favorite browser, the default browser. And opening in Eclipse sort of feels like an insult having no dev tools for development. I think the only effective links to the internal web browser would be the local app engine dashboard.

Example of the console click opens the internal Eclipse browser that shows web page.
![screen shot 2016-11-03 at 8 22 11 am](https://cloud.githubusercontent.com/assets/1326504/19972398/25b445e4-a19f-11e6-9d0a-9b00d37a4726.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.