Just the other day, I hacked up an implementation of transient ZMI bookmarks. It puts an icon next to an object's breadcrumb path that stuffs the path into a session variable, then uses javascript to reload the menu pane. If there are any bookmarks in the session variable, they are listed below the folder tree in the menu pane as links to manage_workspace of that path. So, you click on the little add-a-bookmark icon and a bookmark appears under the folder tree. I showed it to my designer/wife, and she loved it. Then I explained that the bookmarks are kept in a session, so they go *poof* when you restart Zope or your browser. She said "so, make them permanent". Easier said than done, of course. As soon as I started down that path, I got analysis paralysis thinking about bookmark sets, user properties, special bookmark containers, etc, etc. Now, I'm hoping that someone on the list has a clever idea for making these bookmarks persist, in a usefully Zopish way, that doesn't involve dragging in whole other frameworks (i.e. a third-party User Folder implementation). Any thoughts? Cheers, Evan @ 4-am
Evan Simpson wrote:
Just the other day, I hacked up an implementation of transient ZMI bookmarks. It puts an icon next to an object's breadcrumb path that stuffs the path into a session variable, then uses javascript to reload the menu pane. If there are any bookmarks in the session variable, they are listed below the folder tree in the menu pane as links to manage_workspace of that path.
So, you click on the little add-a-bookmark icon and a bookmark appears under the folder tree. I showed it to my designer/wife, and she loved it. Then I explained that the bookmarks are kept in a session, so they go *poof* when you restart Zope or your browser. She said "so, make them permanent".
Easier said than done, of course. As soon as I started down that path, I got analysis paralysis thinking about bookmark sets, user properties, special bookmark containers, etc, etc.
Now, I'm hoping that someone on the list has a clever idea for making these bookmarks persist, in a usefully Zopish way, that doesn't involve dragging in whole other frameworks (i.e. a third-party User Folder implementation). Any thoughts?
Cheers,
Evan @ 4-am
Ok, you will have thought of this, but anyway. Why don't you just make the cookie permanent? I.e., don't use sessions and store the whole information in permanent cookies. IIRC, cookies can store at least 4k in size and you can use at least 20 cookies per domain (this is from a rfc about about http state management), so this should be enough. This wouldn't cover the case of users changing browsers, but that also doesn't work today with the row and column prefs (dtpref_rows). Oh, I got an idea. Just add somethink like a bookmark manager, with the possibility to import/export bookmarks, analogous to the ZMI's import/export functionality with .zexp files. Importing this file would cause zope to resend the cookies, making it possible to transfer the whole bunch to other browsers. Btw, I think the idea of bookmarks is quite sweet, although mozillas capability to store groups of tabs into one bookmark is also a nice feature. cheers, oliver
Oh, I got an idea. Just add somethink like a bookmark manager, with the possibility to import/export bookmarks, analogous to the ZMI's import/export functionality with .zexp files. Importing this file would cause zope to resend the cookies, making it possible to transfer the whole bunch to other browsers.
Addendum: Make the bookmark manager folderish and let users store these files with a custom id/title into the bookmark manager. That way users can group bookmarks themselves and decide how they want to do it. And they can change to another set of bookmarks with a mouseclick. As these bookmarks are in no way security relevant and it's debatable if they really should be tied to users, I think it makes no sense to consider bringing a user folder into the game. cheers, oliver
On Tuesday 16 Jul 2002 6:52 pm, Evan Simpson wrote:
Now, I'm hoping that someone on the list has a clever idea for making these bookmarks persist, in a usefully Zopish way, that doesn't involve dragging in whole other frameworks (i.e. a third-party User Folder implementation). Any thoughts?
Its not clever, and its not Zopish, but cookies sound right for the job.
Evan Simpson writes:
... I follow up the idea of others:
* create a BookmarkManager * create a user specific folder in it, when the user adds a bookmark for the first time This is easy, when you have a single user folder. It get's hairy with different user folders scattered aroung, because then user id's need no longer be unique. * ideally, a user would see (and could manage) his and only his bookmarks. This is tricky. The natural way would be a "__bobo_traverse__" hook. But at traversal time, the user is not yet known. It is solvable, when there is a single user folder (force authentication). Otherwise, it is quite difficult. Dieter
participants (4)
-
Dieter Maurer -
Evan Simpson -
Oliver Bleutgen -
Toby Dickenson