Hi All I just opened this issue.
http://code.google.com/p/google-web-toolkit/issues/detail?id=4139 I just want to hear if anyone has input or any other ideas to this subject. Here is the summery from the issue: Detailed description (please be as specific as possible): Now that development mode (earlier hosted mode) does not embed a browser and basically acts as a proxy http server between the browser and the jetty server or a real system in -noserver option. It would be nice if it was possible to add an option to the development mode to disable showing any GUI at all and a option to log any messages to standard out. This would enable various development scenarios of more advanced character: 1: Legacy systems: If your whole development environment are on a headless non-local unix machine that you have remote access to, but it is not possible to transfer the code to your local machine (perhaps because of company policies) 2: IDE integration: Some users are so used to look at the output window in their IDE that they prefer the logging output to show up there, even if this is limiting the interactive use (reload server etc), this would also enable the IDE to put links from stack traces etc. Scenario 2 could be solved by enabling standard out logging as well as the logging in the development mode window, but scenario 1 requires the option to remove the swing GUI completely. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
