doc.txt

$LastChangedDate: 2007-05-26 16:59:16 -0500 (Sat, 26 May 2007) $

$LastChangedDate: 2007-05-26 16:59:16 -0500 (Sat, 26 May 2007) $
$LastChangedRevision: 92 $
$HeadURL: svn://osiris/drsync/tags/0.52/drsync/doc.txt $

---

What:

DrSync does two things:

1.	Synchronizes files on frame activation.

2. 	Saves files on frame deactivation.

---

Why:

*	Switching between DrScheme and your version control client, it is
	easier knowing that your file is saved, and ready for a commit. After
	going through this process only fifty or sixty times, you will begin 
	to appreciate any way to make it easier.

*	If you use version control keyword expansion, you need to revert your
	file each time you return to DrScheme.

*	If you use an external compilation process, sometimes you forget to
	save your changes, resulting in your quizzical stares and hair pulling.

---

How:

DrSync follows the KIS principle: Keep It Simple.

1.	Synchronization occurs only on frame activation and deactivation and
	at no other time. Opening file menus, switching between tabs, or moving
	between the editor and the REPL will not trigger synchronization.

2.	Every type of file will be synchronized. Whether you edit SS, SCM, or
	TXT files in the editor makes no difference. If there is a file open in
	a tab, it will be synchronized.

3.	Synchronization always occurs, it is not configurable. If you use this 
	tool, you most probably have a good reason to do so, and in the long 
	run you will be better off always knowing that your files are in sync
	at all times.