You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of Che in Che development, GWT CodeServer can be started into a (dev-)machine at the address differs from the localhost. Thus each time one needs to use the new bookmarklets on a browsers toolbar for working with the CodeServer.
It is very inconvenient.
We can add an action to IDE for triggering GWT recompilation on the CodeServer since IDE always knows the address of the launched CodeServer.
Such action allows avoiding drag&drop a new bookmarklet each time when a new instance of GWT CodeServer is launched.
The text was updated successfully, but these errors were encountered:
azatsarynnyy
added
status/code-review
This issue has a pull request posted for it and is awaiting code review completion by the community.
and removed
status/in-progress
This issue has been taken by an engineer and is under active development.
labels
Nov 22, 2017
In case of Che in Che development, GWT CodeServer can be started into a (dev-)machine at the address differs from the localhost. Thus each time one needs to use the new bookmarklets on a browsers toolbar for working with the CodeServer.
It is very inconvenient.
![image](https://user-images.githubusercontent.com/1636395/32232357-8938ecb2-be60-11e7-805e-8a854cad3a58.png)
We can add an action to IDE for triggering GWT recompilation on the CodeServer since IDE always knows the address of the launched CodeServer.
Such action allows avoiding drag&drop a new bookmarklet each time when a new instance of GWT CodeServer is launched.
The text was updated successfully, but these errors were encountered: