DM> Hi devl, DM> Who's the cunt who took the windows-specific code out of fcptools? DM> I was starting to implement the non-dbr inserts into fcpputsite, but I DM> can't be bothered now. DM> Someone else can do it. DM> I now wash my hands of the code entirely. DM> David
The basis of my outburst is that I put a hell of a lot of time into making fcptools work on linux and windows, and to keep the ezFCPtools API identical, and the tool command line options. This was done with client writers in mind, and was intended to empower client authors to create platform-independent clients - either console progs, or GUI apps using wxWindows, FLTK, GTK+ etc. Prior to fcptools, there was already libfcp, which was *nix-only. The only raison d'etre for fcptools was a degree of platform-independence. It feels like my effort was wasted. FreeWeb won't even build with the cvs version of ezFCPlib. I was going to re-write FreeWeb to use FLTK, and thus build native Windows and Linux versions. I'm no particular fan of windows, and ultimately plan to make my network a 'doze-free zone, but with the blatant and deliberate removal of windows platform support, I have lost enthusiasm. Enjoy the code guys. Do what you want with it. David _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
