Re: Cocoa/Windows parallel dvlpmt
Re: Cocoa/Windows parallel dvlpmt
- Subject: Re: Cocoa/Windows parallel dvlpmt
- From: Erez Anzel <email@hidden>
- Date: Sat, 31 Jan 2004 17:40:48 -0500
Thanks, Phil, for the suggestion. I have considered GNUstep. But what I
gather is that it's not nearly ripe enough for me to use, and may not
be so for another year. I'm aiming to ship within just a few months
(ambitious, aren't I?). I don't have a computer science background, and
don't feel comfortable with using what I've seen.
Furthermore, I get the impression that, whereas it would be great to
write once and run everywhere (okay, at least two or three places), my
software would suffer from various compromises. It would end up not
being up to the level of what a program could look like if developed
with Microsoft's tools. This is the same impression I got from reading
postings concerning Trolltech's QT offerings (?).
Bye...Erez
On 31-Jan-04, at 3:11 PM, Philip Mvtteli wrote:
Am 31.01.2004 um 20:05 schrieb Erez Anzel:
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.
have you considered GNUstep?
Re
Phil
_______________________________________________
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.