From: raymond <laseray@gm...> - 2009-06-23 15:46:44
I am starting to cleanup/order the code/file/directories to push it onto the
SF bitext2tmx Git repository. So just providing some preliminary information
about what I am thinking of doing in this regard so we can discuss things and
move forward to version 1.0.M1.
Firstly, pushing all the code to Git is very easy and the commands are
straightforward as far as I can see. If you need information about Git, SF
has its own page at http://sourceforge.net/apps/trac/sourceforge/wiki/Git
with regard to how to use it on SF. And the official Git documentation is at
A primary issue is how work is to be performed once the master branch has
been put up. In this regard, I would like to create separate branches for the
actual work (e.g., at least a branch named "experimental"). All the unstable
changes and experimentation can be done on this "experimental" branch
while retaining the master branch for stable versions/releases after
sufficient testing is done. Thus, I am asking that developers checkout/checkin
code from the experimental branch and not the master one. There is also
a way to control who commits to specific branches I believe. This might be
an option to use. There are only two people going to be doing any work on
B2T as far as I know, so it may not be an issue as long as we keep each other
informed as work progresses.
Anyway, if you have any other ideas about this let us all know so we can
choose the best way going forward.
Apart from that, I am looking over the current code and I have to cleanup and
make some rearrangements. I am trying to simplify the /src folder hierarchy
and have decided to move some resources outside of this path. The program
icons used by the docking desktop and other components is outside now so that
these can easily be changed without recompiling the application, it is the
same as the localizations in this regard then. And, of course, the docking
desktop is completely experimental in this version (although I have experience
using the library in OmegaT+), so there might need to be some rearrangement
or redesign of certain components. You will have to run the application when
it is available, see what you think and let us all know.
Anyway, I should have the first commit to the repository up in the next few
days. Then we can start to integrate the newly ported code from TagAligner
by Miquel into it. Version 1.0.M1 will definitely have some significant
improvements all around.
Apart from that, B2T sorely needs better documentation, in all languages
supported. Not to mention improvements to the webpages. Help with this,
when people have time, would be a real plus for users interested in B2T.
Your thoughts or comments...