GitXplorerGitXplorer
d

DataCenter

public
31 stars
1 forks
0 issues

Commits

List of commits on branch master.
Unverified
ffca836d680648a8e81b1e5e7bee12ccc579cd8c

Use new store options and model configuration methods

ddanielctull committed 12 years ago
Unverified
c03d30fc715644a9668652356ed71989fe3b9691

Share schemes

ddanielctull committed 12 years ago
Unverified
753491219dd85b5ba0adf3a0fc655c821fa5d2c1

Remove old app delegate

ddanielctull committed 12 years ago
Unverified
8f1b14c496024d7221918295570da0ffed4e5ec9

Remove unused submodules

ddanielctull committed 12 years ago
Unverified
90aa2f988d52f9f9b3c441ebdafe81fc7ef47b74

Rename the nice description category

ddanielctull committed 12 years ago
Unverified
7d4b3cac72d807a41609216107a1cf842d971707

Update SampleCoreData and use DCTCoreDataStack for demo

ddanielctull committed 12 years ago

README

The README file for this repository.

h1. DataCenter

DataCenter is a collection of classes that allow you to explore the data stored in a Core Data managed object context.

Including these in your app during debugging and testing phases will allow you to explore the data if anything seems awry. It's pretty basic at the moment.

!http://danieltull.co.uk/DataCenter/screenshots/datacenter.png! !http://danieltull.co.uk/DataCenter/screenshots/person.png!

h2. Branch Structure

There are two branches to this repository, master and production, these are described below. (Thanks to "Abizer":https://github.com/Abizern for showing me this method and for his initial writeup below.)

h3. The master Branch

The master branch contains the class extension files as well as an Xcode project that demonstrates the code and is the branch to use to see how to use the code. It as also the branch that further development of the code should be performed on.

h3. The production Branch

The production branch should be used if you want to add these extensions as a git submodule in other projects and will only contain the class files themselves without the Xcode project or example classes. This is preferable as it will keep your directories clean of any code which is unnecessary to your working project, of course you can switch branches in the submodule to access the given samples.

Changes made to the master branch will be merged across to production, so it will always remain current with respect to master.

To add the production branch rather than master, simply use the -b flag as shown below.

bc. git submodule add -b production git://github.com/danielctull/DataCenter.git

To keep up to date with the latest changes cd into the directory that contains this submodule and pull the newest changes as usual

bc. git pull origin

h3. Artefacts

Sometimes, there may be artefacts left over when switching from master to production. These are files that are ignored by git and are easily cleaned up by running

bc. git clean -dxf

h2. License

Copyright (C) 2010 Daniel Tull. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

  • Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.