2005_05_30
	- Looked for the code, cleaned up documentation
	- Quick visual code inspection
	??? What of instead of using an integer to write md5 burn number, we created a timestamp, and then
	  maintained a file that associated that timestamp with the original list of files burned. This will allow
	  us to easily verify or compare that was burned N days ago.
		-> Waste disk space
		-> Might as well save every project completed that exists properly (99)
		-> Should we do this automatically as a cool feature?

In cd create we want our own size of function
We'll have much better performance than DU
since DU will need to perform the entire size of a directory, even if it is larger than the media size

But DU can be useful. 

How about a function that would tell you how many CDs it would take to backup this data
Update it live in the search browser. 



2005_05_25
	+ Changed output of TestExec() to exec()
	+ Fixed passing of multisession arguments to mkisofs

	??? Found that multisession support is not working in Windows. Is this cdrecord's fault?
		-> In order for the cd-rom data to be reloaded the cd must be ejected and reread.
		-> This removes our ability to easily verify cd-rom data since we cannot read changes
		   on some systems (such as a system with a spring loaded cd-rom -- found on most laptops)
		-> Therefore, checksum's cannot be properly verified on some system's. This occurs on systems
		   where the cd-rom does not have the ability to open/close itself via software.

	? FIXED: When doing multisession burning, where do multiple checksum files go?
		-> n-disk_md5.txt, where n is the number of times the cd has been burned.
		-> On the upside, we can control which session we want to verify

	? FIXED: What happens when you have chopped up the data, but that data is already data on the CD?
		-> Its overwritten.

	? Trimming trailing file seperator for proper directory clipping (when input is taken from the 
	   command line, or interactive mode).

2005_05_22
	+ Fixed typo in env_setup.bat
	+ Verified Jfilerunner in Windows (simply added ls from cygwin)
	+ Modified default mkisofs arguments
	+ Fixed error reporting CD sizes to log file
	+ Updated README.txt
	+ Changed default location of temporary directory
	+ Cleaned up exit mechanism of batch scripts

2005_05_21
	+ Slightly restructured windows bat files. Benefit? Edit Java
	  location in only one file now. Build/run scripts both call
	  <env_setup.bat>.
	+ Found bug loading edcrc (assignment must be trim()'ed)

2005_04_23
	+ Fixed bug reporting burn failure
	+ Improved verbosity of application
	+ Printing of variable settings via command line argument
	+ Loading configuration file from command line
	+ Fixed bug when you reset CDCase (keeping config values)
	+ Improve appearance of command line GUI

2005_04_21
	+ Loading settings from configuration file
	+ Changed setup of command line interface
	+ Added batch mode support
	+ Fixed bug when creating successive ISOs



todo:		Add option to command line interface that prints the current configuration settings
DONE:		Add shortcut to "Send To" Menu
todo:		add configuration panel to Jfilerunner (settings)
			(search and replace feature for writing output)
todo:		modify jfilerunner so that you can traverse directories using only keyboard
			bind rename to F2
todo:		when scripts are done, ensure window does not automatically close
todo:		are we not passing the -multi option to cdrecord?
		http://www.physics.iitm.ac.in/~sanoop/linux_files/cdburn.html

todo:		fix post burn verification in windows

todo:		remove the necessity to create an image on the disk

			mkisofs -J -r dir_with_files/ | cdrecord dev=ATAPI:0,1,0 -v -multi -pad -data -
		
		taken from: http://axljab.homelinux.org/CD_writing

		Coincidentally enough, puppy linux just released a new version. We can create the data
		only the fly, and write the log file to the usb flash drive.
		

What functions do we want to keep in the middle panel?

Delete
Move
Mkdir