How to open interface builder in Xcode 4? - ios

I am following a book tutorial to create a iPhone application.
But I am stuck at the step where it say click on a certain file .xib I think to open up the interface builder. Can anyone advise me where to ind that file?
Another question is that I notice apple will add my project codes to git repository. I think this is good but how do I use git related commands in xcode?

If the .xib file is in your project, you should be able to find it in the project explorer (press CMD-1 to open the project explorer if it is not already open); (example picture)
If it is not in your project, it may be close to the files in your project, so right-click a file in the project explorer, and select "Show in Finder". You can then hunt around for a .xib file.
If you cannot find it, it is possible that the tutorial wants you to create one, in which case
CMD-N will open the "create file" dialog, and you can select the appropriate template under "user interface", all of which will create .xib files.
To commit files with git, right-click on files that you wish to commit to the repository, navigate down to "Source Control", and select "Commit Selected Files". Here is the official Apple git+xcode reference guide which you may find useful.

Related

How to Integrate Kal Calendar?

I am fairly new to iOS development, and have a project in mind that would benefit from a third-party calendar interface. However, I'm having trouble just getting started. Feeling a little disappointed as well because I have searched high and low and it seems everyone is capable of integrating Kal Calendar itself, and that is where I am stuck.
I have downloaded the .zip source here and am trying to follow the steps. The first three are as follows:
Clone the Kal git repository: git clone git://github.com/klazuka/Kal.git. Make sure you store the repository in a permanent place because Xcode will need to reference the files every time you compile your project.
Locate the "Kal.xcodeproj" file under Kal/src/. Drag Kal.xcodeproj and drop it onto the root of your Xcode project's "Groups and Files" sidebar. A dialog will appear -- make sure "Copy items" is unchecked and "Reference Type" is "Relative to Project" before clicking "Add".
Now you need to link the Kal static library to your project. Select the Kal.xcodeproj file that you just added to the sidebar. Under the "Details" table, you will see libKal.a. Check the checkbox on the far right for this file. This will tell Xcode to link against Kal when building your app.
I have dragged the Kal.xcodeproj file from Finder into the root of my project in the Project Navigator as seen in this image:
Is this the correct place to drop the Kal.xcodeproj file? I was not presented with a dialog upon doing so. What is the "Groups and Files" sidebar? Upon selecting the Kal.xcodeproj file from where I have placed it, I cannot find a "Details" table where a libKal.a file is located.
Again, my apologies as I am fairly new to iOS dev, and I completely understand that these could be the most amateur questions out there. If anyone can point me in the right direction it would be greatly appreciated. Just looking for some help getting started so I can finally begin my project.
By the way, I'm using Xcode 6.
Thanks in advance!

Adding a Supporting File to xcode project

I am new to xcode, and development in general. Following a tutorial that tells me to add "file.plist as a supporting file to the project."
Does this just mean add a file to the project? I placed it into a folder (BT_Config) that has the another .plist file in it already). Not knowing anything about my project, does that sound right?
I can't find a clear google reference to "xcode supporting files" - so i'm not sure.
Any suggestions?
You need to add it to your Xcode project. Xcode will then copy it into the file system folder if needed. Just open your project in Xcode and drag your file into the left sidebar. It doesn't matter where you drop it, but supporting files are usually added to the 'Supporting files' group.
If you want to create a new file, just use the 'File > New > File...' item from the menu bar.

Find missing files in Xcode

I am re-arranging files in my file system for my Xcode projects. Therefore, when I open the Xcode project, all of the files are red.
I can add each file manually, but is there a way for Xcode to quickly find these files for me? All of the files are located in one directory.
If you have a bunch of missing (red) files that now live in the same directory, you can improve on the "fix each path individually in the inspector" method by selecting (Cmd-click) all the files at once. You'll see "multiple values" in the inspector, like so:
Clicking the button under the Location dropdown will bring up a directory selector -- note that the prompt says "Choose folder containing..." rather than "Choose file and location".
As far as I know, Xcode doesn't have a way to automatically locate moved files. You can reconnect a reference to its file using the Inspector (panel on the right) but it is somewhat tedious to do so. In your case, it would probably be faster to simply delete the references and then add the files back to your project.
I agree with the answers already given. In a real pinch, or as a last resort, you can open the project file in a text editor and fix the path references by hand.
Close the project in Xcode
Backup the project file someplace safe
In the Finder, right-click on the project file and select "Show Package Contents"
Drag project.pbxproj to BBEdit (or TextEdit or whatever)
Edit whatever "path = xxx" references you want
In this case i do this steps:
1) Add a new group with name Res
2) Click "Add Files to ..."
3) Find a folder with resources, and click CMD + A
4) Set check box on "Create folder references for any added folders".
And in source code i use e.g. "fonts/font1.xml".
5) Then for refresh, i just Removing a Res group references
6) And do steps from 1 to 4
Hope this will be a useful

move xcode project causes red text (missing files from project)

