[interfacekit] Re: input_server and registrar
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Mon, 16 Jun 2003 17:36:26 +0200 (MEST)
On Mon, 16 Jun 2003, Marc Flerackers wrote:
> I spent some time figuring out the protocols used by input_server and the
> registrar. It seems they're really easy. I wrote the _control_input_server_
> function and BInputDevice class, and it seems to work perfectly on BeOS R5.
> With this documentation it's possible to write all the input server
> functions in libbe, and test it on R5, and to write an input_server which
> can replace the R5 one.
> For the registrar I didn't write any class yet, and my documentation is
> still incomplete, but it's a start. It looks like the OBOS BRoster functions
> only need little adaption (id's and field names) to make them work with R5.
For the registrar I don't see what to gain by trying to make it run under
R5. In particular because we did neither implement all the private methods
of BRoster, nor do I believe the semantics of the implemented ones is
exactly the same. So, to really get it working with R5 a bit more than
just a little work would need to be invested. It's simply not worth it, I
believe.
CU, Ingo
- References:
- [interfacekit] input_server and registrar
- From: Marc Flerackers
Other related posts:
- » [interfacekit] input_server and registrar
- » [interfacekit] Re: input_server and registrar
- » [interfacekit] Re: input_server and registrar
- » [interfacekit] Re: input_server and registrar
- » [interfacekit] Re: input_server and registrar
- » [interfacekit] Re: input_server and registrar
- » [interfacekit] Re: input_server and registrar
- [interfacekit] input_server and registrar
- From: Marc Flerackers