FreeLists / openbeostranslationkit / [openbeostranslationkit] Re: Beautification Topics

["Travis Smith" <sage@xxxxxxxx>]

Headers:
/open-beos/openbeos/headers/obos/public/translation

Source:
/open-beos/openbeos/sources/os/kits/translation

As to making the initial commits. I've never used CVS before. If someone
else has used it, they are welcomed to commit first. I tried once, and
added the wrong directly structure. (note the attic in
/open-beos/translation_kit/). 

I'm going to have to argue with you on the coding guidelines. I do what
I do, because I've been doing it for eight years. Its habit, I don?t
even think about it. 

I did some work on the web page. I think it looks a bit cleaner. Testing
is the same for each class.

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

-----Original Message-----
From: openbeostranslationkit-bounce@xxxxxxxxxxxxx
[mailto:openbeostranslationkit-bounce@xxxxxxxxxxxxx] On Behalf Of Brian
Matzon
Sent: Tuesday, April 02, 2002 3:09 PM
To: openbeostranslationkit@xxxxxxxxxxxxx
Subject: [openbeostranslationkit] Re: Beautification Topics

----- Original Message -----
From: "Travis Smith" <sage@xxxxxxxx>
> Yeah - it's a bit better than mine, but I never professed at being
good
> with UI. There's a reason I'm not working on the CDT.
:)

> Beautification
> doxygen - I know nothing of. I've never used it, but I will look for
> something to forward to everyone. It's what the documentation will be
> based upon, so it is wisest to use it.
I'll be looking into it too...

> Coding guidelines - http://opentracker.sourceforge.net/guidelines.html
> it is what the project agreed to use, so we're using them. They aren't
> too hard to follow. I will admit that it takes a while to use 'other'
> guide lines when you are used to your own.
I¨'ve been through this two times before - the problem isn't getting
used
to new conventions. The real problems is when a member thinks his/hers
way is the best and only way... :/

> As to CVS: Mike and Brian - I'll get you added for access. I'll let
you
If I am not mistaken, I am on the Developer list on sourceforge, so I
should already have write access... I was just waiting for the initial
commit so that I actually know where the files go...
is it
  /translation_kit/source
  /translation_kit/translation_kit
  /openbeos/sources/os/kits/translation/
the files are to be placed??
and in the latter case should header files go in
  /openbeos/headers/obos/public/translation/
and if so - just kit headers and no test headers or.

As you can read - I am a bit confused about
the location of files... :) - thats why I wanted you
to make the initial commit.

> know when that's working. Also, try to start using JAM
> (http://www.perforce.com/jam/jam.html).
Already looking at it...

/Brian Matzon