Usually when you create a new Xcode Project you can choose to setup a new Git repository. This is the best and easiest way to track your changes. However if you have a project that is not under version control you can create a Git repository retrospectively.
This is fairly straightforward using the Terminal app on your Mac (under Applications / Utilities):
- cd into the directory where your project resides
- then initialize an empty repository (git init)
- and add the entire directory to it (git add .)
- commit your changes (git commit -m “initial commit)
So far so good. However Mac has a hidden directory called .DS_Store in every directory – we may not want to track that. Plus, every time you make a minor UI change in Xcode (such as open a group in the file explorer or something that is not relevant to your actual code) Xcode tracks this change in a file called UserInterfaceState.xcuserstate, and we definitely do NOT want to track that.
To tell Git that we don’t want those two things, we’ll amend our previous instructions a bit:
- cd into the directory where you project resides
- create a file called .gitignore
- add each file or directory on a new line
- then create, add and commit your files to Git
Let’s assume my project is called MyProject, then the steps are as follows:
(add the following lines to that file)
# ignore these files
(save and exit vi by pressing SHIFT-Z-Z)
git add .
git commit -m "initial commit, omitting several files"
If you have already committed all your files and forgot to setup the .gitignore file you must manually remove the files/directories you don’t want from being tracked. This is how you’d do that:
git rm --cached .DS_Store
git rm --cached # ignore these files
git commit -m "removing files I no longer want"
Replace myusername with your own system user name obviously, and MyProject with the actual folder in which your project resides.
If you don’t want your cell to be highlighted you can de-select the option “User Interaction Enabled” in the storyboard. This is ticked by default. Untick it and nobody can select your cell anymore.
First we make the cell’s background transparent. Next we create a custom view which we can show behind the cell, like so:
cell.backgroundColor = [UIColor clearColor];
UIView *backView = [[UIView alloc]initWithFrame:CGRectZero];
backView.backgroundColor = [UIColor clearColor];
cell.backgroundView = backView;
You can conveniently rename an app you’ve started. For this example, we have a project called Old Project, created from the Master/Detail Template.
Three areas need to be changed here:
- the actual app name and targets
- the scheme
- the group in which most project files reside
Renaming the app
Click on the blue Project, wait a second, then click on it again. The field will change just like in Finder, so you can type in your new app title. Once you hit return it will open a new dialogue box which will tweak some other files, most notably any existing targets, the bundle identifier (if it was set to automatic) and the app’s displayed name.
A couple of things still have the old name, so let’s fix that next.
Renaming the scheme
The scheme is displayed at the top next to the run and compile button. Click the left part of the drop-down menu and a context menu will appear, showing Manage Schemes. Don’t click on the right part (where it says iOS Device or iOS Simulator) as this will only let you pick which device you’d like to run the app on, not which scheme you’d like to use.
And just like before, click on the old app name, wait a second, then click again to change it to your new app title. If you have multiple schemes you can rename them all before hitting OK.
Renaming the file group
This is more of a cosmetic thing: on the left hand side you will still have a group which contains most of your project files. These are not really folders, they are just convenient groups to keep a large amount of files in places where you can find them within a project. Again click on that group, wait a moment, then click again and rename it like a folder or file in Finder.
And that’s it 😉
You can set simply set your UIBarButtonItem to nil, like so:
self.navigationItem.rightBarButtonItem = nil;
will do the trick. Shutdown happens immediately. If you do this in a live app it’s probably a good idea to let the user know and wait for a button click, or perhaps integrate a timer before the shutdown occurs.