Porting a WPF App to Mac ...
-
Oh yeah, I'm coming from the angle that it would be a rewrite from the ground up basically ... a few resources could be carried over like XML lookup tables but that's about it I would imagine. haha!! - from appleinsider ... "C# is the microsoft spawn of satan java hack that is windows only. " This looks interesting ... http://www.mono-project.com/Mono:OSX[^]
Jammer Going where everyone here has gone before! :) My Blog
"You take your stinkin' Mac ways away from these forums. We don' wan' no stinkin' Mac users."
Deja View - the feeling that you've seen this post before.
-
"You take your stinkin' Mac ways away from these forums. We don' wan' no stinkin' Mac users."
Deja View - the feeling that you've seen this post before.
-
Jammer wrote:
heh heh ... nix ... pah!
And now you're bringing up nix? Dear god. Will the horror never end? :wtf:
Deja View - the feeling that you've seen this post before.
-
Jammer wrote:
heh heh ... nix ... pah!
And now you're bringing up nix? Dear god. Will the horror never end? :wtf:
Deja View - the feeling that you've seen this post before.
-
Hi All, This is a way off yet but its something I have to think about. My current project has a large enough potential Mac user base to make a mac version a viable effort. Have any of you here undertaken such a task? I'm not even sure what languages you can use to program for a Mac. I know that its a Unix based system which is significantly different platform and would require a stack of effort to learn but it would be worth it. I need to have a read up but has anyone got any useful info on this topic? Cheers,
Jammer Going where everyone here has gone before! :) My Blog
Hi there, I am working on a project where the situation is the other way round. My background is a boxed software product which is available for both Mac and Windows. After we did a port originally (using GNUStep) we ended up rewriting the application from scratch using Windows native tools (C# and WPF). The reasons: - Windows and Mac users expect a very different user experience which requires two different user interfaces. - Both platforms have different strengths and what is easy on one platform can be very hard on the other. We try to keep our two products feature-identical but the implementation and usage of the features can greatly differ. - ObjectiveC is a dynamic language, C# is a statical typed language. The way you program in these languages is very different. - If you want a great product you need great developers. A Windows developer is likely not the best choice to create a 'good' Mac application and vice versa. Tools that work on both platforms have not the power of the native tools. (eg. Mono) As an example I want to refer to Microsoft Office. Office on Windows and Office on Mac has a VERY different user interface. I think Microsoft made the right choice by understanding that users on Mac and Windows have different expectations.
-
Hi there, I am working on a project where the situation is the other way round. My background is a boxed software product which is available for both Mac and Windows. After we did a port originally (using GNUStep) we ended up rewriting the application from scratch using Windows native tools (C# and WPF). The reasons: - Windows and Mac users expect a very different user experience which requires two different user interfaces. - Both platforms have different strengths and what is easy on one platform can be very hard on the other. We try to keep our two products feature-identical but the implementation and usage of the features can greatly differ. - ObjectiveC is a dynamic language, C# is a statical typed language. The way you program in these languages is very different. - If you want a great product you need great developers. A Windows developer is likely not the best choice to create a 'good' Mac application and vice versa. Tools that work on both platforms have not the power of the native tools. (eg. Mono) As an example I want to refer to Microsoft Office. Office on Windows and Office on Mac has a VERY different user interface. I think Microsoft made the right choice by understanding that users on Mac and Windows have different expectations.
-
Very interesting post Pakl ... Just out of interest what boxed product is this background of your?
Jammer Going where everyone here has gone before! :) My Blog
-
Nice ... I'm going to check that out tomorrow ... looks like a cracking bit of software!
Jammer Going where everyone here has gone before! :) My Blog
getting better and better... we are still on our way from GDI+ to WPF. quite an interesting journey :-D
-
getting better and better... we are still on our way from GDI+ to WPF. quite an interesting journey :-D