Also, some questions on transactions.

- Is there a way in the API to say that perform a write and another operation in hte same transaction ?

- What happens if one tab deletes is doing a version transaction deleting an object store while the other writes to that store ? Standard errors, right ?

I really like the LINQ syntax! A nice, human-readable way of retrieving data.

Your questions:
1. Yes, store creation happens in a VERSION_CHANGE transaction.
2. Yes, getAll returns an Array. FF already has a non-standard impl of getAll, in Chrome I do iterate over all stored entries. So, yeah, if the data is huge, this is going to be an intense operation Iteration is in the making and will be there for the second part of this tutorial; you can have a sneak peek at the iterate() method in the develop branch of IDBWrapper on GitHub.
3. Index functionality will also be covered in part two, but you can already check it out in the develop branch.
4. Yes, get() and getAll() use a READ_ONLY transaction, other methods READ_WRITE. iterate() will probably offer both depending on a flag you can set, defaulting to READ_ONLY, as most ppl won’t need write access in cursors.

1. When a store does not exist and I do a new IDBStore, and then store it, does it all happen in the VERSION_CHANGE transaction

2. When getting all items, all data seems to be in an array. What if the amount of data is huge ? Why not have an iterator like syntax?

3. Noticed that Index functionality is not available. Any specific reason for that.

4. What is the default transaction type you use for get vs store ? Do you explicitly change from READ to READ_WRITE ?

Since IndexedDB does not have a querying language, I thought of writing one up –
Demo: http://nparashuram.com/IndexedDB/LINQ/index.html
Blog: http://blog.nparashuram.com/2011/04/linq-on-indexeddb.html

Let me know what you think of the API ..

Initially I thought I wouldn’t be able to show this project to anybody at all – but it was exactly your post about the TF2 level that opened my eyes that at least a video is possible

About the culling: Right now, there’s no culling at all. Mostly because I still have no clear idea of how to do it… I’m not sure if GLGE removes anything that’s behind the “fog-clipping”, but I don’t really think so, as the world currently is one huge mesh.

And for the capture I used IShowU, which is pretty easy to use, I can recommend it.

Thanks again, glad you liked it!

A clarification on the post, if you don’t mind: Are you doing no visibility culling at all, or only missing the portal culling? With environments that large I’d imagine that you’d have to be culling something, or you’d start thrashing video memory pretty badly.

Finally: What are you using for the video capture? I’ve gotten knocked on my demos several times because the captures make them look jittery. Yours is nice and smooth, though.

(Oh, and I feel your pain on the Mouse Lock thing. It can’t possibly come soon enough!)

Great job again, and I’ll be following this project closely!

Thanks for the pointer True, read and write actions via dot notation work fine in all browsers supporting localStorage, and advising against it might be a little too strong. Still I can’t find the IDL that describes this, and, what’s more important, using dot notation might leave the impression that localStorage is just an object like any other – but it isn’t.

So just for the sake of clarity and code readability, I’d still go for the “API” methods

1. Nothing happens.
2. Limit reached on saving 2560kb. Stored 2048.
3. Fails on #49, and iPhone asks for storing more than 5MB and 25MB.
4. Works for 8064 kb and I was too lazy to tap more…