Changeset 2

Timestamp:

09/12/08 01:27:31 (2 years ago)

Author:

nathanhammond

Message:

• Migrate NOTES.txt to be tracked by the ticketing system.
• Pull out the FIXME from jquery.jssm.js.
• Update jquery.jssm.js to include revision and date keywords.
• Update LICENSE.txt with the newest project name.
• Add VERSION.txt to track the version being developed.

Location:

trunk

Files:

• LICENSE.txt (modified) (1 diff)
• NOTES.txt (deleted)
• VERSION.txt (added)
• jquery.jssm.js (modified) (2 diffs, 1 prop)

trunk/LICENSE.txt

@@ -1 @@
-JSSM (JavaScript State Machine)
+JSSM (JavaScript State Manager)
 Copyright (c) 2008 Nathan Hammond
 

trunk/jquery.jssm.js

@@ +1 @@
+/*
+JSSM @VERSION (JavaScript State Manager)
+Copyright (c) 2008 Nathan Hammond
+
+Licensed under the MIT License (LICENSE.txt)
+
+To report bugs or get the lates version, visit the website:
+http://trac.nathanhammond.com/jssm/
+
+$Date$
+$Revision$
+*/
+
 /*
 Object jssm
@@ -167 +180 @@
                 if (jssm.functions.afterload) { jssm.functions.afterload(calchash); }
 
-
-                /*
-                TODO: Find a solution to the "repetition of history" problem for manually re-entered hashes.
-                FIXME: There is a possible fail state, if a person manually re-enters a previously existing hash it will be appended to the end of the history, but the stack pointer will be adjusted to the first time it appeared in the history stack. This creates a state where you've come to the page "fresh" but are loading the old state.
-
-                PARTIAL SOLUTION: Watch for changes in window.history.length. Compare these to the initial length when arriving at the page and the number of items on the site's stack.
-
-                Success Scenarios:
-                1. A manually re-entered hash that matches the current one won't trigger an event or change the length (click location bar, press enter, no change).
-                2. A manually re-entered hash that doesn't match the current hash changes window.history.length, and is catchable.
-
-                Fail Scenarios:
-                1. The user is exactly one spot deep in the browser history stack. The length does not change because it pops all future events off the stack and adds a new one immediately.
-                */
-
                 // Figure out where to set the pointer.
                 var exists = [];