Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 245 lines (172 sloc) 14.701 kB
e19d74d @balupton readme update
authored
1 Welcome to History.js (v1.7.1 - October 4 2011)
8d5cacf @balupton Initial Commit
authored
2 ==================
3
3263e7e @balupton Moved the changelog into the History.md file
authored
4 [![Flattr this project](http://api.flattr.com/button/flattr-badge-large.png)](https://flattr.com/submit/auto?user_id=balupton&url=https://github.com/balupton/history.js&title=History.js&language=&tags=github&category=software)
de8554b @balupton Added Flattr button
authored
5
8d5cacf @balupton Initial Commit
authored
6
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
7 This project is the successor of [jQuery History](http://balupton.com/projects/jquery-history), it aims to:
8d5cacf @balupton Initial Commit
authored
8
bd6ea2f @balupton Fixed some more issues. Mostly HTML4 States initially in HTML5 browsers.
authored
9 - Follow the [HTML5 History API](https://developer.mozilla.org/en/DOM/Manipulating_the_browser_history) as much as possible
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
10 - Provide a cross-compatible experience for all HTML5 Browsers (they all implement the HTML5 History API a little bit differently causing different behaviours and sometimes bugs - History.js fixes this ensuring the experience is as expected / the same / great throughout the HTML5 browsers)
78681ff @balupton updated commit feed link
authored
11 - Provide a backwards-compatible experience for all HTML4 Browsers using a hash-fallback (including continued support for the HTML5 History API's `data`, `title`, `pushState` and `replaceState`) with the option to [remove HTML4 support if it is not right for your application](https://github.com/balupton/history.js/wiki/Intelligent-State-Handling)
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
12 - Provide a forwards-compatible experience for HTML4 States to HTML5 States (so if a hash-fallbacked url is accessed by a HTML5 browser it is naturally transformed into its non-hashed url equivalent)
833fd3a @balupton Fixed a recursion issue with FF3.6. Removed Firebug Lite.
authored
13 - Provide support for as many javascript frameworks as possible via adapters; especially [jQuery](http://jquery.com/), [MooTools](http://mootools.net/), [Prototype](http://www.prototypejs.org/) and [Zepto](http://zeptojs.com/)
c76ef2c @balupton Added graceful upgradation of HTML4 States to HTML5 Browsers... but i…
authored
14
ba466c3 @balupton Now working with prototype.
authored
15
d2028b3 @balupton Added Code Smaple in Documentation.
authored
16 ## Usage
17
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
18 ### Working with History.js:
d2028b3 @balupton Added Code Smaple in Documentation.
authored
19
4cc19a3 @balupton readme updates
authored
20 ``` javascript
21 (function(window,undefined){
22
23 // Prepare
24 var History = window.History; // Note: We are using a capital H instead of a lower h
25 if ( !History.enabled ) {
26 // History.js is disabled for this browser.
27 // This is because we can optionally choose to support HTML4 browsers or not.
28 return false;
29 }
30
31 // Bind to StateChange Event
32 History.Adapter.bind(window,'statechange',function(){ // Note: We are using statechange instead of popstate
33 var State = History.getState(); // Note: We are using History.getState() instead of event.state
34 History.log(State.data, State.title, State.url);
35 });
36
37 // Change our States
38 History.pushState({state:1}, "State 1", "?state=1"); // logs {state:1}, "State 1", "?state=1"
39 History.pushState({state:2}, "State 2", "?state=2"); // logs {state:2}, "State 2", "?state=2"
40 History.replaceState({state:3}, "State 3", "?state=3"); // logs {state:3}, "State 3", "?state=3"
41 History.pushState(null, null, "?state=4"); // logs {}, '', "?state=4"
42 History.back(); // logs {state:3}, "State 3", "?state=3"
43 History.back(); // logs {state:1}, "State 1", "?state=1"
44 History.back(); // logs {}, "Home Page", "?"
45 History.go(2); // logs {state:3}, "State 3", "?state=3"
46
47 })(window);
48 ```
c76ef2c @balupton Added graceful upgradation of HTML4 States to HTML5 Browsers... but i…
authored
49
833fd3a @balupton Fixed a recursion issue with FF3.6. Removed Firebug Lite.
authored
50 To ajaxify your entire website with the HTML5 History API, History.js and jQuery [this snippet of code](https://gist.github.com/854622) is all you need. It's that easy.
51
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
52 ### How would the above operations look in a HTML5 Browser?
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
53
b0edf7a @balupton Fixed readme formatting a bit. Attempt to add a subscribe form.
authored
54 1. www.mysite.com
41928aa @balupton Readme updates. Had some incorrect installation info.
authored
55 1. www.mysite.com/?state=1
56 1. www.mysite.com/?state=2
57 1. www.mysite.com/?state=3
58 1. www.mysite.com/?state=4
59 1. www.mysite.com/?state=3
60 1. www.mysite.com/?state=1
b0edf7a @balupton Fixed readme formatting a bit. Attempt to add a subscribe form.
authored
61 1. www.mysite.com
41928aa @balupton Readme updates. Had some incorrect installation info.
authored
62 1. www.mysite.com/?state=3
b0edf7a @balupton Fixed readme formatting a bit. Attempt to add a subscribe form.
authored
63
78681ff @balupton updated commit feed link
authored
64 > Note: These urls also work in HTML4 browsers and Search Engines. So no need for the hashbang (`#!`) fragment-identifier that google ["recommends"](https://github.com/balupton/history.js/wiki/Intelligent-State-Handling).
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
65
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
66 ### How would they look in a HTML4 Browser?
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
67
b0edf7a @balupton Fixed readme formatting a bit. Attempt to add a subscribe form.
authored
68 1. www.mysite.com
41928aa @balupton Readme updates. Had some incorrect installation info.
authored
69 1. www.mysite.com/#?state=1&_suid=1
70 1. www.mysite.com/#?state=2&_suid=2
71 1. www.mysite.com/#?state=3&_suid=3
72 1. www.mysite.com/#?state=4
73 1. www.mysite.com/#?state=3&_suid=3
74 1. www.mysite.com/#?state=1&_suid=1
b0edf7a @balupton Fixed readme formatting a bit. Attempt to add a subscribe form.
authored
75 1. www.mysite.com
41928aa @balupton Readme updates. Had some incorrect installation info.
authored
76 1. www.mysite.com/#?state=3&_suid=3
b0edf7a @balupton Fixed readme formatting a bit. Attempt to add a subscribe form.
authored
77
28dacb6 @balupton Minor updates to readme. Mostly typos. Also added a 'Giving Support' …
authored
78 > Note 1: These urls also work in HTML5 browsers - we use `replaceState` to transform these HTML4 states into their HTML5 equivalents so the user won't even notice :-)
dc4cc15 @balupton v1.4.0 Release
authored
79 >
9cdcd93 @balupton Recompiled and fixed final bug
authored
80 > Note 2: These urls will be automatically url-encoded in IE6 to prevent certain browser-specific bugs.
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
81 >
78681ff @balupton updated commit feed link
authored
82 > Note 3: Support for HTML4 browsers (this hash fallback) is optional [- why supporting HTML4 browsers could be either good or bad based on my app's use cases](https://github.com/balupton/history.js/wiki/Intelligent-State-Handling)
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
83
ca86372 @balupton Changed _state to _suid. Updated readme.
authored
84 ### What's the deal with the SUIDs used in the HTML4 States?
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
85
ca86372 @balupton Changed _state to _suid. Updated readme.
authored
86 - SUIDs (State Unique Identifiers) are used when we utilise a `title` and/or `data` in our state. Adding a SUID allows us to associate particular states with data and titles while keeping the urls as simple as possible (don't worry it's all tested, working and a lot smarter than I'm making it out to be).
87 - If you aren't utilising `title` or `data` then we don't even include a SUID (as there is no need for it) - as seen by State 4 above :-)
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
88 - We also shrink the urls to make sure that the smallest url will be used. For instance we will adjust `http://www.mysite.com/#http://www.mysite.com/projects/History.js` to become `http://www.mysite.com/#/projects/History.js` automatically. (again tested, working, and smarter).
89 - It works with domains, subdomains, subdirectories, whatever - doesn't matter where you put it. It's smart.
41928aa @balupton Readme updates. Had some incorrect installation info.
authored
90 - Safari 5 will also have a SUID appended to the URL, it is entirely transparent but just a visible side-effect. It is required to fix a bug with Safari 5.
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
91
bc79c00 @balupton Fixed demo/test. Updated readme. Added note to .htaccess. Demo is now…
authored
92 ### Is there a working demo?
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
93
519ed6e @balupton Updated readme a bit more.
authored
94 - Sure is, give it a download and navigate to the demo directory in your browser :-)
41928aa @balupton Readme updates. Had some incorrect installation info.
authored
95 - If you are after something a bit more adventurous than a end-user demo, open up the tests directory in your browser and editor - it'll rock your world and show all the vast use cases that History.js supports.
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
96
97
98 ## Download & Installation
f2ac286 @balupton First version complete.
authored
99
30d3ca1 @balupton readme updates
authored
100 - Download History.js and upload it to your webserver. Download links: [tar.gz](https://github.com/balupton/history.js/tarball/master) or [zip](https://github.com/balupton/history.js/zipball/master)
f2ac286 @balupton First version complete.
authored
101
30d3ca1 @balupton readme updates
authored
102 - Include History.js
f2ac286 @balupton First version complete.
authored
103
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
104 - For [jQuery](http://jquery.com/) v1.3+
f2ac286 @balupton First version complete.
authored
105
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
106 ``` html
107 <script src="http://www.yourwebsite.com/history.js/scripts/bundled/html4+html5/jquery.history.js"></script>
108 ```
703124e @balupton v1.7 beta. Need to test properly.
authored
109
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
110 - For [Mootools](http://mootools.net/) v1.3+
703124e @balupton v1.7 beta. Need to test properly.
authored
111
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
112 ``` html
113 <script src="http://www.yourwebsite.com/history.js/scripts/bundled/html4+html5/mootools.history.js"></script>
114 ```
f2ac286 @balupton First version complete.
authored
115
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
116 - For [Right.js](http://rightjs.org/) v2.2+
f2ac286 @balupton First version complete.
authored
117
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
118 ``` html
119 <script src="http://www.yourwebsite.com/history.js/scripts/bundled/html4+html5/right.history.js"></script>
120 ```
3263e7e @balupton Moved the changelog into the History.md file
authored
121
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
122 - For [Zepto](http://zeptojs.com/) v0.5+
f2ac286 @balupton First version complete.
authored
123
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
124 ``` html
125 <script src="http://www.yourwebsite.com/history.js/scripts/bundled/html4+html5/zepto.history.js"></script>
126 ```
f2ac286 @balupton First version complete.
authored
127
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
128 - For everything else
f2ac286 @balupton First version complete.
authored
129
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
130 ``` html
131 <script src="http://www.yourwebsite.com/history.js/scripts/bundled/html4+html5/native.history.js"></script>
132 ```
f2ac286 @balupton First version complete.
authored
133
de822d6 @balupton typo
authored
134 > Note: If you want to only support HTML5 Browsers and not HTML4 Browsers (so no hash fallback support) then just change the `/html4+html5/` part in the urls to just `/html5/`. [Why supporting HTML4 browsers could be either good or bad based on my app's use cases](https://github.com/balupton/history.js/wiki/Intelligent-State-Handling)
f2ac286 @balupton First version complete.
authored
135
136
7e77d25 @balupton readme updates
authored
137 ## Get Updates
04697ac @balupton v1.4.1 - Added HTML5 Supported for Safari 5 and Safari iOS 4.2.1
authored
138
139 - For Commit RSS/Atom Updates:
78681ff @balupton updated commit feed link
authored
140 - You can subscribe via the [GitHub Commit Atom Feed](http://feeds.feedburner.com/historyjs)
44f2857 @balupton Readme updates mostly on compatibility.
authored
141 - For GitHub News Feed Updates:
78681ff @balupton updated commit feed link
authored
142 - You can click the "watch" button up the top right of History.js's [GitHub Project Page](https://github.com/balupton/history.js)
04697ac @balupton v1.4.1 - Added HTML5 Supported for Safari 5 and Safari iOS 4.2.1
authored
143
144
7e77d25 @balupton readme updates
authored
145 ## Get Support
55ce2b7 @balupton readme updates
authored
146
00184fe @balupton readme updates
authored
147 - History.js is maintained by people like you. If you find a bug, report it to the [GitHub Issue Tracker](https://github.com/balupton/history.js/issues). If you've fixed a bug submit a [Pull Request](https://github.com/balupton/history.js/pulls) and add your fork to the [Network Wiki Page](https://github.com/balupton/history.js/wiki/Network).
02dcc4c @balupton Added support section to readme.
authored
148
d0699a7 @balupton readme updates
authored
149 - If you would like paid support and trainings, or have job offers, then refer to the [Network Wiki Page](https://github.com/balupton/history.js/wiki/Network). If you are qualified with History.js, then be sure to add your details to that page too.
02dcc4c @balupton Added support section to readme.
authored
150
00184fe @balupton readme updates
authored
151 - If you're company use History.js on your projects, and would like to see it grow and prosper (better documentation, bugfixes, upgrades, maintenance, etc.) and would love to become a corporate sponsor then do email sponsor@bevry.me
02dcc4c @balupton Added support section to readme.
authored
152
00184fe @balupton readme updates
authored
153 - If you would like free support for History.js, then [post your question](http://stackoverflow.com/questions/ask) on [Stackoverflow](http://stackoverflow.com/about) and be sure to use the `history.js` tag when asking your question.
28dacb6 @balupton Minor updates to readme. Mostly typos. Also added a 'Giving Support' …
authored
154
00184fe @balupton readme updates
authored
155 - If you've created a website that uses History.js, or know of one. Then be sure to add it to the [Showcase Wiki Page](https://github.com/balupton/history.js/wiki/Showcase).
28dacb6 @balupton Minor updates to readme. Mostly typos. Also added a 'Giving Support' …
authored
156
7c9d3ed @balupton readme updates
authored
157 - If you'd love to +1 or like this project, then be sure to tweet about it and click the "watch" button up the top of its [Project Page](https://github.com/balupton/history.js).
00184fe @balupton readme updates
authored
158
159 - For anything else, refer to the [History.js GitHub Wiki Site](https://github.com/balupton/history.js/wiki).
28dacb6 @balupton Minor updates to readme. Mostly typos. Also added a 'Giving Support' …
authored
160
55ce2b7 @balupton readme updates
authored
161 Thanks! every bit of help really does make a difference!
28dacb6 @balupton Minor updates to readme. Mostly typos. Also added a 'Giving Support' …
authored
162
163
f4e3f60 @balupton Cleaned files. Improved documentation.
authored
164 ## Browsers: Tested and Working In
ba466c3 @balupton Now working with prototype.
authored
165
f4e3f60 @balupton Cleaned files. Improved documentation.
authored
166 ### HTML5 Browsers
167
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
168 - Firefox 4+
169 - Chrome 8+
170 - Opera 11.5
171 - Safari 5.0+
172 - Safari iOS 4.3+
f4e3f60 @balupton Cleaned files. Improved documentation.
authored
173
174 ### HTML4 Browsers
88c3212 @balupton Lots more working.
authored
175
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
176 - IE 6, 7, 8, 9
88c3212 @balupton Lots more working.
authored
177 - Firefox 3
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
178 - Opera 10, 11.0
330416f @balupton Added some more demos. Fixed safari bug replaceState bug. Now need to…
authored
179 - Safari 4
3818f02 @balupton Made good progress. Building completed. Just needs testing now.
authored
180 - Safari iOS 4.2, 4.1, 4.0, 3.2
f2ac286 @balupton First version complete.
authored
181
182
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
183 ## Exposed API
184
185 ### Functions
186
a9ccf1d @balupton Typos.
authored
187 - `History.pushState(data,title,url)` <br/> Pushes a new state to the browser; `data` can be null or an object, `title` can be null or a string, `url` must be a string
188 - `History.replaceState(data,title,url)` <br/> Replaces the existing state with a new state to the browser; `data` can be null or an object, `title` can be null or a string, `url` must be a string
189 - `History.getState()` <br/> Gets the current state of the browser, returns an object with `data`, `title` and `url`
190 - `History.getHash()` <br/> Gets the current hash of the browser
f4e3f60 @balupton Cleaned files. Improved documentation.
authored
191 - `History.Adapter.bind(element,event,callback)` <br/> A framework independent event binder, you may either use this or your framework's native event binder.
192 - `History.Adapter.trigger(element,event)` <br/> A framework independent event trigger, you may either use this or your framework's native event trigger.
193 - `History.Adapter.onDomLoad(callback)` <br/> A framework independent onDomLoad binder, you may either use this or your framework's native onDomLoad binder.
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
194 - `History.back()` <br/> Go back once through the history (same as hitting the browser's back button)
195 - `History.forward()` <br/> Go forward once through the history (same as hitting the browser's forward button)
196 - `History.go(X)` <br/> If X is negative go back through history X times, if X is positive go forwards through history X times
197 - `History.log(...)` <br/> Logs messages to the console, the log element, and fallbacks to alert if neither of those two exist
198 - `History.debug(...)` <br/> Same as `History.log` but only runs if `History.debug.enable === true`
199
200 ### Events
201
14d196b @balupton Attempted to add a YUI adapter, failing miserably.
authored
202 - `window.onstatechange` <br/> Fired when the state of the page changes (does not include hash changes)
09127ba @balupton Cleaned documentation, a few other things. Not ready yet as some test…
authored
203 - `window.onanchorchange` <br/> Fired when the anchor of the page changes (does not include state hashes)
204
205
7529b35 @balupton Fixed Google Chrome issue. Now have to retest in HTML4 Browsers.
authored
206 ## Notes on Compatibility
207
fdfefac @balupton v1.6 preparation. Removed initial statechange fire. Added some url ut…
authored
208 - History.js **solves** the following browser bugs:
330416f @balupton Added some more demos. Fixed safari bug replaceState bug. Now need to…
authored
209 - HTML5 Browsers
14d196b @balupton Attempted to add a YUI adapter, failing miserably.
authored
210 - Chrome 8 sometimes does not contain the correct state data when traversing back to the initial state
ca86372 @balupton Changed _state to _suid. Updated readme.
authored
211 - Safari 5, Safari iOS 4 and Firefox 3 and 4 do not fire the `onhashchange` event when the page is loaded with a hash
330416f @balupton Added some more demos. Fixed safari bug replaceState bug. Now need to…
authored
212 - Safari 5 and Safari iOS 4 do not fire the `onpopstate` event when the hash has changed unlike the other browsers
213 - Safari 5 and Safari iOS 4 fail to return to the correct state once a hash is replaced by a `replaceState` call / [bug report](https://bugs.webkit.org/show_bug.cgi?id=56249)
214 - Safari 5 and Safari iOS 4 sometimes fail to apply the state change under busy conditions / [bug report](https://bugs.webkit.org/show_bug.cgi?id=42940)
215 - Google Chrome 8,9,10 and Firefox 4 prior to the RC will always fire `onpopstate` once the page has loaded / [change recommendation](http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/)
216 - Safari iOS 4.0, 4.1, 4.2 have a working HTML5 History API - although the actual back buttons of the browsers do not work, therefore we treat them as HTML4 browsers
9276538 @balupton Cleaned code up. Still a few bits left to document. Fixed state data …
authored
217 - None of the HTML5 browsers actually utilise the `title` argument to the `pushState` and `replaceState` calls
330416f @balupton Added some more demos. Fixed safari bug replaceState bug. Now need to…
authored
218 - HTML4 Browsers
9276538 @balupton Cleaned code up. Still a few bits left to document. Fixed state data …
authored
219 - Old browsers like MSIE 6,7 and Firefox 2 do not have a `onhashchange` event
220 - MSIE 6 and 7 sometimes do not apply a hash even it was told to (requiring a second call to the apply function)
330416f @balupton Added some more demos. Fixed safari bug replaceState bug. Now need to…
authored
221 - Non-Opera HTML4 browsers sometimes do not apply the hash when the hash is not `urlencoded`
703124e @balupton v1.7 beta. Need to test properly.
authored
222 - All Browsers
223 - State data and titles do not persist once the site is left and then returned (includes page refreshes)
224 - State titles are never applied to the `document.title`
535d2ad @balupton Updated readme
authored
225 - ReplaceState functionality is emulated in HTML4 browsers by discarding the replaced state, so when the discarded state is accessed it is skipped using the appropriate `History.back()` / `History.forward()` call
833fd3a @balupton Fixed a recursion issue with FF3.6. Removed Firebug Lite.
authored
226 - Data persistance and synchronisation works like so: Every second or so, the SUIDs and URLs of the states will synchronise between the store and the local session. When a new session opens a familiar state (via the SUID or the URL) and it is not found locally then it will attempt to load the last known stored state with that information.
c2c15fa @balupton Fixed url encoding issue.
authored
227 - URLs will be unescaped to the maximum, so for instance the URL `?key=a%20b%252c` will become `?key=a b c`. This is to ensure consistency between browser url encodings.
833fd3a @balupton Fixed a recursion issue with FF3.6. Removed Firebug Lite.
authored
228 - Changing the hash of the page causes `onpopstate` to fire (this is expected/standard functionality). To ensure correct compatibility between HTML5 and HTML4 browsers the following events have been created:
14d196b @balupton Attempted to add a YUI adapter, failing miserably.
authored
229 - `window.onstatechange`: this is the same as the `onpopstate` event except it does not fire for traditional anchors
230 - `window.onanchorchange`: this is the same as the `onhashchange` event except it does not fire for states
8b30581 @balupton Minor fix. Updated readme to talk about Opera 11 issue under load.
authored
231 - Known Issues
833fd3a @balupton Fixed a recursion issue with FF3.6. Removed Firebug Lite.
authored
232 - Opera 11 fails to create history entries when under stressful loads (events fire perfectly, just the history events fail) - there is nothing we can do about this
233 - Mercury iOS fails to apply url changes (hashes and HTML5 History API states) - there is nothing we can do about this
7529b35 @balupton Fixed Google Chrome issue. Now have to retest in HTML4 Browsers.
authored
234
f2ac286 @balupton First version complete.
authored
235
3263e7e @balupton Moved the changelog into the History.md file
authored
236
237 ## History
238
239 You can discover the history inside the [History.md](https://github.com/balupton/history.js/blob/master/History.md#files) file
240
55ce2b7 @balupton readme updates
authored
241
242 ## License
243
244 Licensed under the [New BSD License](http://opensource.org/licenses/BSD-3-Clause)
245 <br/>Copyright &copy; 2011-2012 [Benjamin Arthur Lupton](http://balupton.com)
Something went wrong with that request. Please try again.