Re: Cocoa/Windows parallel dvlpmt
Re: Cocoa/Windows parallel dvlpmt
- Subject: Re: Cocoa/Windows parallel dvlpmt
- From: Glen Low <email@hidden>
- Date: Sun, 1 Feb 2004 12:33:03 +0800
I may yet hire a Window developer to guide me through the jungle. How
hard can it be? (Famous last words!) I am not so concerned about my
product being pretty; I'm focusing on utility at first.
My current Cocoa app accesses many C++ files which I created while
using CodeWarrior and PowerPlant. (I want to wean myself off of
PowerPlant, by removing from my code any last depencies upon it.) My
"engine" is all C++. I've learned to mix and match where necessary. I
use STL vectors etc. in many of those files. All my C++ implementation
files have .mm suffices now, though I guess that I may have to change
some setting in Xcode and switch back to .cpp for the benefit of
Microsoft tools.
Depending on how much of a reach you want on the Windoze platform, you
may want to consider .NET. Managed C++ is .NET wedded to C++, just like
Objective C++ is Objective-C wedded to C++. I think the object model on
.NET and the functionality is far better and easier to get into than
MFC, and there's GUI layout tools similar to IB. However the user would
need to have .NET installed on their Windoze machine.
The Core Foundation C++ object approach may be very helpful. If such
an object can bridge toll-free with equivalent Cocoa/Objective-C
objects, and also work in a Microsoft world, then it saves me a lot of
trouble. But I'll have to research this further; I've never looked at
Core Foundation. I take advantage of the fact that my current model's
objects are instantiations of NSObject subclasses; I don't know if I
can have my cake and eat it too.
If you design your model properly as C++ objects, they can be accessed
directly from either Managed C++ in the Windows .NET world or Objective
C++ in the Mac world. The model will likely have to handle memory
allocation since .NET uses garbage collection and ObjC uses reference
counting, but they should be able to exist as lightweight C++ objects
in both worlds.
Alternatively you could either crib a Windoze implementation of
NSObject from the Core Foundation sources, or dummy one up yourself for
.NET.
If you need a Windows developer, I have had some experience porting
between platforms and currently develop in both Windows and Mac OS X.
Cheers, Glen Low
---
pixelglow software | simply brilliant stuff
www.pixelglow.com
_______________________________________________
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.