Cocoa/Windows parallel dvlpmt
Cocoa/Windows parallel dvlpmt
- Subject: Cocoa/Windows parallel dvlpmt
- From: Erez Anzel <email@hidden>
- Date: Sat, 31 Jan 2004 14:05:15 -0500
I have been happily developing in Cocoa using XCode 1.1. But I have to
port to Windows, very quickly. I want to keep my duplication of effort
to a minimum, so that I can maintain and enhance both products
efficiently.
I've read through the archives, and have come to the conclusion that I
should do the interface of my CAD-like (but with lots of internal math)
application in two parallel universes: Cocoa/XCode and MFC/Visual C++.
I've used MacApp in the distant past, and assume that the MFC
experience will be similar. I used CodeWarrior and PowerPlant for about
a year, but dropped it this past June when I got the impression that it
wasn't any longer (if it ever was) the best way to do cross-platform.
(I also switched to Cocoa this past June.)
I know almost nothing of Windows, MFC, Visual C++, etc. I have no idea
how (or if) they implement multiple Undo, for instance. I have never
touched Windows, and don't have a Windows machine; I figure I'd start
with Virtual PC for Mac.
I am not sure if I should have two separate models (in the MVC sense).
In Cocoa I could use NSMutableArray, and each of my objects could be an
NSObject subclass, which is what I have now. In Windows I'd have some
parallel. Or should I use STL lists or vectors, and then in Cocoa have
a model object which owns the STL list of raw C++ objects, and do
likewise in Windows. For actions upon my objects, I'd perhaps use some
Objective-C wrapper in Cocoa as I operate on each individual object.
That might, however, be very inefficient.
I'm stabbing in the dark.
Any pointers, guidance, etc. would be greatly appreciated. When I have
more cash, I'll hire someone who knows what they're doing.
Bye...Erez
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.