blocks|key|2542542|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2542543|There's并非易事，就是这么简单。令人沮丧的是，你只需要擅长编写Mac程序就行了。|ordered-list-item|offset|length|style|BOLD|2542544|说：“我非常肯定所有UIView的东西都能在那个类里工作”--不幸的是，不行。每件事都不同，你必须努力工作。|2542545|2542546|这不是一场有趣的演出。确保你真的，真的认为这在财务上是值得的。|2542547|抛开其他问题不谈，如果你在iOS应用程序中堆叠了很多视图，请注意“同级视图在操作系统上不起作用”的问题。从本质上讲，如果你在手机上到处依赖视图的嵌套层次结构，你将不得不在Mac上使用图层(而不是简单的视图)！|2542548|单击此链接：Is+there+a+proper+way+to+handle+overlapping+NSView+siblings?，查看该特定问题的详细信息！|2542549|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/466297/is-there-a-proper-way-to-handle-overlapping-nsview-siblings/3739007#3739007^0|0|0|C|0|0|0|0|0|6|1O|0|0^^$0|@$1|2|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|Z|7|@$D|10|E|11|F|G]]|8|@]|9|$]]|$1|H|3|I|4|C|6|12|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|13|7|@]|8|@]|9|$]]|$1|K|3|L|4|5|6|14|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|15|7|@]|8|@]|9|$]]|$1|O|3|P|4|5|6|16|7|@]|8|@$D|17|E|18|1|19]]|9|$]]|$1|Q|3|-4|4|5|6|1A|7|@]|8|@]|9|$]]]|R|$S|$4|T|U|V|9|$W|X]]]]

<ol>
<li>There's no easy way. It's that simple. Depressingly, you simply have to become good at programming the Mac.</li>
<li>"I'm pretty sure all the UIView stuff will work in that class" -- unfortunately, no. Everything is different that enough you have to work hard.</li>
</ol>

It's not a fun gig. Make sure you really, really think it's worth it financially.

Apart from anything else, be aware of the "sibling views don't work on OSX" problem if you stack up a lot of views in your iOS app. Essentially, you will have to change to using layers (instead of simply views) on the Mac if you rely on nested hierarchies of views here and there on the phone!

Click this link: <a href="https://stackoverflow.com/questions/466297/is-there-a-proper-way-to-handle-overlapping-nsview-siblings/3739007#3739007">Is there a proper way to handle overlapping NSView siblings?</a> for the gory details on that particular problem!

blocks|key|2542585|text|你可能还有很多工作要做。虽然纯算法类不需要任何更改就可以移植，但任何涉及UIKit的类都可能需要重写或大量调整。OSX上的UI类设计模式是视图之间的关系，其中您的代码负责管理控制器；而在iOS上，它是视图控制器之间的关系之一，其中隐含着视图管理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2542586|当然，正如BoltClock提到的，你有交互的问题。由于触摸不再有效，您可能需要首先处理您的交互模型，甚至在开始移植之前也是如此。|2542587|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You may have a lot of work ahead of you. While purely algorithmic classes will port without any change, anything that touches UIKit will likely need to be rewritten, or heavily adapted. The UI class design pattern on OSX is that of a relationship between views, where your code is responsible for managing controllers; while on iOS it is one of a relationship between view controllers, where view management is implied.

Of course, as BoltClock mentioned, you have the issue of interaction. Since touch no longer works, you will probably need to work on your interaction model first, even before you start porting.

blocks|key|1586802|text|有一个开源的UMEKit库可以帮助移植一些UI类，但是您可能需要重写大量的UI，以便更好地处理鼠标/键盘/多窗口/菜单图形用户界面环境。基本的NSObjects，以及一些Open+GL和Quartz图形渲染，可能只需要很小的修饰即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1586803|entityMap|0|LINK|mutability|MUTABLE|url|http://kenai.com/projects/umekit^0|6|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There exists an open source (BSD) <a href="http://kenai.com/projects/umekit" rel="nofollow">UMEKit</a> library that may help with porting a few UI classes, but you may have to rewrite a fair amount of the UI to better handle the mouse/keyboard/multi-window/menu GUI environment. Basic NSObjects, and some Open GL and Quartz graphics rendering, may port with only minor touch ups.

