Hey mate, seems we are trying to accomplish the same thing :)

[balupton]

Hey Fortes,

Author of the other History.js here ;-) Seems we are both trying to accomplish the same things. Working on this stuff is my day job, so I've been able to dedicate a lot of hours to my History.js and it handles a whole series of use cases that haven't been covered yet in yours:

• Allows people to bind as much as they like to a state change
• IE6, IE7 compatibility
• Support for traditional anchors not firing states - required to ensure that the history trail remains the same for HTML5 and HTML4 browsers
• A google chrome issue with data being kept when going back to the home page

I'll be spending today and tomorrow working on it some more - as I'd like to add data persistance to all browsers, better unit tests, and queuing of events. Eventually this will replace my jQuery History project used in jQuery Ajaxy - my primary product.

I'd be happy to have a chat with you about it - you can reach me on skype with username balupton - as perhaps we can merge our efforts :)

[rc1]

It is very confusing having two similar named projects (this projects shows first in google).

[balupton]

@rc1 yeah google's ranking algorithms are very strange, especially considering the amount of downloads and followers the projects are getting:

• Fortes: https://github.com/fortes/history.js/graphs/traffic
• Balupton: https://github.com/balupton/history.js/graphs/traffic

I will be sorting out the SEO issue soon enough :-)

[balupton]

@fortes is there any chance of having this project removed as it is now maintained in your treesaver project https://github.com/Treesaver/treesaver/blob/master/src/lib/history.js and not here?

[marsgoonbars]

where's that google "+1" when you need it, lol.