Community
Participate
Working Groups
Must convert the places where we're using cookies to persist settings to use the Preferences API instead. To do: - saved searches - favorites - splitter state in coding.html
Previous discussion: 1.Mark MacDonald Nov 19, 2010 11:56 A.M. The first 2 items have been fixed, but the 3rd raises the issue of how to handle Dojo widgets, which currently rely on cookies to store all their state. If we want to use these widgets for our UI, we need to save their settings to the user's preference store instead. Forcing every widget to manage asynchronous communication with the preference store is probably not the right answer. (Among other things, it means they couldn't work offline). Instead we should have a "local storage" layer which gets saved to the preference store when the server is available. Reads/writes to the local store could happen instantly, so replacing dojo.cookie() with localstore calls would be straightforward. However, this means save conflicts could arise between the local store and the preferences, so we should think about that.
This depends on preference work Simon is doing in M6.
We're likely to have nearly exactly what Mark describes for M6 however I haven't been looking at the cookies case. Instead more focused on default and user preferences for storing plugins. I'm going to defer to m7 for now.
(In reply to Mark Macdonald from comment #0) > Must convert the places where we're using cookies to persist settings to use > the Preferences API instead. > To do: > - saved searches > - favorites > - splitter state in coding.html This work has been completed.
