|
From: Alexander S.K. <al...@be...> - 2013-06-21 06:08:10
|
Luiz, please, clarify your point. Does you suggest to leave all as it is and work on current SVN branch, or you mean that it is better to use for the new HwGUI repository only the Sourceforge SVN ? I never like the idea to have two HwGUI, but here is the reality: I'm not ready more to dig in complicated and labyrinthine current HwGUI code in SVN to clean it up and look for bugs. In a last half of year I investigated the sources few times, looking for a bugs, reported here, and every time I had a feeling that it's better to "cut the Gordian cnot" - to replace the whole file with its more simple old version. For me much more simple to clean 2.16c and then introduce there some of enhancements of current version,if needed, but, probably, in a bit other implementation. That's why I use 2.16c for myself and I want it to be a base for further HwGUI development. And for me the question is where to place 2.16c sources. CVS, SVN, GIT, ... - the choice isn't important for me. We all worked with CVS few years ( letodb is still under CVS ) and I hadn't problems with it, moreover, SVN is worse for me because of a bigger size of a local repository. Sourceforge, github or something else ? I haven't much experience with github, excepting a passive work with a Harbour repository. Are there real problems with it ? Sourceforge isn't an ideal, too. It becames more and more slow, and there appears problems which aren't solved by their team One of them you will see, if you visit the HwGUI or LetoDB page - the latest activity is marked as of 2012-12-07, while there was many code uploading and some other changes since this time. I reported about this to Sourceforge a couple of months ago and got a link to some kind of discussion board, where this problem was noted as awating of solving for a long time already... So, what's your point about these all ? Regards, Alexander. > Alex > > Please, no github, stay all hwgui only on SVN > > |