I have bundled a framework/SDK from Philips Hue written in Objective-C into my Swift project. The code of the SDK is well in-line documented. Thus, I have fired up appledoc and created a custom docset: appledoc --project-name HueSDK --project-company Philips --install-docset ..
The target was to implement it directly into Xcode's Documentation window:
I have realized that this is not working anymore in Xcode 10, whereas reports show that it was working for older Xcode versions (<8). This is quite a pity as Xcode very often directs the user to the Documentation window, e.g. clicking on a link within the Quick Help Inspector:
Do you know any possibility how to integrate custom Docsets into Xcode's Documentation window?
Related
My app Plumb-Bob is based on the IKImageViewDemo:
https://developer.apple.com/library/archive/samplecode/IKImageViewDemo/Introduction/Intro.html#//apple_ref/doc/uid/DTS10004049
I compile it for MacOS 10.10+ and in my tests I noticed that the "move tool" is not working at all in Mojave (10.14) while it does as usual in the previous systems.
Since I have strongly modified IKImageViewDemo for my purposes, I have downloaded it again to make some test (see link above).
When build and run IKImageViewDemo I have verified that it has the same behavior:
On MacOS 10.14 the move tool shows its open hand cursor, but, when dragging, the image is not moved at all.
On older MacOS, it works like a charm.
I did not find any updates, deprecations and changes on IKImageView framework in 10.14, searching at Apple Developer's docs.
Can anyone address me to the solution, it is very important, in my app, to move around the zoomed image.
Thank you in advance
I have an iOS app which I need to build a supporting app for macOS. I was hoping to share code between them, specially the DataModel.
As the iOS app was using Pods, there was already a workspace.
I pulled in the macOS project into the workspace, and I can see all its files with no problem. But I don't seem to be able to figure out how to 'use' the class files from the iOS project in the macOS project. Would it have anything to do with Modules?
Or should I just make a new Target that is a macOS application?
I'm using Xcode 8.3.3 at the moment, and the projects are in Swift.
Select the source files you want to use and tick the "Target Membership" for your macOS target in the Inspector:
Update:
To use common code in different projects, make an extra project for your common code which builds as a Framework and include this framework in the iOS and in the macOS.
This tutorial might be helpful.
There appear to be lots of people having issues since Apple's updates to support Universal Frameworks in their latest release. We have been using Universal Frameworks for quite some time. Of course, the update broke our Universal Frameworks and I have been trying to figure out how to get them to work again. I have looked at a few questions and found this one to be exceptionally helpful. There appears to be some confusion regarding whether scripts are still needed. I found some instructions here that say the new scripts are python scripts instead of shell scripts. But even with the information I have found out there, I am still confused.
Can anyone give me clear consise steps to convert an existing Universal Framework into one that compiles and builds in Xcode 6?
We are also facing similar issue when we upgraded to xcode6 and haven't found any solution so we decided to use apple ios custom cocoa touch framework .Below is the tutorial for building frameworks using xcode 6.
http://rescueprogramming.blogspot.com/2014/11/how-to-create-custom-cocoa-touch.html
We have written up a step by step guide on how to implement and integrate Xcode Frameworks that describes:
1) How to create an Xcode 6 Cocoa Touch Framework.
2) How to create a dependent Xcode 6 Cocoa Touch Framework.
3) How to Integrate your working Xcode 6 Frameworks and dependent Frameworks into an iOS application.
This step-by-step instruction guide can be found here:
https://kodmunki.wordpress.com/2014/11/07/universal-cocoa-touch-frameworks-for-ios-8/
I have been developing an app using Xcode, which included the Facebook SDK. The Facebook SDK requires the AdSupport.framework and the Social.framework, both of which were previously installed, but seem to have disappeared. My question is how do it update the library to 6.0, instead of five? I understand that you have to go into the build phases and add the frameworks in the Line Binary With Libraries section, but when I go to add the framework, the folder is 5.1, not six. I have looked through the Apple doc's and haven't found anything.
Here is an image of what I'm getting:
It should look like this:
There should be no way the SDKs provided with Xcode can regress. However you could see them vanish if you launch an older version of Xcode.
Based on experience, if you had Xcode installed before it was a single app bundle and have subsequently installed the app bundle version then there's a reasonable probability the old version is still present and therefore good odds that a Spotlight launch will open the wrong one.
I got a application from my teammate, and it is for both iphone and ipad devices (which it is developed under iPhone SDK 3.2).
I have iPhone SDK 3.1.3 installed in my mac book. When i tried to compile the application for iphone simulator i got the following error.
Interface builder is unable to open documents of type iPad XIB.
The above error is for interface builder created for ipad.
My Question is we can't compile the application on iPhone SDK 3.1.3 which the application developed under iPhone SDK 3.2?
Please shed some light of this?
thanks
mindus
Go to your project settings, and delete the line that says Interface Builder Plugin search path or something similar.
the exact line in project.pbxproj is: IBC_PLUGIN_SEARCH_PATHS = "${PROJECT_DIR}/**";
Short answer
Temporarily remove the iPad xib when working with the 3.1.3 SDK. Put them back when you go back to 3.2 and above.
Longer answer
This cropped up for me when compiling against 3.1.3. You can use conditional compiling to get code user newer features to build successfully (see Matt Gallagher's helpful post on conditional compiling).
There may be a smarter way to tell the compiler not to look at the iPad xibs. For testing on the 3.1.3 simulator I simply made a copy all my iPad xibs and then removed them from the xcode project. When going back to my current development set up, you have to put them back. It's a bit of pain, but not that fiddly.
To fix this:
Press Command-1 to go to the project tree
Select your project
The in the right panel select your project, and then click on "Build Settings"
In search field just below the "Build Settings" enter: "Overriding Plug-In"
Now, the only visible setting left should say "Overriding Plug-In and Framework Directory"
Double-click the value and remove all entries using "-" button
Click somewhere else so settings are saved
That should fix it