On Mon, Nov 10, 2003 at 09:58:31AM +0000, Berin Loritsch wrote: > Martin Man wrote: > > > >I'd like to contribute it, but at this moment my C++ port uses at least QT, > >log4cpp and cppunit which are (from the license point of view) ASF > >incompatibile. Refactoring all of them out could be a major effort and I'd > >like to first know whether there is an interest for it before touching the > >code. > > :) The APR (Apache Portable Runtime) would be a better foundation for > building a framework like this without tying it to a graphical library > (QT)--which in itself can be controversial depending on who you talk to.
I agree completely with you, in fact I don't see any problem replacing qt dependence with apr dependence (except the manpower that I don't have at the moment) > My question is how big is your Avalon++ project? If it is *just* the > interfaces, then there is no big issue. Of course the C++ equiv. of an > interface is a pure virtual abstract class. The code resembles Avalon Framework (just framework), e.g., it's a set of interfaces and several Default* implementations. The code is already avaliable in the public cvs, you can check it and see how complicated it is. I've updated, renamed and relicensed the code and put it to the cvs, you can check it out using cvs -d :pserver:[EMAIL PROTECTED]:/publiccvs login (press enter when prompted for password) cvs -d :pserver:[EMAIL PROTECTED]:/publiccvs co swaloun-framework (note that ATM you probably wont be able to compile it, since two small dependent libraries are not yet in the cvs, but they'll be there hopefully during this night) as you can see I've renamed the project from ccavalon to swaloun-framework and placed it under GPL (due to QT dependency, QT is itself GPL) to not conflict with original avalon license. I hope I've not violated any rights... sincerly, martin p.s. feel free to contact me directly if you have any questions
signature.asc
Description: Digital signature
