[interfacekit] Re: BDirectWindow doesn't compile
- From: "DarkWyrm" <bpmagic@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Fri, 19 Sep 2003 18:25:29 -0400 EDT
> I just noticed BDirectWindow doesn't compile.
> It is partially my fault (I didn't add the the needed
> UsePrivateHeader rule to the jamfile), but it's not just that.
> Since I usually work on single classes (BString, BRegion,
> BDirectWindow) I tend to work with BeIde, and then transfer the work to
our source tree. I know it isn't probably the best way to work, but
hey... :P=0D
You wouldn't be the only one working that way. If you turn out good
code, no one cares what you use. :D
> Anyway, BDirectWindow doesn't compile right now also because our
> BWindow header has changed, and it's not anymore like R5 one, more
precisely... there was a member variable "_BSession_ a_session" which
is now "BSession session" (Adi or DW did the change).
> Well, since BDirectWindow relies on R5 implementation of _BSession_,
> I should do some strange tricks to make it build within our tree ( I
should add a R5 header of BWindow, which will be used just by
BDirectWindow, at least until our app_server supports it), and I guess
it isn't the case... what should I do ? I guess I should remove it from
the build...
Not necessary to remove it from the tree. In fact, please don't. It
will receive its time in the sun, so to speak, when its time is due -
pretty much when a lot of other things have progressed in the
app_server and we can really get fixing things. For now, it can just
sit right where it is. The classes which communicate with the
app_server are not expected to be binary compatible in the sense that
you've achieved - drop it into R5 and it works just the same as R5's
implementation - but it's a nice bonus. The reason is that we're not
reverse-engineering the protocols used to communicate with the server.
It's just too time-consuming and too much work for something that would
be little more than qualifications for bragging rights. BWindow, BView,
BScreen, BCursor, and BApplication are all examples of the same kind of
compatiblity - they will work when libbe is replaced right alongside
the app_server and registrar.
--DW
- References:
- [interfacekit] BDirectWindow doesn't compile
- From: burton666@xxxxxxxxx
Other related posts:
- » [interfacekit] BDirectWindow doesn't compile
- » [interfacekit] Re: BDirectWindow doesn't compile
- » [interfacekit] Re: BDirectWindow doesn't compile
- [interfacekit] BDirectWindow doesn't compile
- From: burton666@xxxxxxxxx