If you're rolling your own cross platform UI code, then you could consider having abstract classes representing UI elements; subclass for each platform as appropriate. Or, as you suggested, instead of subclassing, simply include the implementation of each class on a per platform basis but keeping the declaration uniform. You could even have a "cross platform implementation" file that is included in every platform build, but have additional platform specific "extensions" to those classes. It really depends on your needs. On 1/28/11, Littlefield, Tyler <tyler@xxxxxxxxxxxxx> wrote: > Hello, I know that there are cross-platform libraries, I just didn't > want to mess with them to much, unless I needed to, because as you say > there is a big problem with trying to make everything work with one library. > On 1/28/2011 3:29 PM, qubit wrote: >> Hey there Ty -- perhaps you know this already, but you may find that an >> awful lot of the core code is influenced by the choice of GUI, and so you >> may end up doing a lot of development in your 3 GUI's each time something >> new is added. >> You could get a cross platform GUI library like swt in java or wx widgets >> to >> reduce the amount of work, but you sacrifice something when you try to ram >> the same type of GUI on all platforms. There was a thread on that on the >> brailleblaster list, which is using java and SWT. >> Are you still working on your aspen mud framework? Is that what you are >> asking about? >> I am going back to get a microsoft live id...grumble, brumble. >> Cheers. >> --le >> >> ----- Original Message ----- >> From: "Littlefield, Tyler"<tyler@xxxxxxxxxxxxx> >> To:<programmingblind@xxxxxxxxxxxxx> >> Sent: Friday, January 28, 2011 3:33 PM >> Subject: createing a client with a core and cross-platform gui >> >> >> Hello all, >> I have a quick question: 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? >> > > > -- > > Thanks, > Ty > > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind