[openbeostranslationkit] Re: CVS Access and BTranslatorRoster

Good Job!

I'll e-mail Michael to add you to the list Mike!

--------------------
~Travis Smith 
sage at ieee dot org

-----Original Message-----
From: openbeostranslationkit-bounce@xxxxxxxxxxxxx
[mailto:openbeostranslationkit-bounce@xxxxxxxxxxxxx] On Behalf Of Mike
Wilber
Sent: Wednesday, June 12, 2002 11:10 PM
To: openbeostranslationkit@xxxxxxxxxxxxx
Subject: [openbeostranslationkit] CVS Access and BTranslatorRoster


OK, here is an update for everyone:

BTranslatorRoster is basically finished. I think there is a memory leak
issue with it, but I don't know how best to deal with that yet.
BTranslatorRoster has a static member variable to store the default
translators, but I don't know when or how I should destroy the static
variable. Be's TranslatorRoster.h has some funky functions and a friend
class listed in its private section, so I'm not sure what they did to
solve the problem.  I'm guessing some other class deletes the static
data in BTranslatorRoster at some point.

So, basically there is only one more class to write: BTranslator. The
nice thing about BTranslator is that it doesn't do much of anything, its
an interface for people to write their own private translators. So, it
should be no problem to implement that class. I'd like to start on it
after I get BTranslatorRoster properly commented and put into CVS.

After that, I plan to go over BBitmapStream, get it as close to the
OpenTracker format as I can, and do some testing.

When all of that is finished, I should be able to make the OpenBeOS
Translation Kit to replace Be's Translation Kit. I'll replace Be's
version and Be's headers on my computer and see if there are any
applications that fail to work properly. After that, maybe I'll figure
out how to make it available so others can easily test the library.

I lost my CVS access when Michael Phipps weeded out the access list. So,
I haven't checked-in my changes yet.

Travis, if you are around, please get me added to the CVS access list.
If you are not around, I'll e-mail Michael Phipps and get it taken care
of.

Michael Wilber
wilber@xxxxxxxxxxxxxxxx

Other related posts: