[interfacekit] Re: Graphics Drivers and the App Server (LONG)

>So this isn't anything more than a BWindowScreen app that handles a
>single key stroke, right?  Hmm ... probably not worth checking in. 
>Dunno.
I just thought I'd mention that a little bit of code is being flung around. 
Nothing that can be really considered progress, though. When I do get 
something worth checking in, I'll get all my CVS stuff squared away and check 
it in.

>> AtheOS uses a layer system which we could probably use conceptually 
without
>> much problem. As for messaging, I've read up a little on it. BMessages are
>
>Are you familiar enough with the AtheOS layer system to write a little
>something up about it?  That would save everybody else some time.
I have almost no spare time tonight, but I'll look into things and write 
something up for you guys in the next couple days.

>I think you're confusing the accelerated functions obtained from the
>driver with the relatively new accelerants which are used for 3D
>acceleration and the like.  The latter is what I want to know about. 
>Maybe these things are only available with the new OpenGL ... nope, just
>checked.  See /boot/beos/system/add-ons/accelerants.  There are a whole
>bunch in there.  Just did nm on stub.accelerant and it definitely seems
>to be, in great part, a cover for the "accelerated" functions obtainable
>from standard drivers.  There are some intriguing new symbols there like
>"stub_get_engine_count", "stub_acquire_engine" and
>"stub_release_engine"; what exactly is an "engine"?  I have a feeling
>that figuring out how accelerants work is going to be a key thing.
>
>e
I suspect you're right and also that you're about 2 steps ahead of me. I 
forgot that we could actually have OpenGL and have it accelerated, too. Guess 
that's what I get for jumping on the bandwagon at R5. :)

--DW

Other related posts: