[interfacekit] Re: app_server specs
- From: DarkWyrm <darkwyrm@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Tue, 12 Feb 2002 19:49:41 -0500
>Do we have a published plan of attack for app_server? Because how
>app_server, BWindow, and BView work together is going to become really
>important soon. I've got a hypothetical analysis of how the current BeOS
>app_server operates, but I haven't yet figured out how this meshes with
>our current app_server, which is based on AtheOS'.
Yes, we do. I haven't tweaked the schedule mostly because I've been the only
one working on it. I do my best work on my own, so that's been a good thing.
The app_server is currently on the back burner while the client classes are
in the works. As I've mentioned before I'm working on a BLooper and BHandler,
the main reason being that all BHandler, BLooper, BApplication, and BWindow
all have tendrils in each other. That reminds me - how should I test the code
for them?
>For example, OBOS app_server relies on drawing done by the application
>itself, whereas it doesn't seem like Be's does (rather, through a
>app_server thread thad handles these things).
>
>Isaac
Nope. If you look at prototype 4's source, you'll notice that there isn't any
drawing done by the test app. The only thing it does is make a bunch of
messages and fire 'em off to the server.
To enumerate my current plans:
1) Complete BHandler
2) Complete BLooper
3) Complete BApplication
4) Complete BWindow
5) Complete BView
6) Get back to the server
Once I return to getting the server done, I can test the new code I've got in
place for what will be prototype 5, which should be along the lines of
displaying a window. There's quite a bit of code in place already, but I
don't really have much of a way to test it. I *could* write a bunch of hack
test code, but why bother when I know I'll need to help (at least a little)
in the implementation of the mentioned classes.
I have a big problem concerning BBitmaps: the actual buffer for the bitmap
data is an area which is shared by the server. No problem, right? The problem
is in the allocation. George [Hoffman] wrote a memory manager from scratch
when he did this part of the app_server. I have no experience in this area
and no clue how to do it, either.
- Follow-Ups:
- [interfacekit] Re: app_server specs
- From: Erik Jakowatz
- [interfacekit] Re: Re: app_server specs
- From: Isaac Yonemoto
- References:
- [interfacekit] app_server specs
- From: Isaac Yonemoto
Other related posts:
- [interfacekit] Re: app_server specs
- From: Erik Jakowatz
- [interfacekit] Re: Re: app_server specs
- From: Isaac Yonemoto
- [interfacekit] app_server specs
- From: Isaac Yonemoto