Scripts - Revision history

Jlderidder: /* Additions */

2012-10-03T15:38:35Z

Additions

←Older revision		Revision as of 15:38, 3 October 2012
Line 74:		Line 74:
	===Additions===		===Additions===
	* [[Shift Reporter]]		* [[Shift Reporter]]
-	* [[filenamesAndDupes]]	+	* [[image:filenamesAndDupes.txt]]
-	* [[makeJpegs]]	+	* [[image:makeJpegs.txt]]
-	* [[relocate_all]]	+	* [[image:relocate_all.txt]]
-	* [[findMissing]]	+	* [[image:findMissing.txt]]
-	* [[moveContent]]	+	* [[image:moveContent.txt]]

Jjcolonnaromano at 18:21, 12 September 2012

2012-09-12T18:21:12Z

←Older revision		Revision as of 18:21, 12 September 2012
Line 25:		Line 25:

	[[Counting stuff]]		[[Counting stuff]]
		+
		+	==On Making Scripts Work From the S Drive on Windows==
		+
		+	===Associating Ruby Scripts===
		+	*To associate a Ruby .rbw file with the run-time executable found on the Share Drive
		+	**Double click on the script file or a shortcut to the script file.
		+	**If you do not have Ruby installed on your local machine or proper file associations in place Windows will show you an error telling you it does not know what to do with that kind of file.
		+	**In the error window select the option to choose an application from a list, then click OK.
		+	**Click on Browse then navigate to "S:\Digital Projects\Administrative\scripts\Ruby193\bin" and select in this case "rubyw.exe"
		+	**Make sure the "Always use this application..." box is checked, and click "Ok".
		+	**Once the file association is made files with that extension will always default to opening with the selected application.
		+	**The file associations need to be set separately for each computer that needs to run scripts with an executable located on the S Drive.

	==On Making Scripts Work on Mac OSX==		==On Making Scripts Work on Mac OSX==

Howar039 at 21:24, 11 July 2012

2012-07-11T21:24:05Z

←Older revision		Revision as of 21:24, 11 July 2012
Line 57:		Line 57:
	*Make sure you use only forward slashes for path slashes. e.x. "foo/bar" is good, but "foo\bar" is bad.		*Make sure you use only forward slashes for path slashes. e.x. "foo/bar" is good, but "foo\bar" is bad.
	**There should be no need to ever use backslashes in scripts, however, as Windows OS is equally tolerant of forward and back slashes.		**There should be no need to ever use backslashes in scripts, however, as Windows OS is equally tolerant of forward and back slashes.
		+
		+
		+
		+	===Additions===
		+	* [[Shift Reporter]]
		+	* [[filenamesAndDupes]]
		+	* [[makeJpegs]]
		+	* [[relocate_all]]
		+	* [[findMissing]]
		+	* [[moveContent]]

Scpstu32: /* Running Scripts */

2011-03-23T15:24:38Z

Running Scripts

←Older revision		Revision as of 15:24, 23 March 2011
Line 43:		Line 43:
	*In the second case the script AND in the case of double-clicking the filename, the script would have to include the appropriate shebang line, for example '''#!/usr/bin/python''' for Python scripts and '''#!/usr/bin/perl''' for Perl scripts.		*In the second case the script AND in the case of double-clicking the filename, the script would have to include the appropriate shebang line, for example '''#!/usr/bin/python''' for Python scripts and '''#!/usr/bin/perl''' for Perl scripts.
	**This will allow the MACs to know where to locate Python and Perl, respectively.		**This will allow the MACs to know where to locate Python and Perl, respectively.
