X-platform strategies?
X-platform strategies?
- Subject: X-platform strategies?
- From: "Theodore H. Smith" <email@hidden>
- Date: Sat, 14 May 2005 20:50:11 +0100
Does anyone have an idea of strategies that would be useful when
porting MFC apps to a Cocoa based Mac app?
I'm finding that a lot of the code that I need to port, is doing stuff
to manipulate the controls, which is a lot of MFC code, or even worse,
custom controls based off of MFC.
I find it hard to imagine how to port this in such a way that maximises
code-reuse. I could just re-write almost everything except for reading
and writing of file formats and other serialisation stuff (Sockets)...
but I think that's not a strategy for the future, because as time goes
by, the app will only get more complex and having more and more forked
code will only make things worse.
Ideally, I'd like to use/write some kind of wrapper that made both
platforms have a consistent programming interface. I'm not sure how
doable that is, and what with all these custom controls defined, it
just makes the idea worse.
Just wondering if anyone had some idea of different strategies.
Right now it's looking like I must fork most of the app code, and very
little will be shared. That just doesn't feel like a good solution to
me.
--
elfdata.com/plugin/ Industrial strength string processing, made easy.
"All things are logical. Putting free-will in the slot for premises in
a logical system, makes all of life both understandable, and free."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden