Hi Kari,
MVC is an reasonable abstraction to use, but bear in mind that you will
probably want to make part of the controller and view code portable /
cross-platform as well, otherwise you'll still end up coding the same
things twice.
In other words, you need to look carefully at the program you want to
port and separate it into platform-independent and platform-specific
parts. There is no silver bullet here (i.e. the Builder pattern or MVC
will not magically make a perfect cross-platform strategy for you).
Also, do realize that you don't need to make the separation via a DLL or
framework: you can just compile cross-platform and platform-specific
files into one executable.
If you're an inexperienced developer, this will be difficult to pull
off, but you'll learn a lot along the way. :-)
Best regards,
Frederik Slijkerman
Filip van der Meeren wrote:
The Builder Pattern (http://en.wikipedia.org/wiki/Builder_pattern) is a
simple design pattern that enables you to write programs without knowing
in advance what classes you will be using. All you will do is program
against an interface.
But porting C# to mac actually means rewriting all C# code to ObjC or
C/C++...
Or you should fall back to the Mono-Project, but I find that not
everything is ported (well).
Filip van der Meeren
fi...@code2develop.com
http://www.sourceforge.net/projects/xlinterpreter
On 13 May 2009, at 10:37, Kari Valkama wrote:
Hi Filip,
I am also interested in porting a Win app to Mac. It is a C# .Net app.
Could you please be more specific. What do you mean with portable
model and builder pattern for view and new concrete class for each
platform. That sounds like developing a new program, not porting an
old one.
I went to your xlinterpreter site at sourceforge.net, but it did not
have documentation, so I do not know if you meant that it could be
used for porting.
If I am sounding like a noob, that is because I am!
Yours,
Kari Valkama
Filip van der Meeren kirjoitti 13.5.2009 kello 10.20:
I would go for a portable model, and something like a builder pattern
for the view...
Just create a new concrete class for each new platform...
Mvg,
Filip van der Meeren
fi...@code2develop.com
http://sourceforge.net/projects/xlinterpreter
*** Send from my IPhone ***
On 13-mei-09, at 09:01, Тимофей Даньшин <ok5.ad...@gmail.com> wrote:
Hello.
I am about to get involved in a project on porting a windows program
into MacOS. The original program is written in C++ with limited use
of windows-specific libraries, and its owner wants the code that
will result from that project to be compilable both under Windows
and MacOS (and, preferably, other platforms).
We both understand, that that cross-platform code will only be, in
terms of the MVC model, the Model.
In that view I have two questions:
Is it a good idea to port a program that way? Or is it, perhaps,
better to have platform-specific code for each system?
If it is a good idea, then how should we create a project in a
repository so that it was usable both in Windows and in MacOS? Say,
a framework for Mac and a dll for win?
Is there anything i need to know before starting that?
Thank you in advance,
Timofey.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
