Re: private stuff "temporary" exposed

2014-10-03 Thread Alan Griffiths
On 03/10/14 14:13, Alan Griffiths wrote: > I guess my first step is to zap the platform-api code... Giving up for now. Zapping the code is easy. Understanding the surrounding code enough to be sure of not breaking things though... -- Mir-devel mailing list Mir-devel@lists.ubuntu.com Modify set

Re: private stuff "temporary" exposed

2014-10-03 Thread Alan Griffiths
On 03/10/14 13:28, Alexandros Frantzis wrote: >> > >> > However, things have not worked out as intended. These APIs are in use >> > for an (apparently stable) unity.protobuf.UnityService service copied >> > between platform-api, unity-mir and qtmir. > My understanding is that Unity is now using DB

Re: private stuff "temporary" exposed

2014-10-03 Thread Alexandros Frantzis
On Fri, Oct 03, 2014 at 12:23:40PM +0100, Alan Griffiths wrote: > Some time ago we introduce a "temporary" facility to hook into the > protobuf messaging protocol. This is exemplified by the > DemoPrivateProtobuf acceptance tests. This support was intended to allow > faster prototyping of some feat

private stuff "temporary" exposed

2014-10-03 Thread Alan Griffiths
Some time ago we introduce a "temporary" facility to hook into the protobuf messaging protocol. This is exemplified by the DemoPrivateProtobuf acceptance tests. This support was intended to allow faster prototyping of some features that would eventually migrate into Mir. Once these features were s