[interfacekit] Re: BDeskbar completed

Good deal!  The interface kit team portion of openbeos.org has all our 
outstanding tasks, and there are plenty.

e

>>> I expect that the libopenbeos.so will not be able to send 
>>> BMessages to the BeOS deskbar because of the differences in the 
>>> messaging protocol.
>>
>>The only difficulties that may arise are how to target the Deskbar 
>>application, as the signature/team BMessenger constructor uses 
>BRoster, 
>>and the Deskbar is of course not registered to our roster. But you can 

>>search for the Deskbar's team and AppLooperPort, make BDeskbar 
>>temporarily a friend of BMessenger and use the private team/port 
>>constructor (preferred = true, token is ignored). The messaging itself 

>>should be compatible with that of BeOS -- currently we're using the 
>>original BMessage anyway.
>
>Well, I cheated and put my source for BDeskbar right into my testcase 
>code and called it JDeskbar.  I built all that locally and showed that 
>when my "JDeskbar" implementation was linked with the rest of libbe.so, 

>everything works fine.  When I use the actual BDeskbar code compiled 
>into libopenbeos.so, the test fails because of a B_BAD_PORT return code 

>(which would be expected).  So although the tests as checked in will 
>fail, I am pretty sure the code is OK.  Its just that the deskbar 
>itself is not running under our own app_server yet.
>
>So, I have finished off BDeskbar.  I don't think I have any assignments 

>left in my name so if there is something out there for me, please let 
>me know.
>
>>CU, Ingo
>
>--
>Jeremy Rand
>jrand@xxxxxxxx

Necessity is the plea for every infringement of human freedom. It is the 
argument of tyrants; it is the creed of slaves.
        -William Pitt, British prime-minister (1759-1806)

Other related posts: