FreeLists / openbeos / [openbeos] Re: openbeos Digest V2 #33

["Nathan Whitehorn" <nathan.whitehorn@xxxxxxxxxxx>]

> > > > Well, first of all, it's OOP in C, which is often a recipe for 
> > > > ugliness. The code I've seen (*not* leaked, the sample headers 
> > > > that 
> > > > were released) was a complete mess. Also, doing things in the 
> > > > kernel 
> > > > meant not really being able to interact with user-space apps. 
> > > > For 
> > > > instance, a net_server addon I wrote once that monitored 
> > > > ethernet 
> > > > activity put up a deskbar widget. BONE add-ons couldn't do 
> > > > that.
> > > >
> > > Nope, instead they use ioctl()'s to just those kinds of 
> > > parameters 
> > > filled in by the kernel driver.
> > > 
> > > Point being?
> > 
> > Point being that you would have to run a seperate application to 
> > put 
> > it 
> > in the deskbar, which is ridiculous. Same with DUN. You would need 
> > to 
> > run some kind of DUN monitor app to place it in the deskbar, which 
> > is 
> > needlessly increasing binaries.
> > 
> Not really - the code for monitoring network traffic + displaying the 
> icon in the Deskbar probably has nothing in common with the network 
> add
> -on, despite it being in the same binary.. Think about it.

Well, the add-on installs the network add-on. Besides, they couldn't be 
in the same binary using BONE. The kernel won't let you link against 
user-land symbols, which means no BViews anywhere in your binary, even 
if they aren't called. So different binaries are required.
-Nathan

--
Fortune Cookie Says:

Science is facts; just as houses are made of stones, so is science made
of facts; but a pile of stones is not a house and a collection of facts
is not necessarily science.
                -- Henri Poincair'e