Changing where stickies live?

[Lazarus18]

I had a (for me at least) brilliant thought. I use my powerbook at school, and my G4 at home. I also love stickies, and throw random thoughts about papers I'm writing or to dos or whatever in them.

My brilliant thought would be to save the data in them to my iDisk so my stickies at home and at school would mirror each other. I found the file where all the data is stored, it's .stickiesdatabase in my ~user/library folder. The only problem is that I can't figure out how to tell the program that I want it to store that file somewhere else. com.apple.stickies.plist is of no help. I poked around inside the .pkg but didn't see anything. There must be some way to tell it where to retrieve that .stickiesdatabase when is starts up, and therefore a way to give it a new location.

Thoughts surpassing mine in brilliance anyone?

 

[Lazarus18]

OK, so barring that I have an interim solution. It sure could use some improving, so I'm all ears.

I set up a cron event to copy the .stickiesdatabase to my idisk every 30 minutes. I could of course do this more often.

I then wrote a script that on login mounts the idisk, copies the .stickiesdatabase from it to my ~/library and then launches stickies.

This works, but the problems are:
a) using the mount_webdav command I can't make my login and pw part of the command, so a window comes up and I have to enter that info. Annoying.
b) there must be a way to avoid it, but once everything in the script runs I get this dead terminal window that I have to shut down.

This is all probably because I know nothing about scripting. I wrote a little script which is:
#!/bin/tcsh
mkdir /idisk
mount_webdav http://idisk.mac.com/user /idisk
cp /idisk/Documents/.StickiesDatabase.copy ~/library/.StickiesDatabase
open /Applications/stickies.app

then I used show info to dictate that the terminal open the ap.

Please improve on this.

-------------------------------
Ammendment:
I'm a moron. The .stickiesdatabase is not updated unless you quit the ap or save all stickies. Therefore the cron event isn't necessarily getting the freshest, newest file. What I really need (as I have whined about elsewhere) is a way to run CLI items on logout. That way it could update the idisk when I logout on one machine, and then when I login on the other it would fetch that fresh one. Grrrrrr.