The idea is the same as Hash.Cookie. In fact, I used the same trick Hash.Cookie uses to add the Hash.prototype methods, since extending Hash via mutators is not possible. The providers are: ie, swiff, html5session, html5local, whatwg_db and gears. The way things are, I don't think adding window.name support is even worth it.
http://github.com/Guille/moogets/tree/master/Hash.Persistent/Hash.Persistent.js On Thu, Oct 2, 2008 at 2:52 PM, nutron <[EMAIL PROTECTED]> wrote: > I'm interested. All these methods are attached to a specific window? Are > they more persistent than specific windows or sessions? > > > On Thu, Oct 2, 2008 at 10:38 AM, Guillermo Rauch < > [EMAIL > PROTECTED]<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=1134506&i=0> > > wrote: > >> Oh, and I also think there're better ways to achieve permanent storage >> than window.name. Ideally, the script should check if others are >> available first. >> I have some work done on this... my script checks for the availability of >> the HTML5 storage method, WhatWG database, SQlite, Gears, >> MSIE proprietary storage, etc. If anyone is interested, poke me. >> >> -- >> Guillermo Rauch >> http://devthought.com >> > > The MooTools Tutorial: www.mootorial.com CNET Clientside: > clientside.cnet.com > > ------------------------------ > View this message in context: Re: Element Storage on > window.name<http://n2.nabble.com/Element-Storage-on-window.name-tp1131513p1134506.html> > Sent from the MooTools Users mailing list > archive<http://n2.nabble.com/MooTools-Users-f660466.html>at Nabble.com. > -- Guillermo Rauch http://devthought.com
