Hello all,

I wish to first apologize, since I haven't kept up with reading the -users mailing list (I have 140 messages unread in my AxKit-Users IMAP folder. !!) so if something concerning this has already been brought up, please slap me with a wet flounder...

Anyway, I'm doing more work on Callisto CMS (yay!) and am working on a StyleChooser module that'll integrate with my BasicSession XSP taglib. The idea being you can choose a style based on the value of a session key (either a default or a key passed in using PerlSetEnv, so different directories/locations can have their own style keys).

The thing I would *really* like to implement is a pass-thru StyleChooser. Let me explain.

I would like to be able to set my style session key using another StyleChooser. So, I can go to "/index.xml", which will be loaded with the default style (#default). If I load "/index.xml?style=printable" using the QueryString StyleChooser, this will both set the preferred_style and will also automagically set the session key to that value, so the next time you load "/index.xml", it'll load with the "printable" style.

What I was thinking would be to define Apache::AxKit::StyleChooser::BasicSession as the last in the plugin list, and check to see if preferred_style is already set; if so, then I set my session to the value of preferred_style, and "return DECLINED;". Would this work? I have too much work on my plate right now to go of and test that, so I was hoping if someone more familiar with the StyleChooser system could tell me if this is feasible?

I'd really rather not have to introduce XSP code just to support persistent user styles.

Anyway, back to the grind stone.

-man
Michael A Nachbaur


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to