History log of /frameworks/layoutlib/remote/tests/src/RemoteBridgeTest.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
62413126b979e60482d6dd7d4ec8ce1412c61da5 06-Nov-2017 Diego Perez <diegoperez@google.com> Add ability to load remote classes

This implements LayoutlibCallback.loadView so it can load classes from
the other side of the remote connection.

Test: Added test
Change-Id: Ic79a05a4972ca35919c2682ac1099f9fb3e2a48f
/frameworks/layoutlib/remote/tests/src/RemoteBridgeTest.java
ce1a4634e3b96e7e4d043afa4d5cc8ab23ce92db 06-Nov-2017 Diego Perez <diegoperez@google.com> Run RemoteTests in a separate JVM

This creates a more realisting environments for the tests and hopefully
will avoid subtle errors when not using correctly remote primitives.

Test: Updated remote tests
Change-Id: I95229184769814f119b826a05a26c91c9709eeef
/frameworks/layoutlib/remote/tests/src/RemoteBridgeTest.java
5c5efc433eb4cc81f59bcfaf28f5e72b38f7a829 01-Sep-2017 Diego Perez <diegoperez@google.com> Initial work for remote layoutlib

This CL creates the API and proxies to support remote layoutlib (in a
separate process).
The classes are separated in three modules: client, common and server.

The client includes the classes meant to be used from Android Studio.
Server includes the new layoutlib server that will eventually end as a
separate jar file from the client.

TODO:
- Support custom component class loading
- Improve performance of remote streams and image transfers
- Add Android build files

Test: Adds initial test checking that it can pass renderActivity
Change-Id: I34cf050ec099282683d87b75a576e4a3ad067fdd
/frameworks/layoutlib/remote/tests/src/RemoteBridgeTest.java