-	**If for some reason this doesn't work, make sure the script is saved with a UNIX style ~~byte order~~ so that the shebang will be read properly by the MAC.	+	**If for some reason this doesn't work, make sure the script is saved with a UNIX style EOL (end of line) so that the shebang will be read properly by the MAC.
	**A good text editor like [http://notepad-plus-plus.org/ Notepad ++] (Windows) easily allows one to make these changes to text files.		**A good text editor like [http://notepad-plus-plus.org/ Notepad ++] (Windows) easily allows one to make these changes to text files.

Scpstu32: /* Running Scripts */

2010-12-01T15:48:13Z

Running Scripts

←Older revision		Revision as of 15:48, 1 December 2010
Line 44:		Line 44:
	**This will allow the MACs to know where to locate Python and Perl, respectively.		**This will allow the MACs to know where to locate Python and Perl, respectively.
	**If for some reason this doesn't work, make sure the script is saved with a UNIX style byte order so that the shebang will be read properly by the MAC.		**If for some reason this doesn't work, make sure the script is saved with a UNIX style byte order so that the shebang will be read properly by the MAC.
-	**A good text editor like Notepad ++ (Windows) easily allows one to make these changes to text files.	+	**A good text editor like [http://notepad-plus-plus.org/ Notepad ++] (Windows) easily allows one to make these changes to text files.

	===Programming Notes===		===Programming Notes===

Scpstu32: /* Programming Notes */

2010-11-10T22:06:01Z

Programming Notes

←Older revision		Revision as of 22:06, 10 November 2010
Line 49:		Line 49:
	*Save scripts with a UNIX style byte order. Not doing so appears to prevent the OS from being able to read the shebang line.		*Save scripts with a UNIX style byte order. Not doing so appears to prevent the OS from being able to read the shebang line.
	*If you are adding timestamps to log files you may need to strip all whitespaces and colons from your timestamp variable. Not doing so can prevent the file from getting written.		*If you are adding timestamps to log files you may need to strip all whitespaces and colons from your timestamp variable. Not doing so can prevent the file from getting written.
-	**For example if your timestamp variable is '''$timestamp''' in a PERL script try this:	+	**For example if your timestamp variable is '''$timestamp''' in a PERL script try this after you've already established your timestamp value:
	#start MAC block		#start MAC block
	#trimming whitespace and colons because the MAC won't write the output file if they are present		#trimming whitespace and colons because the MAC won't write the output file if they are present

Scpstu32: /* Programming Notes */

2010-11-10T21:54:20Z

Programming Notes

←Older revision		Revision as of 21:54, 10 November 2010
Line 48:		Line 48:
	===Programming Notes===		===Programming Notes===
	*Save scripts with a UNIX style byte order. Not doing so appears to prevent the OS from being able to read the shebang line.		*Save scripts with a UNIX style byte order. Not doing so appears to prevent the OS from being able to read the shebang line.
-	*If you are adding timestamps to log files you may need to strip all whitespaces and colons from your timestamp variable ~~for any timestamps~~ . Not doing so can prevent the file from getting written.	+	*If you are adding timestamps to log files you may need to strip all whitespaces and colons from your timestamp variable. Not doing so can prevent the file from getting written.
	**For example if your timestamp variable is '''$timestamp''' in a PERL script try this:		**For example if your timestamp variable is '''$timestamp''' in a PERL script try this:
	#start MAC block		#start MAC block

Scpstu32: /* Programming Notes */

2010-11-10T21:53:44Z

Programming Notes

←Older revision		Revision as of 21:53, 10 November 2010
Line 48:		Line 48:
	===Programming Notes===		===Programming Notes===
	*Save scripts with a UNIX style byte order. Not doing so appears to prevent the OS from being able to read the shebang line.		*Save scripts with a UNIX style byte order. Not doing so appears to prevent the OS from being able to read the shebang line.
-	*If you are adding timestamps to log files in strip all whitespaces and colons from your timestamp variable for any timestamps . Not doing so can prevent the file from getting written.	+	*If you are adding timestamps to log files you may need to strip all whitespaces and colons from your timestamp variable for any timestamps . Not doing so can prevent the file from getting written.
	**For example if your timestamp variable is '''$timestamp''' in a PERL script try this:		**For example if your timestamp variable is '''$timestamp''' in a PERL script try this:
	#start MAC block		#start MAC block

Scpstu32: /* Programming Notes */

2010-11-10T21:52:53Z

Programming Notes

←Older revision		Revision as of 21:52, 10 November 2010
Line 56:		Line 56:
	#end MAC block		#end MAC block
	*Make sure you use only forward slashes for path slashes. e.x. "foo/bar" is good, but "foo\bar" is bad.		*Make sure you use only forward slashes for path slashes. e.x. "foo/bar" is good, but "foo\bar" is bad.
-	**There should be no need to ever use backslashes in scripts, however, as Windows OS is equally tolerant of forward and ~~backslashes~~.	+	**There should be no need to ever use backslashes in scripts, however, as Windows OS is equally tolerant of forward and back slashes.

Scpstu32 at 21:52, 10 November 2010

2010-11-10T21:52:29Z

←Older revision		Revision as of 21:52, 10 November 2010
Line 55:		Line 55:
	$timestamp=~ s/://g;		$timestamp=~ s/://g;
	#end MAC block		#end MAC block
-	*Make sure you use only forward slashes for path slashes. e.x. "foo.bar" is good, but "foo\bar" is bad.	+	*Make sure you use only forward slashes for path slashes. e.x. "foo/bar" is good, but "foo\bar" is bad.
	**There should be no need to ever use backslashes in scripts, however, as Windows OS is equally tolerant of forward and backslashes.		**There should be no need to ever use backslashes in scripts, however, as Windows OS is equally tolerant of forward and backslashes.