[interfacekit] Re: input_server and registrar

"Marc Flerackers" <mflerackers@xxxxxxxxxx> wrote:
> > I also think those who follow this project have understood that we
> > won't replace R5 piece by piece for those things - and so much work
> > just for a PR gag...
> I don't know how long it takes. At least for the input_server it took 
> me
> less then an hour to write the libbe functions which communicate with 
> the R5
> input_server, and they work. The OpenBeOS input_server just needs to 
> respond
> to these messages (a question of changing the message id's and 
> message field
> names), to work with the R5 libbe.
> And it's not just for PR. Doing it this way, the input_server could 
> be
> tested in a working environment. And completely tested and debugged 
> before
> the other components are ready. Also performance can be compared.

Oh, sorry, I am not against doing this for the input_server - but I 
would be against doing so for the app_server and registrar. I don't 
think that would pay off well.

> The other way you would wait for app_server/input_server/registrar/
> libbe to
> be finished, and then hope each one works, and works well together.

Yes, that will be a lot of fun and excitement ;-))
I think our unit tests are a better approach to check the functionality 
of our code than a working environment (at least they should be done 
before); we have found so many bugs in Be's implementation of the API 
that way.

Adios...
   Axel.

Other related posts: