Server/Code/modifications to main.js - Revision history

Deusexmachina at 20:45, 7 September 2012

2012-09-07T20:45:48Z

← Older revision		Revision as of 20:45, 7 September 2012
Line 328:		Line 328:
	</body>		</body>
	</html>		</html>
			</pre>

	Feel free to modify the confirmation text as you see fit.		Feel free to modify the confirmation text as you see fit.
	~~</pre>~~

2012-09-07T20:44:47Z

@@ Line 199: / Line 199: @@
 	</body>
 </html>
 </pre>

2012-09-04T06:10:43Z

@@ Line 88: / Line 88: @@
 	// Sets the flag to tell confirmUnload subroutine that it is OK to let the user leave this page (close the Window, etc.)
 	allowUnload = true;
 </pre>

2012-09-04T03:48:06Z

← Older revision		Revision as of 03:48, 4 September 2012
Line 68:		Line 68:

	Alternately, you can just use the entire main.js file from the previous page.		Alternately, you can just use the entire main.js file from the previous page.

			Lastly, it is probably undesirable in a kiosk-type session to allow the person to close the window on your laptops, thus making the machine useless for the next user. To block this, I added the following code:

			Add this to the script section of your mainscreen.html file (and any other page you want to stop the user from closing:

			<pre>
			//function triggered by any closing of the current document
			function confirmUnload(){
			if(!allowUnload){
			//message displayed (as well as inbuilt IE junk) when page is unloaded.
			return 'Why on earth would you think it is a good idea to close this window?!? Well, it ISN\'T!!! Do NOT close this window. If you do, all hell will rain down upon you, you will cause a micro-singularity to destroy the known universe, and I will get very upset. (At you closing the window, not the destruction of the universe, that can fend for itself.)\n :\'(';
			}
			}
			</pre>

			Then add the following lines to the function m_sessionLogout function of your main.js

			<pre>
			// Sets the flag to tell confirmUnload subroutine that it is OK to let the user leave this page (close the Window, etc.)
			allowUnload = true;
			</pre>

2012-09-04T02:56:09Z

← Older revision		Revision as of 02:56, 4 September 2012
Line 59:		Line 59:
	</pre>		</pre>

	Then you can just add the following code into your other pages:		Then you can just add the following code into the javascript section of your other pages:
	<pre>		<pre>
			//Bind key press function
			document.onkeyup = m_keyPressed;
	//Prevent browser from seeing the Delete key press		//Prevent browser from seeing the Delete key press
	document.onkeydown=trapDelete;		document.onkeydown=trapDelete;

2012-09-04T02:46:53Z

← Older revision		Revision as of 02:46, 4 September 2012
Line 61:		Line 61:
	Then you can just add the following code into your other pages:		Then you can just add the following code into your other pages:
	<pre>		<pre>
	//Prevent browser from seeing the Delete key press		//Prevent browser from seeing the Delete key press
	document.onkeydown=trapDelete;		document.onkeydown=trapDelete;
	</pre>		</pre>

	Alternately, you can just use the entire main.js file from the previous page.		Alternately, you can just use the entire main.js file from the previous page.

2012-09-04T02:46:14Z

← Older revision		Revision as of 02:46, 4 September 2012
Line 57:		Line 57:
	return true;		return true;
	}		}
			</pre>

			Then you can just add the following code into your other pages:
			<pre>
			//Prevent browser from seeing the Delete key press
			document.onkeydown=trapDelete;
	</pre>		</pre>

	Alternately, you can just use the entire main.js file from the previous page.		Alternately, you can just use the entire main.js file from the previous page.

2012-09-04T02:44:34Z

← Older revision		Revision as of 02:44, 4 September 2012
Line 34:		Line 34:

	</pre>		</pre>

			In addition, it is very useful to trap the delete key, so that users do not inadvertently go back to the previous page by hitting this key (which, for instance, might take them back to the previous singers page from the login screen after a log out). This would be bad!
			To do this, you need to make a few mods to the pages. In particular, you need to call the function in your pages. To make it work, paste this into the variable declaration section of your main.js (at the top).

			<pre>
			//checks to see if the search field it in focus. If it is, allow the user to use the Delete/Backspace key. Otherwise, set flag to trap it.
			var inSearch = {
			on: function() {allowBackspace = true;},
			off: function() {allowBackspace = false;}
			}
			</pre>

			And then add this somewhere in the function declarations:

			<pre>
			function trapDelete() {
			//Checks to see if the key pressed is the Delete/Backspace key, and if so, stop it from getting to the browser.
			var keyID = (window.event) ? event.keyCode : e.keyCode;
			if (keyID==8 && !allowBackspace){
			return false;
			}
			return true;
			}
			</pre>

			Alternately, you can just use the entire main.js file from the previous page.

2011-03-13T21:35:52Z

← Older revision		Revision as of 21:35, 13 March 2011
Line 1:		Line 1:
	Often times when using kJams ~~server~~, the user will miss the "Song Added" alert at the bottom of the window. (Heck, even I just recently noticed it!) As a result, they will mistakenly hit the "Tonight" button over and over, thus adding the song multiple times. To combat this (but not be quite as intrusive as a pop up alert) I made this little code snippet that will make the text bright red and flash it several times to catch the users attention.		Often times when using kJams Server, the user will miss the "Song Added" alert at the bottom of the window. (Heck, even I just recently noticed it!) As a result, they will mistakenly hit the "Tonight" button over and over, thus adding the song multiple times. To combat this (but not be quite as intrusive as a pop up alert) I made this little code snippet that will make the text bright red and flash it several times to catch the users attention.

	To use it, open the file "main.js" (it should be in "~/Libraries/Preferences/kJams/server") and find the "function m_setStatus(status, revert)" code block. Replace it with the text below and save.		To use it, open the file "main.js" (it should be in "~/Libraries/Preferences/kJams/server") and find the "function m_setStatus(status, revert)" code block. Replace it with the text below and save.

2011-03-13T21:33:29Z

← Older revision		Revision as of 21:33, 13 March 2011
Line 1:		Line 1:
	Often times when using kJams server, the user will miss the "Song Added" alert at the bottom of the window. (Heck, even I just recently noticed it!) As a result, they will mistakenly hit the "Tonight" button over and over, thus adding the song multiple times. To combat this (but not be quite as intrusive as a pop up alert. I made this little code snippet that will make the text bright red, and flash it several times to catch the users attention.		Often times when using kJams server, the user will miss the "Song Added" alert at the bottom of the window. (Heck, even I just recently noticed it!) As a result, they will mistakenly hit the "Tonight" button over and over, thus adding the song multiple times. To combat this (but not be quite as intrusive as a pop up alert) I made this little code snippet that will make the text bright red and flash it several times to catch the users attention.

	To use it, open the file "main.js" (it should be in "~/Libraries/Preferences/kJams/server") and find the "function m_setStatus(status, revert)" code block. Replace it with the text below and save.		To use it, open the file "main.js" (it should be in "~/Libraries/Preferences/kJams/server") and find the "function m_setStatus(status, revert)" code block. Replace it with the text below and save.