[dojo-contributors] Dojo 1.9 Proposal
neonstalwart at gmail.com
Wed Oct 31 11:24:26 EDT 2012
i took a look over this and the main comment i have is that i don't think this is ready for core. i don't think that it even belongs in core but for the sake of argument let's say that it's appropriate for core... then i'd say that we still probably need to give this some time in some applications before we commit to the API. it won't hurt to let it simmer for a little while especially since browsers are only just starting to fully support this.
back to whether or not it's suitable for core… if we were to give it some time to incubate then that would need to be somewhere (of course) so why not make that somewhere be the permanent home for a new project and let it have a life outside of core? this is the kind of thing that could even be used by people who don't use dojo (yet).
On Oct 24, 2012, at 3:48 PM, Kitson Kelly wrote:
> For anyone interested, I committed my first cut of IndexedDB: https://github.com/kitsonk/dojo/blob/webstorage/store/IndexedDB.js
> It isn't complete yet (doesn't support any sort of query), but it was a bit more complicated than I anticipated, mostly due to the async nature of the API. I convert the different requests to promises, which works quite well. Also because the API has a "ObjectStore" on top of a "Database" that made things slightly more complex. Coupled with the fact there is still a significant API difference between Chrome 11-22 and Firefox, it was all a bit not straight forward to normalise it. Chrome 23 finally matches the Firefox API, but it was still frustrating getting the basic add/put/get/delete functionality working on both browsers.
> I am still thinking something like "Sync" will be the mechanism to "wrap" a Memory store and local persistent storage.
> dojo-contributors mailing list
> dojo-contributors at mail.dojotoolkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dojo-contributors