Moving on to IndexedDB

I’m more or less satisfied with the routing solution I came up with yesterday  based on Director.js so today I’m moving on to the apps IndexedDB store.

Here’s a useful link: http://caniuse.com/#search=IndexedDB

I hadn’t realized that IndexedDB support is currently limited to FF and Chrome. However, reading through the sources and examples for the https://github.com/axemclion/jquery-indexeddb library I plan to use, I see there’s a Javascript shim that allows me to use the IndexedDB API over WebSQL so that I can support also Safari, iPad, etc.

For now, I’m going to make the explicit decision to reduce supported browser set to just current Firefox and Chrome in order to get this project done. The goal isn’t necessary to stand up an application that runs in everyone’s browser. Rather, it’s to make it fundamentally feasible to create complex model datasets. If people turn out to be interested in the concept, then there’s plenty of time to make it work on other browsers. And if not, then who really cares?

Advertisements

About Chris Russell

http://www.chrisrussell.net
This entry was posted in Internet, Open Source, Projects, Software and tagged , , , , . Bookmark the permalink.

2 Responses to Moving on to IndexedDB

  1. I also wrote IndexedDB wrapper (with websql failback) https://bitbucket.org/ytkyaw/ydn-db/wiki/Home If you have time, check out and let me know

  2. Thank you, Yathit! I will definitely take a look!

Comment on this article

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s