TweetFollow Us on Twitter

Advanced CVS

Volume Number: 24
Issue Number: 11
Column Tag: Code

Advanced CVS

Get more out of your CVS Setup

by José R.C. Cruz

Introduction

In the article "Version Control on a Budget", we learned how to use the CVS tool to manage our project files. Today, we will explore some of the tool's advanced features.

First, we will configure the tool on either the client or server side. Then we will use the tool to keep track of project activity. Finally, we use the tool to manage the project repository.

Be aware that this article assumes that you have a basic understanding of CVS and bash.

Configuring CVS

You can configure your CVS setup in two ways. One way is to add an invisible file in your home directory. This file, called a run—control file, tells the tool how to handle each SCM transaction. Users can have their own unique run—control files, or they can share a common set of files.

Another way is to change one of the files in the CVSROOT directory. To access those files, type the following statement at the Terminal prompt.

   cvs checkout CVSROOT

CVS then copies the CVSROOT files and stores them on the current work directory. After you made your changes, commit them back to the repository as follows.

   cvs commit —m "Made changes to the CVSROOT files" CVSROOT

First, CVS updates its CVSROOT directory with all your changes. It then applies your changes to all future commands. If you, however, changed a single file, e.g. modules, you can commit just that file as follows.

   cvs commit —m "Made changes to the CVSROOT file 'modules'" modules

Backing up CVSROOT

Before changing any of the CVSROOT files, make sure to create a backup of those files. This will protect your CVS setup from any errors caused by your changes. One way to backup CVSROOT is to use the tar tool.