When I move iphone project directory to a new path.
There are some red texts indicate the missing files from the project source codes.
How to avoid these?
Here is how to locate the missing (red) files using the Xcode 4 interface:
Select the file or files in the left hand Project Navigator (the folder icon)
In the right sidebar click on "File Inspector" which is the leftmost icon resembling a page
In the "Identity and Type" section, there is a grey box labeled "Location".
Click on the small icon to the lower left that resembles a file browser - this will come up with a file browser to locate the file.
Voila, you are done.
Xcode 7
1.) Right click on the red (missing) file.
2.) Select "Show File Inspector"
3.) Look at the right hand side of the screen under "Identity and Type" between "Location" and "Full Path"
4.) Click on the folder icon to the right of the file name.
5.) Navigate to the file's new location in the pop-up window and select the file.
I encountered this issue when copying my project from one mac to another.
The solution for me:
assuming your files are grouped (in folder)
from xcode open the group in file inspector
The group will probably be missing the absolute path.
press the little icon nearby to pick the folder to associate the group with.
restart xcode to see the changes.
I had the same problem, when I changed the permission on the files/folders to everyone read/write they then appeared in Xcode.
This worked on a Pod project. Quit XCode.
rm -rf project.xcworkspace/xcuserdata/*
Restart XCode and reopen project.
In Finder, create a duplicate of the project directory just in case all goes squiffy.
In Finder, open the project directory that contains all the files with red references
For all the red files you see in XCode, except the info.plist file (see step 5 below), highlight them in Finder and drag them from Finder to XCode's project navigator. i.e. import them.
In XCode's "Choose options for adding these files" window: a) Select Copy items into Destination's group folder (if needed)
b) Select Create groups for any added folder
c) Select Add to Targets, and press Finish
Highlight and drag the info.plist file from Finder to Project Navigator and repeat step 4 WITHOUT selecting Add to Targets
If you had groups in Project Navigator (e.g. Supporting Files), reorder the files to be in the right places.
Delete the original bad red references in Project Navigator, and Cmd-Shift-K to clean for good measure.
Build and run on a device to remove the bad reference to the .app file
you just have to locate the missing file press in file icon in the identity and type you will find the full path just locate your file where do you move it click the file icon
When you create these files be sure to save in your app directory. Or if you import classes from other project be sure to check the copy option.
I dont know if this is the main reason but when you are importing files to the application, do you mary the "Copy items in to destination group's folder (if needed)" ?
this make sure the file is not only referenced but added to your project folder and ir will move any where you move your project.
Did you move files in to folders directly in your project folder and not in xcode?
This worked on a Pod project.
go into finder and project.
right click on your project .xcworkspace and click show package contents
right click on contents.xcworkspacedata and open with textEdit then make sure file path is correct. If project has been moved this can change
I also did this below but now sure if you need it
Quit XCode.
rm -rf project.xcworkspace/xcuserdata/*
Restart XCode and reopen project.
If you create an Xcode project, then move the .xcodeproj file or the newly created project folder to a different folder using Finder, subsequent builds may show many missing files which still reference the original folder locations (which no longer exist because you moved them). These missing files can appear as red text or as issues in the Issue Navigator.
This can happen when Xcode is configured to automatically add or remove files to/from source control (under Xcode > Preferences > Source Control). When configured this way, simply creating a project in Xcode causes new project folders and files to be marked for addition to source control. When you later move the project folder or .xcodeproj file these pending adds now point to missing files.
To resolve this issue when Subversion is the source control program, revert the pending adds for the phantom items from your local working copy folder. In my case this requires dropping into a Terminal window, navigating to the parent of the phantom project folder, then reverting the automatic add, e.g.
cd /my-working-copy-folder
svn status --depth infinity
svn status --depth infinity existing-parent-folder/phantom-project-folder/
svn revert --depth infinity existing-parent-folder/phantom-project-folder/
Note that the first svn status command will list both missing files as well as properly added, modified or deleted files which you must take care to avoid reverting. The second status command is "practice" for the final revert command, to ensure you've specified the proper path to revert.
I do not know git but I assume it offers corresponding commands.
It's too simple to do :
Close the project that includes the missed files and open the Xcode, go to "Organizer">"Projects" and remove the project from the list there. Open your project from Finder and that's it.
hope this help.

How to open a c project in source insight?

Someone recommends me to use SI to read the c source of PHP ,a great open source project.
I've already downloaded the source.
But I don't know how to import it,can anyone help?
Open the Project menu and create a new project (or push Alt+Shift+N). In the upcoming dialog window, enter PHP as the project's name and select a folder to store the project data. Click OK to configure the project, e.g. activate storing function-local symbols in the project DB etc. Click OK again.
The next dialog lets you actually import files to the project. Select your source folder and click "Add Tree" to add the whole directory structure to the project. Click Close. You can now start browsing the source code.
Make sure you configure SourceInsight so that it knows where your local library folders are, i.e. the C headers & runtime. This is usually done when installing SourceInsight.

Resources