[interfacekit] Re: Phase 1

>> OpenTracker (and a little bit deskbar) has tons of dependancies
>> on internals of both the app_server and registrar,  not just
>> on some extern"C"   functions but also message::what
>> constants and the like.
>
>Functions? How can it call functions of other applications? I doubt, 
that
>the Tracker is linked against them. Mmh, maybe internal libbe 
functions?

Yup -- silly expression sorry. The functions of the app_server
I thouhgt off are the ones invoked by the BMenuItem's of
the deskbar dedicated to show/hid'ing windows, changing the
active window decor ..etc; but anyway i'm digressing, in this thread,
here goes:


>> Those are easy to spots, Pavel(?) went to great pain to
>> outline each of them with one of those famous "will robinson"
>> comment headers, so people may just $ grep  for those.
>> 
>> Since you're at the stage when some messaging protocol has
>> to be decided, maybe have  alook at all this; it will make
>> the OpenBeOS-soon-to-be-renamed code not pretty, but I
>> guess that's the price to pay to be compatible in R1...
.
>However, I think, the matter is not that critical, as we could add
>needed functions/messages later. Aside from this, we also have the 
Tracker
>sources and can fix those.

Right, with the manpower on the project this might be feasible;
I was "impressed" (negative meaning) at the sheer quantity
of hardcoded dependancies, but as I said they are clearly delimited
so the worst scenario (having to dig up) is avoided.

--
PGP key: http://cdegea.free.fr/degea_kagi_pubkey.txt | BeDev E-16870
"What's oil got to do, got to do with it" -- F02 Chorus

Other related posts: