Here are the examples for all the browsers
http://nparashuram.com/ttd/IndexedDB/index.html.
On you second point, the delay is actually due to the wait function
where I check for the availability of a variable before running the
function. For example, objectStore is dependent on open() call, and
this dependency is handled using a setTimeout and checking for
variables.
On Apr 26, 9:44 pm, Eric Bidelman <
ericbidel...@chromium.org> wrote:
> This is really fantastic! There's nothing else out there like this and
> hardly any examples.
> Two comments:
>
> - It would be great if the samples worked in both FF and Chrome. I think
> we're at
> a point where both implementations are stabilizing but there could still be
> some
> discrepancies.
>
> - Sometimes when I click run, there's a significant delay when the code is
> executed
> and the output shows in the console. What gives? I'm worried developers
> might get the impression indexedDB is slow.
>
>
>
>
>
>
>
>
>
> On Tue, Apr 26, 2011 at 9:28 AM, axemclion <
n.parashu...@gmail.com> wrote:
> > I was working on some IndexedDB API examples and thought of sharing
> > them with the group.
> > The IndexedDB API playground basically lists the various concepts
> > defined in the specification and has examples for each case.
>
> > It works great with the latest Canary build.
>
> > It is available at
> >
http://nparashuram.com/trialtool/index.html#example=/ttd/IndexedDB/we...
>
> > Would love to hear your feedback on this.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Chromium HTML5" group.
> > To post to this group, send email to
chromium-ht...@chromium.org.
> > To unsubscribe from this group, send email to
> >
chromium-html5+unsubscr...@chromium.org.
>
e.bidel...@google.com