With cookies the selected state of the Twisty is remembered the next time the Twisty is shown.
I would, but:
- TwistyContrib is installed by default for PatternSkin, not TwistyPlugin
Why do you need a dedicated TwistyContrib
? If there's no indispensable reason for it then
do everything just with the TwistyPlugin
. Most will install both anyway.
Besides, I'd love to have a PersistentSessionVarsPlugin
that stores session variables into
in the user topic. That would enable some nice stuff, but only for things that
are stored within the session object.
New item: Item814.
Where does the session come into play?
Just in case you are not aware of session objects: (skip if you already know)
The session object is the store for a user's session state. He knows which session object belongs to
him by a cookie that stores a sesson id - an integer which is sent to the browser. If this user comes
back TWiki gets the session id and retrieves the session object belonging to it and everything that
is stored in it. You can arbitrary amount of data in one session object and still only send one cookie
to the browser. Thereby session info is stored on the server vs. on the client in its cookie jar.
So if the user clicks on a Twisty link a session variable is created to store the Twisty state. Note, that
the session object stores key-value-pairs. To store the Twisty state you have to construct a reasonable
key taking the page location and the twisty-id on the page into account which you should have done
with no communication to the server while changing the Twisty state.
The server never notices that the user is twisting html. Now I understand what this Twisty is all about. /me paddles backwards.