Assume, for example, that your CVSROOT directory is stored in /Volumes/Projects/Database. Assume also that you want to store the tarball in /Volumes/Backup. To create the CVSROOT tarball, type the following at the Terminal prompt.

   tar —create —verbose —gzip —file /Volumes/Backups/CVSROOT.tar.gz \
      /Volumes/Database/CVSROOT/*

First, the tar tool copies all the files in the CVSROOT directory. It then stores the copies in the tarball CVSROOT.tar.gz. It also compresses the tarball with the gzip tool.

Now if you made a mistake configuring your CVS setup, type the following statement at the Terminal prompt.

   tar extract —gzip —file /Volumes/Backups/CVSROOT.tar.gz \
      —directory /

The tar tool then updates your CVSROOT directory with the contents of the tarball CVSROOT.tar.gz.

The .cvsignore file

Use the .cvsignore file to tell CVS which project file to exclude from its repository. CVS checks this file each time it gets an import or an update subcommand. Use your favorite text editor to create this file on your home directory. Make sure to precede the file's name with a period, '.'.

Each line in the .cvsignore file is either a filename or a glob pattern. Glob patterns work in the same way as regex patterns, but they have a simpler syntax.

Listing 1 is a sample of entries in a .cvsignore file. The first entry matches the invisible file .DS_Store. The second matches any file with a .dbug extension. And the third matches any HTML files that have the name foobar or foobur.

Listing 1. Example of a .cvsignore file.

   .DS_Store
   *.dbug
   foob[au]r.htm

Before you install your .cvsignore file, be aware that CVS already excludes certain file types by default. A sample of these file types are as follows.

*.a *.bak *.BAK *.exe *.o *.obj *.old *.orig

For a complete list of excluded file types, consult the online CVS manual (see reference).

Finally, you can tell CVS to disable your .cvsignore file for certain tasks. To do so, add the —I ! option to your import or update subcommand (note the '!' character). This option disables not only your .cvsignore file but also the default list of file types that CVS ignores.

The .cvsrc file

Use the .cvsrc file to set the default options for either the CVS tool or any of its subcommands. Like the .cvsignore file, the .cvsrc file also goes into your home directory. Use your favorite text editor to create this file.

Each line in the .cvsrc file has the following syntax.

   cvs | subcommand option [option]

If the leftmost item is a subcommand, the option argument is one of the option flags used only by that subcommand. But if the leftmost item is CVS itself, the option argument is one of the global options available to that tool. Those options apply to all CVS transactions. Read the online CVS manual (see reference) for a list of available options.

Listing 2 is a sample of entries in a .cvsrc file. In the first line, the —r option tells CVS to set the states of the project files as read—only. The —q option tells it to keep its feedback messages to the bare minimum.

In the second line, the —f option tells CVS to allow committals even if none of the project files have changed. In the third line, the —f option tells CVS to always export the head revision. The —P option tells the tool to remove any empty directories from the exported project.

Listing 2. Example of a .cvsrc file.

   cvs —r —q
   commit —f
   export —f —P

Any changes you made to the .cvsrc file are used by the next CVS command. You can, however, tell CVS to ignore the .cvsrc file for certain tasks. To do so, use the —f global option.

Assume, for example, you are using the .cvsrc file shown in Listing 2. To commit only those files that you have changed in project foobar, type the following statement.

   cvs f commit foobar

Do not add the —f global option to the .cvsrc file. This is an unsupported setting and can result in aberrant behavior.

The cvswrappers file

Use the cvswrappers file to tell CVS which project files are text files and which are binary files. Use it also to tell CVS how to store each file type in the repository. There are two versions of this file: one in the CVSROOT directory, the other in the home directory. The name for the home directory version is .cvswrappers.

Each line in the cvswrappers file has the following syntax.

file_name | glob_pattern    option mode [option mode]

The line starts with a filename or a glob pattern. The option argument sets the storage option for that file, the mode argument the storage mode. Each line can have at most two sets of these arguments.

For a binary file, e.g. TIFF, add the following entry to the cvswrappers file.

   *.{tif,tiff} —k 'b'   —m COPY

The above entry matches any file that has a .tif or .tiff extension. It tells CVS not to convert any end—of—line characters in the file. It also tells CVS to always store a copy of that file intact in the repository.

For a non—mergeable text file, e.g. a UTF—16 file, use the same option and modes as the binary file. This is to compensate for CVS's lack of support for Unicode—based files.

For a mergeable text file, e.g. C—headers and sources, add the following entry to the cvswrappers file.

   *.{c,h}    —m MERGE

The above entry matches any file that has a .c or .h extension. If the repository has a copy of that file, CVS stores only the differences between the two. Otherwise, CVS will store an intact copy of the text file.

Now if you have two versions of the cvswrappers file present, CVS will use the entries from both files as one. If both versions of the file have entries for the same filename or glob pattern, CVS will use the entry from the CVSROOT/cvswrappers.

Finally, you can override the entries in both cvswrappers files by adding a —k option to your CVS statement. Read the online CVS manual (see reference) to learn which subcommand uses the —k option.

The modules file

Use the modules file to set shortcuts to specific projects or items in the repository. Shortcuts reduce the amount of typing needed. They are also easier to remember if chosen correctly.

Each line in the modules file has the following syntax.

shortcut    [options]    repository_path

The options argument defines how the shortcut will work. It has one of two possible values: —a for an alias and —d for a directory. The repository_path argument is the path to the item or project in the repository.

Listing 3 is a sample of shortcuts in a modules file. The first shortcut tells CVS to retrieve the items in project foobar. Also, CVS saves those items under the directory MyFoo.

The second shortcut tells CVS to retrieve only the items in the graphics directory of project foobar. The —a option then tells the tool to save those items under the same directory of foobar/graphics.

The third shortcut tells CVS to retrieve the items in project foobar. But the '!' token tells it to exclude those items in the directory foobar/graphics. Again, the —a option tells the tool to save the retrieved items in the directory foobar.

The fourth shortcut tells CVS to retrieve the project items referred to by the shortcut NoPics. Note the ampersand symbol, '&', in front of the referring shortcut.

The fifth shortcut tells CVS to retrieve the items in project foobar. Also, the —d option tells the tool to store those items under the directory Test/foobar.

Finally, the sixth shortcut tells CVS to retrieve only the file foobar.css. And the —a option tells the tool to save the file in the directory foobar/styles.

Listing 3. Example of a modules file.

   MyFoo             foobar
   MyPics       —a    foobar/graphics
   NoPics       —a    !foobar/graphics    foobar/
   PicFree          &NoPics
   MySite       —d    Test    foobar
   MyStyles    —a    foobar/styles/foobar.css

Tracking Project Activity

Tracking project activity is an important part of the work cycle. It helps identify which files got the most attention and those that got the least. It helps measure the number of changes made to each file. Tracking also shows which users worked on which files, and the time spent on each file. It can also help users coordinate their efforts and avoid possible conflicts.

Tracking file activity

Use the cvs log command to list the changes made to the project or file. For example, to list all the changes to the file foobar.htm, type the command as follows.

   cvs log foobar.htm

CVS then displays the list on the Terminal window. To save the list of changes into a file, e.g. foobar.log, use the '>' operator.

   cvs log foobar.htm > foobar.log

You can restrict the list to a specific date or revision range. To restrict it by date, use the d option. For example, to show only changes made between 2007 Aug 1 and 2007 Sep 1, type the command as follows.

   cvs log —d"2007/08/01<2007/09/01" foobar

Notice that there is no space between the —d option and the date range. Also, notice the use of the '<' token to specify an exclusive range. For an inclusive date range, retype the command with a '<=' token.

   cvs log —d"2007/08/01<=2007/09/01" foobar

To restrict the range by revision number, use the —r option. For example, to show only the changes made between revisions 1.2 and 1.5, type the command as follows.

   cvs log —r1.2:1.5 foobar

Notice again that there is no space between the option and the range. Notice also the use of the ':' token to specify an inclusive range.

To learn other useful log options, read the online CVS manual (see reference).

Figure 1 is a sample output from the cvs log command. The header section tells us where the project file is located on the repository. It tells us what tags belong to the file (gold), and the revision count (red). It also shows a short description of the file (green), if one is available.

Right after the header is a list of changes made to the file. Each entry starts with the revision number and date of the change (green). It shows the user who made the change (blue), the file's current state (red), and the number of lines that changed (pink).


Figure 1. Sample output of the cvs log command

The output of the cvs log command, however, is not customizable. Creating it is a separate step, making it prone to neglect. It can also be changed either by accident or by intent.

But you can have CVS create the log output automatically. You can customize the output to suite your needs. You can also make the output a part of your project file, thus serving as a version history for that file. You can do all these by using revision keywords.

Table 1 is a list of common revision keywords. To use these keywords, add them within a comments block. Doing so will tell the file's owner to ignore the keywords. Also, when you commit the file to the repository, CVS updates each keyword with the right information.

Table 1. A list of useful revision keywords.

Keyword Description

$Author$ Name of the last user who made the change

$Date$ Date when the change was made

$Header$ Basic header information

$Log$ A description of changes made to the file

$State$ State of the file when the change was made

$Source$ Location of the project file in the repository

$Revision$ Revision number assigned to the file

Listing 5 is a sample revision block for an HTML file. Notice the block is placed between the comment marks <!— —>. Assume you added this block to the file foobar.htm. Then you committed the file by typing the following command.

   cvs commit —m "Added the revision history block" foobar.htm

Listing 5. A sample revision block.

   <!— 
      $Source$
      $Author$
      $Date$
      Revision history:
         $Log$
   —>

CVS responds by first updating the revision block as shown by Listing 6. It then commits the updated file to the repository. Notice that the block retains the keywords, even after the update. Also, future committals will cause CVS to insert more entries right after the $Log$ keyword.

Listing 6. The revision block after a committal.

   <!— 
      $Source: /Volumes/Projects/CVS/foobar/foobar.htm,v $
      $Author: s_hardin $
      $Date: 2007/09/11 04:30:50 $
      Revision history:
         $Log: foobar.htm,v $
         Revision 1.2  2007/09/11 04:30:50  s_hardin
         Added the revision history block.
   —>

Tracking user activities

Use the cvs watch command to keep track of users working on the same project. This command performs two functions. First, it sets the project file to a read—only state during a checkout or an update. Second, it adds a user to the watch list.

The basic syntax of the cvs watch command is as follows.

   cvs watch operator [file ...]

The operator argument sets the behavior of the command. It has four possible values: on, off, add, and remove. You can also list more than one file after the command.

Let us assume that you are working on project foobar with another user named h_mallow. To add the file to the watch list, use the cvs watch command with an on operator.

   cvs watch on foobar.htm

When h_mallow checks out a copy of the file, he will find the file in a read—only state. To remove the file from the watch list, use the command with an off operator.

   cvs watch off foobar.htm

Since you placed the file on the watch list, you should inform h_mallow that you are watching that file. To do so, use the cvs watch command with an add operator.

   cvs watch add foobar.htm

To remove yourself from the list, use the command with a remove operator.

   cvs watch remove foobar.htm

To get a list of other users watching the file, use the cvs watchers command.

   cvs watchers foobar.htm

Listing 7 shows a sample output of the above command.

Listing 7. Sample output of the cvs watchers command.

   foobar.css      h_mallow edit    unedit  commit
   foobar.htm      youRhere edit    unedit  commit

Now assume that user h_mallow added the file foobar.css to the watch list. When you checked out that file, you will find it set to a read—only state. If you want to change the file, first use the cvs edit command to change its state to read/write.

   cvs edit foobar.css

When user h_mallow types the cvs watchers command, he gets the following list of users.

   foobar.css      h_mallow edit    unedit  commit
      youRhere tedit   tunedit tcommit
   foobar.htm      youRhere edit    unedit  commit

He then sees that you have started work on the foobar.css file.

Once you have made your changes to foobar.css, use the cvs unedit command to set the file's state back to read—only.

   cvs unedit foobar.css

Committing your changes to the repository will also do the same thing. And both actions will remove you from the watch list.

Managing The Repository

Sometimes, you want to make minor changes to your project repository. You may want to set tags to specific project revisions. Or you may want to generate a patch for a specific project file.

CVS gives you the means to make these changes directly on the repository. But be aware that you could easily mess up the repository as well. Make sure to create a backup of your repository beforehand. Also, make sure to allow only a small group of trusted users to change the repository itself.

Managing tags

Now, you use the cvs tag command to assign a tag to a file or project from your working copy. To do the same directly on the repository, use the cvs rtag command. Unlike the former, you do not need a working copy of the project to use this command.

The basic syntax of the cvs rtag command is as follows.

   cvs rtag [options] tag file | directory | project

This command shares many of the same options as the cvs tag command. For example, that you are managing the project foobar. To set the tag alpha1 to the latest revision of the file foobar.htm, type the command as follows.

   cvs rtag alpha1 foobar.htm

To set the same tag to the latest revision of project foobar, type it as follows.

   cvs rtag alpha1 foobar

Suppose a user gave the wrong tag beta1 to the latest revision of foobar.htm. To remove that tag, use the —d option.

   cvs rtag —d beta1 foobar.htm

But make sure that the tag exists before you remove it. Otherwise, CVS will return an error message. Use the cvs status command with a —v option to get a list of tags.

   cvs status —v foobar.htm

CVS then displays a list of all tags assigned to the file foobar.htm (Figure 2, gold).


Figure 2. Sample output of the cvs status —v command.

Assume you want to set the tag dev1 to revision 1.15 of foobar.htm. To do so, use the cvs rtag command with a —r option.

   cvs rtag —r 1.15 dev1 foobar.htm

If you want to set the same tag to the file foobar.css revised on 2007 Sept 01, use the —D option.

   cvs rtag —D 2007/09/01 dev1 foobar.css

Again, make sure that either revision number or date exists on the repository. If you are not sure, add a f option to the command.

   cvs rtag —f —r 1.15 dev1 foobar.htm

If CVS fails to find the specified revision or date, it will set the tag to the latest revision of that file.

Suppose a user sets the tag GM1 to the wrong revision of foobar.htm. To move that tag to the correct revision, e.g. 2.0, use the —F option.

   cvs rtag —F —r 2.0 GM1 foobar.htm

First, CVS removes the tag GM1 from foobar.htm. Then it assigns the same tag to revision 2.0 of that file.

Assume that project foobar has a subdirectory named scripts. To set the tag alpha3 to all the files in that subdirectory, type the cvs rtag command as follows.

   cvs rtag alpha3 foobar/scripts

Not only will CVS tag all the files in scripts, it will also locate any scripts subdirectories and tag their files as well. To tag only those files in the scripts subdirectory, use the —l option.

   cvs rtag —l alpha3 foobar/scripts

Managing diffs

Now, you use the cvs diff command to compare two revisions of a file or project. But to do the comparisons directly on the repository, use the cvs rdiff command. Again, unlike the former, you do not need a working copy of the project to use this command.

The basic syntax of the cvs rdiff command is as follows.

   cvs rdiff [options] file | project

This command shares many of the same options as the cvs rdiff command. Assume, for example, that you are managing the project foobar. To set the tag alpha1 to the latest revision of foobar.htm, type the command as follows.

Assume you are working on project foobar. To compare its latest revision against revision 1.5, type the cvs rdiff command with a —r option.

   cvs rdiff —r 1.5 foobar

To compare revision 1.1 against 1.5, use two —r options as follows.

   cvs rdiff —r 1.1 —r 1.5 foobar

Make sure the repository contains both revisions, or CVS will return an error message. If you are not sure, you can add a —f option to the command.

   cvs rdiff —f —r 1.1 —r 1.5 foobar

CVS will use the latest revision if it fails to find one of the revision numbers.

Suppose you want to check on the project file foobar.htm. To compare its latest revision against the one on 2007 Sep 01, type the cvs rdiff command with a —D option.

   cvs rdiff —D 2007/09/01 foobar/

To compare the file from 2007 Sep 15 against the one on 2007 Sep 01, use two —D options as follows.

   cvs rdiff —D 2007/09/01 —D 2007/09/30 foobar/foobar.htm

Make sure to place the earliest date first. Make sure also that the repository contains both dates. Use the f option if you are not sure.

Now the cvs rdiff command generates its output in one of two formats. The first format, context diff, is the default format. It is the one used by most BSD projects. The second format, unified diff, is a more compact format. It is also the one used by most GNU projects.

Assume you are comparing the latest revision of foobar.css against revision 1.5. To save the results in context diff, type the cvs rdiff command as follows.

   cvs rdiff —r 1.5 foobar/foobar.css > foobar.diff

CVS then saves the comparison results into the file foobar.diff. To save the results in unified diff, add a —u option.

cvs rdiff —r 1.5 —u foobar/foobar.css > foobar.diff

Once you saved the results, you can send the file to non—CVS users. Those users can then update their copy of foobar.css using your diff file and the patch tool. For more information about that tool, type man patch at the Terminal prompt.

Managing miscellany

Use the cvs admin command to make changes to a project file in your repository. Unlike the previous two commands, you will need a working copy of the project in order to use this command. Also, most changes you make with this command are undoable. Make a backup of the repository to protect yourself from any mistakes.

The basic syntax of the cvs admin command is as follows.

   cvs admin [options] [file]

The file argument specifies which file to change. If this argument is missing, the command will apply the change to all the latest revisions of the project's files. The options argument specifies what changes to make to the file in the repository.

Suppose a user used the wrong message when he committed his changes to the file foobar.htm. To correct the message, first find out the revision number of that committed file, e.g. 1.5. Then use the cvs admin command with a —m option as follows.

   cvs admin —m1.5:"the correct committal message here" foobar.htm

Suppose you want to trim down your project repository. A good way to do so is to use the cvs admin command with a —o option. Then specify a range of revisions to remove from the repository. For example, to remove all revisions of foobar.htm between 1.2 and 1.5, type the command as follows.

   cvs admin —o1.2::1.5 foobar.htm

Note the use of double—colons, '::', when setting the range. To remove revisions 1.2 and 1.5 as well, use a single colon, ':', to set the range.

   cvs admin —o1.2:1.5 foobar.htm

To remove revisions 1.2 and older of foobar.htm, specify the range as follows.

   cvs admin —o:1.2 foobar.htm

To remove revisions 1.2 and newer of that file, specify the range as follows.

   cvs admin —o1.2: foobar.htm

Again, if you want to exclude revision 1.2 from the range, use double—colons, '::', to set the range.

By default, CVS sets all project files to an Exp (experimental) state. Other possible states include Stab, for stable; and Rel, for release. You can also specify your own state label.

Suppose you want to change the latest revision of the foobar.htm file to a Stab state. To do so, use the cvs admin command with a —s option.

   cvs admin —sStab: foobar.htm

To set revision 1.5 of foobar.htm to a Test state, type the command as follows.

   cvs admin —sTest:1.5 foobar.htm

Notice that there are no spaces between the —s option and the state label itself. Notice also that the revision number comes after the ':' token. To find out if CVS set the correct state, type cvs log foobar.htm. CVS will display the file's state in one of its log entries (Figure 1, red).

CVS also leaves the project file's description blank. To add your own description, use the cvs admin command with a —t option. For example, to add a description to foobar.htm, type the command as follows.

   cvs admin —t—"This is a test HTML file." foobar.htm

Note the use of a dash, '—', to separate the —t option and the description string. To add a much larger description, first add the description to a separate file, e.g. foobar.txt. Then type the cvs admin command as follows.

   cvs admin tfoobar.txt foobar.htm

Also, when you type cvs log foobar.htm, you will see the description string on that command's output (Figure 1, green).

Final Thoughts

This article has shown you a handful of ways to get more out of your CVS setup. It showed how to configure your setup to suit your needs. It showed how to track changes to project files and the users that made them. It also showed how to maintain the repository, its tags and diffs.

Despite its limits, CVS is still a popular tool for managing OS X projects. It is available on all versions of OS X, and it integrates well with other tools such as BBEdit and Xcode. It also inspired users to create tools that address its limits and extend its capabilities.

It is possible that other SCM tools such as Subversion and Git will finally replace CVS in the near future. Until that happens, however, CVS is a strong management system, alive and well.

Bibliography and References

Cruz, José R.C. "Version Control on a Budget". MacTech Magazine. Volume 22. Issue 10. (c) 2006 MacTech.

Cederqvist, Per. "Reference manual for Administrative files". CVS—Concurrent Versions System v1.11.22. (c) 2003, 2006 Ximbiot, LLC. Online: http://ximbiot.com/cvs/manual/cvs1.11.22/cvs_18.html#SEC158

Fogel, Karl, Moshe Bar. "Using Keyword Expansion". Open Source Development with CVS, 3rd Edition. (c) 1999, 2000 Karl Fogel. Online: http://cvsbook.redbean.com/cvsbook.html#Using%20Keyword%20—Expansion

Free Software Foundation. "Pattern Matching". Bash Reference Manual. (c) 1991—2002 Free Software Foundation. Online:

http://www.gnu.org/software/bash/manual/bashref.html#SEC35


JC is a freelance engineering writer from North Vancouver, British Columbia. He spends his time writing technical articles; tinkering with Cocoa, REALbasic, and Python; and visiting his foster nephew. He can be reached at anarakisware@gmail.com.

 

Community Search:
MacTech Search:

Software Updates via MacUpdate

BBEdit 11.1.1 - Powerful text and HTML e...
BBEdit is the leading professional HTML and text editor for the Mac. Specifically crafted in response to the needs of Web authors and software developers, this award-winning product provides a... Read more
CrossOver 14.1.3 - Run Windows apps on y...
CrossOver can get your Windows productivity applications and PC games up and running on your Mac quickly and easily. CrossOver runs the Windows software that you need on Mac at home, in the office,... Read more
Little Snitch 3.5.3 - Alerts you about o...
Little Snitch gives you control over your private outgoing data. Track background activity As soon as your computer connects to the Internet, applications often have permission to send any... Read more
OmniGraffle Pro 6.2.3 - Create diagrams,...
OmniGraffle Pro helps you draw beautiful diagrams, family trees, flow charts, org charts, layouts, and (mathematically speaking) any other directed or non-directed graphs. We've had people use... Read more
OmniFocus 2.2 - GTD task manager with iO...
OmniFocus helps you manage your tasks the way that you want, freeing you to focus your attention on the things that matter to you most. Capturing tasks and ideas is always a keyboard shortcut away in... Read more
Cocktail 8.4 - General maintenance and o...
Cocktail is a general purpose utility for OS X that lets you clean, repair and optimize your Mac. It is a powerful digital toolset that helps hundreds of thousands of Mac users around the world get... Read more
PDFKey Pro 4.3 - Edit and print password...
PDFKey Pro can unlock PDF documents protected for printing and copying when you've forgotten your password. It can now also protect your PDF files with a password to prevent unauthorized access and/... Read more
Kodi 15.0.beta1 - Powerful media center...
Kodi (was XBMC) is an award-winning free and open-source (GPL) software media player and entertainment hub that can be installed on Linux, OS X, Windows, iOS, and Android, featuring a 10-foot user... Read more
DiskCatalogMaker 6.4.12 - Catalog your d...
DiskCatalogMaker is a simple disk management tool which catalogs disks. Simple, light-weight, and fast. Finder-like intuitive look and feel. Super-fast search algorithm. Can compress catalog data... Read more
Macs Fan Control 1.3.0.0 - Monitor and c...
Macs Fan Control allows you to monitor and control almost any aspect of your computer's fans, with support for controlling fan speed, temperature sensors pane, menu-bar icon, and autostart with... Read more

Moleskine Timepage – Calendar for iCloud...
Moleskine Timepage – Calendar for iCloud, Google & Exchange 1.0 Device: iOS iPhone Category: Productivity Price: $4.99, Version: 1.0 (iTunes) Description: The most elegant calendar for your pocket and wrist, Timepage is a... | Read more »
QuizUp Gets Social in its New Update
Plain Vanilla Corp has released a new and improved version of their popular trivia game, QuizUp. The app now emphasizes social play so you can challenge friends from all over the world. [Read more] | Read more »
The Deep (Games)
The Deep 1.0 Device: iOS Universal Category: Games Price: $1.99, Version: 1.0 (iTunes) Description: Swipe Controls Delve into the deep in this retro rogue-like! Swipe to move your diver around and keep away from the enemies as you... | Read more »
Battle of Gods: Ascension (Games)
Battle of Gods: Ascension 1.0 Device: iOS Universal Category: Games Price: $2.99, Version: 1.0 (iTunes) Description: TURN-BASED TACTICAL COMBATFight tactical battles against the forces of Hades! In Battle of Gods: Ascension you play... | Read more »
Shadowmatic's Latest Update Adds a...
Shadowmatic's shadowy shadow-ness is getting a little shadowy-er thanks to a recent update that adds an Arcade Mode. [Read more] | Read more »
Sunrise Calendar and Slack Have Assimila...
Wunderlist is perhaps one of the most populat and beloved productivity apps on the App Store - and now it's gone and incorporated itself into other useful services like Sunrise Calendar and Slack. [Read more] | Read more »
Crossy Road Devs Hipster Whale are Bring...
Hipster Whale, the minds behind the rather popular (and rather great) Crossy Road, have teamed-up with Bandai Namco to create PAC-MAN 256: an absolutely bonkers looking maze runner chaser thing. | Read more »
Meet the New Spotify Music
Spotify Music  has a lot going on. They're introducing 3 new modes to serve all your musical needs, with the "Now" start page  gives you curated playlists based on your particular tastes. As you listen the app will learn more about your tastes and... | Read more »
What the Apple Watch Gets Right, and Wha...
| Read more »
Celebrate PAC-MAN's 35th Birthday W...
BANDAI NAMCO Entertainment America is celebrating PAC-MAN's 35th anniversary by releasing updates for PAC-MAN and PAC-MAN Lite for iOS. [Read more] | Read more »

Price Scanner via MacPrices.net

Apple refurbished 2014 13-inch Retina MacBook...
The Apple Store has Apple Certified Refurbished 2014 13″ Retina MacBook Pros available for up to $400 off original MSRP, starting at $979. An Apple one-year warranty is included with each model, and... Read more
What Would the ideal Apple Productivity Platf...
For the past four years I’ve kept a foot in both the Mac and iPad camps respectively. my daily computing hours divided about 50/50 between the two devices with remarkable consistency. However, there’... Read more
PageMeUp 1.2.1 Ten Dollar Page Layout Applica...
Paris, France-based Softobe, an OS X software development company, has announced that their PageMeUp v. 1.2.1, is available on the Mac App Store for $9.99. The license can be installed on up to 5... Read more
Eight New Products For USB Type-C Application...
Fresco Logic, specialists in advanced connectivity technologies and ICs, has introduced two new product families targeting the Type-C connector recently introduced across a number of consumer... Read more
Scripps National Spelling Bee Launches Buzzwo...
Scripps National Spelling Bee fans can monitor the action at the 2015 Spelling Bee with the new Buzzworthy app for iOS, Android and Windows mobile devices. The free Buzzworthy app provides friendly... Read more
13-inch 2.5GHz MacBook Pro on sale for $120 o...
B&H Photo has the 13″ 2.5GHz MacBook Pro on sale for $979 including free shipping plus NY sales tax only. Their price is $120 off MSRP, and it’s the lowest price for this model (except for Apple’... Read more
27-inch 3.3GHz 5K iMac on sale for $1899, $10...
B&H Photo has the new 27″ 3.3GHz 5K iMac on sale for $1899.99 including free shipping plus NY tax only. Their price is $100 off MSRP. Read more
Save up to $50 on iPad Air 2, NY tax only, fr...
B&H Photo has iPad Air 2s on sale for up to $50 off MSRP including free shipping plus NY sales tax only: - 16GB iPad Air 2 WiFi: $469 $30 off - 64GB iPad Air 2 WiFi: $549.99 $50 off - 128GB iPad... Read more
Updated Mac Price Trackers
We’ve updated our Mac Price Trackers with the latest information on prices, bundles, and availability on systems from Apple’s authorized internet/catalog resellers: - 15″ MacBook Pros - 13″ MacBook... Read more
New 13-inch 2.9GHz Retina MacBook Pro on sale...
B&H Photo has the 13″ 2.9GHz/512GB Retina MacBook Pro on sale for $1699.99 including free shipping plus NY tax only. Their price is $100 off MSRP, and it’s the lowest price for this model from... Read more

Jobs Board

*Apple* Solutions Consultant - Retail Sales...
**Job Summary** As an Apple Solutions Consultant (ASC) you are the link between our customers and our products. Your role is to drive the Apple business in a retail Read more
*Apple* Watch SW Application Project Manager...
**Job Summary** The Apple Watch software team is looking for an Application Engineering Project Manager to work on new projects for Apple . The successful candidate Read more
Engineering Manager for *Apple* Maps on the...
…the Maps App Team get to take part in just about any new feature in Apple Maps, often contributing a majority of the feature work. In our day-to-day engineering work, we Read more
Senior Software Engineer - *Apple* SIM - Ap...
Changing the world is all in a day039s work at Apple . If you love innovation, here039s your chance to make a career of it. You039ll work hard. But the job comes with Read more
Lead *Apple* Solutions Consultant - Retail...
**Job Summary** Job Summary The Lead ASC is an Apple employee who serves as the Apple business manager and influencer in a hyper-business critical Reseller's store Read more
All contents are Copyright 1984-2011 by Xplain Corporation. All rights reserved. Theme designed by Icreon.