Re: [Armory-devel] About using qt in armory
Status: Planning
Brought to you by:
bicofino
|
From: <ana...@gm...> - 2007-06-22 14:21:14
|
Darrik, Thanks for your comments. The server and client I have written in C is portable across all *nix, and with a couple of #ifdefs, will work on windows too. But I agree with you on using a cross-platform tool because it eases maintenance. > B) Instead of writing some plugins and having some built-in > functionality of the client, I suggested we write a client that simply > loads whatever plugins it's told to. the client and the statistics gathering programs are very much separate (please see the server and client code in the 'backend' directory in 'test' on sf SVN, though it can be improved much more) > > A cross-platform toolkit (while it may not support -every- possible > platform) will allow us to save dev time on the major ones, and if need > be, we can still #ifdef the hell out of some code for legacy systems and > platforms not supported by our toolkit. Qt seems like a good choice to > me (especially since I have a lot of it written already), and it > provides a build system with tools for abstracting cross-platform > compilation. > I am not familiar with Qt other than that it a tool to develop GUI, but have you taken a look at the ADAPTIVE Communication Environment (ACE) C++ libraries (http://www.cs.wustl.edu/~schmidt/ACE.html)? It has been developed written specifically to make platform dependent things like network programming, process and thread creation, inter process communications portable across OSes. There is also the BOOST libs (asio.sorurceforge.net), but this is not as wide as ACE in terms of system programming interfaces provided. Let me know what you think of this. But one thing is using these tools wont help in getting the performance statistics because they *are* highly OS specific. we cant make that portable. Do let me know you opinions. Thanks, Ananth |