4 ms·
Compiling Objective-C Using Visual Studio 2015 [video]
- jdmoreira 12y agohttps://dev.windows.com/en-US/uwp-bridges/project-islandwood https://dev.windows.com/en-US/uwp-bridges/project-islandwood
- mpweiher 12y agotl;dv: - real ObjC compiler (clang) + runtime (unspecified) - "modern" ObjC with ARC + Blocks - C++ interop access to all Windows APIs - C# integration "coming" - Apps are full windows apps - subset of iOS APIs - OpenGL/ANGLE/CAEAGLLayer/EAGLContext, OpenAL, Sensor - UIKit, CoreAnimation, CoreGraphics CoreText, "Touch" - Nibs, Storyboards and Autolayout are supported They don't claim or shoot for complete coverage or compatibility with a specific iOS version. Swift is not there, dev said "coming", suit said "we have no comment" (the interaction between the young and slightly insecure program manager and the old and very comfortable dev. was fun to watch). Project conversion is one-way and apparently one-time, which could be an issue. Dev immediately said "why not two-way, hey, that's a good idea, we'll do that". I think the suit was only half joking when he asked for the dev's mike to be cut... I didn't quite get the philosophical musings about code generation. Huh? Coroutines for C++ also looked quite neat, very light-weight/fast implementation (~cost of a function call).
- ossreality 12y agoYou're doing the lord's work.
- copx 12y ago> - real ObjC compiler (clang) + runtime (unspecified) It seems Microsoft actually wrote their own Objective-C runtime. I mean otherwise the guy would have said "we ported Apple's runtime" or something like that. But he said "We are providing you with a great Objective-C runtime." Crazy times. EDIT: Definitely a new runtime written by Microsoft. The rest of the talk made that clear.
- wsc981 12y agoCrazy and awesome. From what I've seen it should be possible to create a fully-featured WinPhone app now with Objective-C code. Microsoft claims that they've ported a lot of the API's including the most important API's for gaming (OpenGL, OpenAL, etc...) but also (and this surprised me) CoreGraphics, CoreAnimation and (a large part of) UIKit and Foundation (must have been a crazy amount of work). Microsoft looked at the API's that are most used by developers and implemented those first, but they will add more API's in the future. A lot of stuff, like local notifications is directly mapped to WinPhone toasts. But at the same time you can directly use WinPhone API's from Objective-C, if you choose to. And you can develop all using Visual Studio. This will be really interesting and fun.
- discohead 12y agoI was really hoping to see more support for OS X API's, personally I'm a lot more interested in porting my Mac desktop app to Windows desktop than any iOS project.
- coldtea 12y agoI don't think they are interested in OS X APIs at all. It's not as if Windows doesn't have tons of native apps in the first place. What they want is to offer a way to get the million of iOS apps into Windows Phone.
- discohead 12y agoAgreed, sadly.
- itistoday2 12y agoMicrosoft would be stupid to not offer to port Cocoa apps. How else are they supposed to convince developers such as myself to even consider buying a PC? With Apple dropping the ball with Yosemite, the opportunity is ripe for Microsoft to compete for quality devs and quality apps.
- coldtea 12y agoThis sounds like reasoning from some parallel universe to me. First, Apple hasn't dropped any ball with Yosemite. It's it's as good as it ever was. People have been complaining for every major release since 10.2 how the OS gotten more buggier, etc. Then a couple of point updates come and fix any major new bugs and the stop. Then, sometime around 10.x.6-8 a new version is relased and then they complain for the next release and remember the old one fodly. I have articles and blog posts with similar complaints from 10.5 and 10.7 and 10.8 and 10.9 with the same pattern. Even for 10.6, which was mostly a no-new-features release. Second, even if they had, there's not much value in "offering to port Cocoa apps". Major apps are already cross platform (from Adobe stuff and Eclipse/Idea, to Cubase, Sublime Text and Mathematica, including Office, which MS itselfs makes anyway), and smaller Mac-Only apps don't have much to offer to Windows users, and wouldn't be much outside of the Mac ecosystem anyway. You'd get what, Pixelmator and BBEdit? There are 4-5 established alternatives in Windows for each piece of Mac software.
- mrdrozdov 12y agoI watch this and I can't help thinking, "Apple has won".
- wvenable 12y agoExactly. They won a few years ago. At first Microsoft tried to copy exactly what Apple was doing and that didn't work. Now they're at least trying to compete with Apple in a way that leverages their advantages.
- alyx 12y agoYou don't need to watch this video to know that Apple has won. But what do you expect, everybody to pack up and go home? I'm glad they are trying something/everything in order to bootstrap Windows. Innovation happens when people are competing and fighting for the user's attention. Not when they are rolling in cash with no desire to do anything new.
- kevingadd 12y agoI think the reality is even more interesting than that: Apple has won, but MS is in the position of being able to do whatever they want, so they can chase after any developer audience they're looking to capture. Thus, they're adding clang integration, and an objective c runtime, and a way to run 'universal' windows 10 apps on xbox one, a rearchitected browser with modern js (asm.js!) and modern platform features (webgl!) etc etc etc. They just want devs to put their applications on Microsoft platforms, they're letting go of the desire to control every part of the platform & developer experience. Compare this with how Apple has been aggressively pruning and scoping down their dev tooling, it's a pretty interesting contrast. They insist on controlling everything from beginning to end, which results in problems like not being able to build executables that support older versions of OSX with the official toolchain.
- malkia 12y agoSomeone has been porting my porridge!
- bananaboy 12y agoThat talk is interesting and it's be great to be able to build for iOS in VS, but other information that seems to be coming out around this is very confusing. This[1] blog post links to this MSDN article[2] which says "You can use Visual C++ for Cross-Platform Mobile Development to edit, debug and deploy iOS code to the iOS Simulator or to an iOS device, but because of licensing restrictions, the code must be built remotely on a Mac.". [1] http://blogs.msdn.com/b/vcblog/archive/2015/04/29/what-s-new-with-c-cross-platform-development-with-vs-2015-rc.aspx http://blogs.msdn.com/b/vcblog/archive/2015/04/29/what-s-new... [2] https://msdn.microsoft.com/library/dn707598%28v=vs.140%29.aspx?f=255&MSPPError=-2147217396 https://msdn.microsoft.com/library/dn707598%28v=vs.140%29.as...
- bananaboy 12y agoAhh, after watching the entire talk now I get it. So this Obj-C+libraries is for bringing Obj-C apps to Windows, not really for building apps targeted at iOS.