Minor suggestion - replace the shade and hide functions
with a snippet of javascript and CSS trickery so you don't
have a page refresh.
In banging this out for Sloan I came across some architectural issues in the portal system. The details are here:
https://openacs.org/forums/message-view?message_id=284093
I propose a few approaches to tracking the client side shade state and am trying to determine the impact on existing installations.
I'd like to make these changes before rolling the Sloan code up to production, in other words ASAP, and would greatly appreciate your feedback.