blocks|key|2542667|text|正如其他人所说，移植可能是一件苦差事。不过，一般的技术是可行的。您可以在interface+Builder中重新设计界面(如果适用)，并检查不同的控件是如何调用的(CocoaTouch只有典型桌面控件的一小部分)。UI*通常变成NS*。Tableview委派是类似的，所以它可能会很容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2542668|我还是像往常一样推荐Aaron+Hillegass这本书。这是对iOS开发的一个很好的介绍，了解Mac开发会让你更有优势。|2542669|由于这是一款游戏，你可能需要考虑如何进入全屏模式。这个游戏不一定会占据整个屏幕，你也不应该强迫它。现在需要一套全新的首选项。当然，现在有了一些新的方法来处理Snow+Leopard的分辨率列表/更改(之前的方法会给出弃用警告)，这就涉及到了一些“有趣”的事情。|2542670|只要接受这一点，在一切“点击”之前，可能会有一个漫长的过渡期:)|2542671|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

As others say, porting can be a chore. The general techniques work, though. You redesign the interface in Interface Builder (where applicable) and check what the different controls are called (CocoaTouch only has a small subset of typical desktop controls). UI* typically becomes NS*. Tableview delegation is similar, so it will probably be easy.

I'll have to recommend the Aaron Hillegass book as usual. It's a great introduction to Mac development, and knowing iOS development gives you an edge.

Since it's a game, you probably need to consider how to do fullscreen mode. The game doesn't necessarily take up the entire screen anymore, and you shouldn't force it. A whole new set of preferences will now be necessary. There is of course some "fun" involved now that there are new ways to handle resolution listing/changing with Snow Leopard (with the previous ways giving you deprecation warnings).

Just accept that there will be a possibly lengthy transition period until everything "clicks" :)

blocks|key|4139608|text|Iconfactory的http://chameleonproject.org/+UIKit+for+Mac值得一看。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4139609|“变色龙是一项正在进行的工作。经过9个月的工作，该框架目前实现了大约60%25的UIKit。”|4139610|https://github.com/BigZaphod/Chameleon|4139611|entityMap|0|LINK|mutability|MUTABLE|url|http://chameleonproject.org/|1^0|C|S|0|0|0|0|12|1|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|G]]]]

<a href="http://chameleonproject.org/">http://chameleonproject.org/</a> UIKit for Mac
from Iconfactory is worth checking out.

"Chameleon is a work in progress. The framework currently implements about 60% of UIKit after nine months of work."

<a href="https://github.com/BigZaphod/Chameleon">https://github.com/BigZaphod/Chameleon</a>

Is there a preferred way to go about this?

The app in question is not too large . . . single-player game that I wrote over the course of a couple of months.

EDIT: I should add that I have no experience with mac development . . . outside of what comes naturally with being an iOS developer.

EDIT: Classes heavily used in the game: subclasses of NSObject, UIView, and UIViewController. I don't know much about NSView, but I'm pretty sure all the UIView stuff will work in that class. Also some use of UITableViewController. I do also have Game Center, but I can leave that part out for now. There is no multi-touch.

EDIT: My graphics is all stuff that is in the QuartzCore and CoreGraphics frameworks. I do have a moderate view hierarchy.

EDIT: If you are doing such a port, you may also be interested in the issue of <a href="https://stackoverflow.com/questions/4581556/porting-an-ios-app-to-mac-how-to-handle-memory-management">memory management</a>

port an iOS (iPhone) app to mac?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有没有更好的方法来解决这个问题呢？有问题的应用程序并不太大。。。我花了几个月的时间写的单人游戏。编辑:我应该补充说，我没有mac开发的经验。。。除了作为一名iOS开发人员所固有的东西之外。编辑:游戏中经常使用的类: NSObject、UIView和UIViewController的子类。我对NSView了解不多，但我非...

问将iOS (iPhone)应用程序移植到mac？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将iOS (iPhone)应用程序移植到mac？EN