The server side doesn't really have to be cross platform since you have more choice over where and on what it is going to run, yet if you use APIs that are already cross platform like boost for example, even your server could be mostly portable. I would say concentrate all the heavy lifting and complexity in the server and then create custom clients for each new platform you desire to support. Make separate projects for each of these clients so that you can use whatever GUI toolkit you want, and so that you can drop any particular client if it doesn't work out as expected.
GUIs are like flowers; they are pritty and valuable, but they are here today and gone tomorrow.
On 1/29/2011 12:11 PM, Lex wrote:
28.01.2011 23:33, Littlefield, Tyler пишет:I am developing a client-server app, and I want the client to run on windows, Linux and Mac. So here was y idea: I will develop the core in c++, then just use whatever library I want to per OS and compile it for that. So I'll have different "gui" folders that will hold the code for each separate gui, and then when I compile on anything I'll just include that into the project I'm compiling. Is this a viable solution? Are there other ways to do what I want?You can use a cross-platform GUI library. WXWidgets seems to be quite accessible, because it uses native widgets on each platform. We're using it to manage GUI in NVDA screen reader.Lex __________View the list's information and change your settings at //www.freelists.org/list/programmingblind
-- Kerneels Roos Cell: +27 (0)82 309 1998 Skype: cornelis.roos "There are only two kinds of programming languages in the world; those everyone complains about, and those nobody uses." __________View the list's information and change your settings at //www.freelists.org/list/programmingblind
