
|
[openbeostranslationkit]
||
[Date Prev]
[04-2002 Date Index]
[Date Next]
||
[Thread Prev]
[04-2002 Thread Index]
[Thread Next]
[openbeostranslationkit] Re: Beautification Topics
- From: "Brian Matzon" <brian@xxxxxxxxx>
- To: <openbeostranslationkit@xxxxxxxxxxxxx>
- Date: Tue, 2 Apr 2002 23:58:13 +0200
----- Original Message -----
From: "Travis Smith" <sage@xxxxxxxx>
> Headers:
> /open-beos/openbeos/headers/obos/public/translation
>
> Source:
> /open-beos/openbeos/sources/os/kits/translation
Thnx!
> 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/).
Heh - have done that before a couple of times too :)
It's a shame we don't have access to the actual repository - could
just delete attics then.
I use CVS daily, so I can add the initial files if you want to?
Where should the test cpp/h files go (along with directory structure
and data files)?
> 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.
me 2, but the last time I changed job I had to go from one
coding convention to another, and it's a lot easier to just change
your habit than to argue your case - at least with my colleague's it was :)
> I did some work on the web page. I think it looks a bit cleaner. Testing
> is the same for each class.
Yep - definitely nicer!
I have some sparetime tomorrow evening, will try to commit
and fix some more tests...
/Brian Matzon
|

|