Reviewers: mmendez,

Description:
This patch depends on rietveld issue #80805.

Modified remotemessage.proto:
-Defined the SERVER log type; got rid of the BROWSER log type (BROWSER
was the same as module)
-Moved the ViewerRequest and DevModeRequest enums to be top-level, so
that they could be used in capability exchange responses

Fixed up the DevModeServiceServer capability exchange logic. Instead of
dumbly iterating over all possible request types that it knows about, it
queries the RemoteUI to see which capabilities are supported by the
DevModeServer. This type of interaction makes the name "RemoteUI" seem a
bit odd. It's more of a ocnduit between the DevMode Server and the UI,
as opposed to one-way interaction.

Implemented the RemoteUI class, which led to the addition of the
ViewerServiceTreeLogger and the ViewerServiceClient.
ViewerServiceTreeLogger is an implementation of a TreeLogger that adds
log entries by interacting with a ViewerService. The ViewerServiceClient
class is used by the ViewerServiceTreeLogger and the RemoteUI for
interacting with a ViewerServiceServer.

NOTE: There may be some minor tweaks to this patch (and previous
patches). I'm going to run some tests against the modified plugin side;
if I discover any bugs, I'll fix them up. I'll send an updated patch
which is dependent upon all of the previous patches that I've sent.



Please review this at http://gwt-code-reviews.appspot.com/80806

Affected files:
   M dev/core/src/com/google/gwt/dev/shell/remoteui/DevModeServiceServer.java
   M dev/core/src/com/google/gwt/dev/shell/remoteui/RemoteMessageProto.java
   M dev/core/src/com/google/gwt/dev/shell/remoteui/RemoteUI.java
   A dev/core/src/com/google/gwt/dev/shell/remoteui/ViewerServiceClient.java
   A  
dev/core/src/com/google/gwt/dev/shell/remoteui/ViewerServiceTreeLogger.java
   M dev/core/src/com/google/gwt/dev/shell/remoteui/remotemessage.proto



--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to