Community
Participate
Working Groups
Created attachment 244140 [details] patch with iOS documentaton update The patch include the documentation for CocoaPods and some other adjustments of UserManual regarding ios testing: * ios AUT cannot be used with autrun * XCode 5 is assumed to be in use, so creating Testing Target description have been changed * fix of the Bug 436702 is added ...
This needs to be reviewed on a technical level first. Then I'll review it on an English level and commit it.
I'm not the perfect person doing a technical review here - I've myself only briefly worked with this mechanism. I'd recommend TKi to take a look at the technical details the CocoaPods integration documentation (as he's also the person who did it). Nevertheless I took a brief glance at the patch and noticed the following: - there are again "empty" line changes within the patch (e.g. spaces, ...) - whenever there is a path to replace I'd mark it in the normal <setThisPathExplicitlyByHand> way (line 70 of the setup.tex) For information how to apply this patch maintaining the correct author information please talk to me after reviewing it on an English level.
CTRL+click *or right click* the target and choose ”Duplicate” entry of the context menu! ------ You can also (optionally) rename the new target from the default MyApp copy to something more meaningful e.g. MyApp (GUIdancer or Jubula Tests) by selecting the ”Build Settings” tab and searching for ”Product Name”, then changing the value to a new name. 1. We can change the target name by 1 click on the target. 2. With changing the "Product name" we change the name of the app. If the "Bundle display name" in the <appname>-Info.plist is ${PRODUCT_NAME}. Suggestion: Maybe the new name of the "Product name" in build settings can be ${TARGET_NAME}, because if we change the target name it will change the product name also. ------ The first step is to link the librc.mobile.ios.nativ static library and its header file directly into your iOS application. I think we can name the header file: UIRemoteControl.h The first step is to link/add the librc.mobile.ios.nativ static library and UIRemoteControl.h file directly into your iOS application. ------ In the sheet that appears, select CFNetwork.framework and SenTestingKit.framework and click ”Add”. For iOS7 we should add XCTest.framework also ----- You also have to make sure that your application delegate provides a UIWindow property called window which contains the window used to present the app’s visual content on the device’s main screen. ... #if RUN_FUNCTIONAL_TESTS @property(nonatomic, retain) UIWindow *window #endif This is not necessary at all. “UIWindow* window” variable will created automatically when we create a new project. And it is a wrong use case to take it inside #if RUN_FUNCTIONAL_TESTS statement, because we can need it not just for testing. ----- you need a specification that describes a version of the installed Pod library - a .podspec file It describes a lot of other things, not just the version: “A specification describes a version of Pod library. It includes details about where the source should be fetched from, what files to use, the build settings to apply, and other general metadata such as its name, version, and description.” ----- pod ’rcmobile’, :path => ’iOS-support-path’ iOS-support-path: the path where are the rcmobile.podspec is. pod ’rcmobile-debug’, :path => ’sources-path’ sources-path: the path where are the rcmobile-debug.podspec is.
Created attachment 244831 [details] Update of iOS doc uncluding CocoaPods information Thanks Tamas! I updated the patch regarding your suggestions. I´ve just found small change: we have to use double click on the target to change its name instead of 1 click.
Alex, could you please review it on an English level?
Created attachment 244887 [details] Update of iOS doc uncluding CocoaPods information Small update that iOS-Support.zip contain only normal podspec file, because the debugging podspec have to be installed from location where sources are, so we don´t need it in iOS-support zip.
I've applied the patch with minor changes with: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=210bd5dd59cb4ba9c70aeab1e67669a627f3b7f6
I've verified that the documentation has been updated with the additional CocoaPods information.
