The Apple instructions show how to use both svnserve and the Apache plugin as approaches to setting up Subversion. Both allow outside access. The Apache approach is useful for large groups of developers while the svnserve approach is appropriate for smaller groups. But neither address a single developer working on one computer. Svnserve can be used in a local fashion that does not require turning on remote access. Since everything is local, ssh is not necessary and connections are more reliable and do not require internet access.

Setting up the repository

Start by following the instructions to set up a repository. For this article it will be located at /Library/Subversion/Repository but can be located elsewhere.

mkdir -p /Library/Subversion/Repository
svnadmin create /Library/Subversion/Repository/Project1

Import an empty directory structure using a temporary directories.

mkdir -p /tmp/Project1/trunk /tmp/Project1/branches /tmp/Project1/tags
svn import /tmp/Project1/ file:///Library/Subversion/Repository/Project1 -m "Initial import"
rm -rf /tmp/Project1

Restrict the permissions.

sudo chown -R root:admin /Library/Subversion/Repository
sudo chmod -R ug+rwX,o= /Library/Subversion/Repository

Setting up Xcode

Open Xcode and create Project1. It can just be placed on the Desktop since it will be removed once it has been imported into Subversion. Since the build directory does not need to be stored in Subversion, go to Project->Edit Project Settings and specify a Custom location and Build products location. Click on the Configure Roots & SCM button. If there already is an entry, delete it (-). Click the add repositories (+). For the Root, put the path to the Xcode project directory. Under Repository select Configure SCM Repositories.

Now we will diverge from the Apple instructions. Instead of using ssh enter the local repository form of the URL.

file:///Library/Subversion/Repository/Project1

The remaining fields should automatically fill once you leave the URL field and the status indicator should quickly show “Authenticated.” The advantage of this approach is remote login does not have to be enabled, the computer does not have to be hooked up to the internet, and the response is much faster.

Continuing with the instructions from Apple, go to SCM->Repositories and using the Repository browser select the trunk directory of the Project1 repository. Click on Import. Select the Xcode Project1 directory, add a comment and click on import. Click OK to confirm. Once the files are imported they can be deleted from the desktop.

Checking out and turn on SCM

Start Xcode but cancel at the first menu. Go to SCM->Repositories. Select the repository and then the trunk and Project1. Click on Checkout. Edit the name of the directory and select the location for it. When the checkout is completed you will be prompted to open it.

Go to Project->Edit Project Settings. Click on the Configure Roots & SCM. Under Root, enter the project directory. For the Repository, choose the repository just set up for this project.

The jQuery documentation suggests using the following code

$(document).ready(function(){
// do some fancy stuff
});

This runs the code when the document is ready but before the page is completely loaded (images and media may still be loading). Drupal calls this function and suggests the following code be used instead

Drupal.behaviors.myModule = function (context) {
//do some fancy stuff
};

While this is true it is like reading the middle of the book without the start or end. Surely there is some more information such as where to put this magical snippet of code that might be useful.

Javascript

Let’s go back and start at the beginning. The code above is Javascript so first we need to know how Drupal handles Javascript. There are three ways to add Javascript code in Drupal 6.x. First, there is the Drupal core which puts Javascript code in the js directory. This is typically not of interest unless looking at the version of jQuery or adding jQuery plugins. As with most other Drupal approaches, the other two methods are themes and modules. The same result can be achieved either way but the application may suggest one way or the other as better.

Module development

For a module, the code would likely go in the myModule.module file where myModule is the name of your module. It could go in the hook_form function but in this case I will show it in the page callback function which calls the hook_form function. In the myModule_menu function you should have code like this

$items['myPage'] = array(
'title' => 'My Module',
'page callback' => 'myModule_page',
'access arguments' => array('access myModule content'),
'type' => MENU_CALLBACK
);

Then in myModule_page function

function myModule_page() {
//echo drupal_get_path('module','myModule') . '/myModule.js';
drupal_add_js(drupal_get_path('module','myModule') . '/myModule.js');

where code for dumping the path to the Javascript file is commented out.

Then in myModule.js the following code should produce the “Hello, World”.

Drupal.behaviors.myModule = function(context) {
alert(“Hello, World”);
}

The context could be the entire page or a snippet added by other Javascript code.

Themes

I have not used Javascript/jQuery using the theme approach but it should follow the same pattern as for the style.css file. Drupal 6.x is supposed to look for a script.js file in your theme directory and automatically load the code. The same code in the myModule.js above should work.

P_r*Q^T*A*P_c^T =
| R |
| 0 |

where Q^T*Q = I in Re^mxm, R in Re^nxn upper triangular, and P_r in Re^mxm as well as P_c in Re^nxn are permutation matrices. Note that this is a research code developed for the following paper.

Thomas H. Robey and Deborah L. Sulsky, Row Ordering for Sparse QR Decomposition, SIAM J. Matrix Anal. and Appl., Vol. 15, No. 4, pp. 1208-1225, October 1994.

The software is available in C and C++ under the GNU Library General Public License. To obtain the source code click on the desired version listed below.

• C version
• C++ version

Version 2.* has improved code for calculating fill that results in less memory and faster execution. Version 3.* reduces work in the minimum degree calculation resulting in faster execution.