Just offhand, I'd still use cookies, just in a slightly different way.
The thing google does is, it saves the user account settings into a
database, then saves a cookie with a session ID. the database keeps
session IDs, linked to the user table, which can then link to a settings
table. All of this, of course, would require a back end that'd store the
positions, probably via AJAX calls (reposition an element, close it,
whatever).
Likely, use a default settings record, then they can override on an
element-by-element basis. What are you using for a back end?
- Toby
Trekmp wrote:
Thanks to both of you for your advice. I'm not just wanting to store
if an element is open/closed, I need to be able to do something like
google where I can move objects around and remember where they are and
what their status is (open/closed). I'm no javascript programmer so
is it possible you can elborate some more with regards to the cookies,
using jquery, setting and reading. When would be the best time to set
the cookie for the objects.
Many thanks again for your help
On Apr 17, 7:08 pm, "Benjamin Sterling"
<[EMAIL PROTECTED]> wrote:
Piggie backing off of what Rafael said, you can take the params for each
thing and put that in a cookie and when you do you $(document).ready, have a
function that looks at the cookie and gets the params.
Say you have a menu that the user wants hidden:
menuParams:hidden;
and when you come in to the page, it looks for the menuParams and sees if it
is set and what the value is.
--
Benjamin Sterlinghttp://www.KenzoMedia.comhttp://www.KenzoHosting.com
