On Mon, 17 Nov 2008 20:07:37 +0100 Nicolas Weeger <[EMAIL PROTECTED]> wrote:
> Hello. > > I do plan to have a C++/Qt (core only, no X dependency) version of > the server, with advanced stuff (dynamic archetype loading, ...). Well, one thought, is there any reason Qt-core as opposed Boost C++ perhaps? If I understand correctly, they provide similar faculties but Boost C++ also provides some rather nice looking python bindings that may make it far easier to move cfpython to a C++ code style. I'm not saying anything is wrong with Qt-core, and I've never actually used it or Boost C++ for that matter, but I'm just wondering if should maybe be considered, as it may have merits. That said, as you're likely going to be the main person in this code effort, simply having more experience with QT-core than Boost C++ can be a significant and quite valid factor. > So two options: > - I work directly on trunk - my preferred option, considering it's > "unstable" since some years, and doesn't seem to be soon stable, not > much work going on it > - I make a branch and work there - and if needed / when we want we > merge to trunk Not too much of a strong opinion, except that if you do work on trunk there should be either a tag or branch made for the current state of trunk. Best of luck, Alex Schultz _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
