Visual Preview / Smart Context Edit question

mikeb

We are in the process of upgrading from Teamsite 5.5 to 6.5 and are going to be using the Visual Preview (Smart Context) functionality. We have not used this functionality before and we have some very strict requirements regarding which buttons / functionality will appear based on user permissions or on the actual page / file that is being viewed. So I'm wondering, Is there a way to limit the display of buttons based on something other than NT level permissions, or regex's in iw.cfg?

For example, we would like to remove the edit button functionality from the visualpreview bar on a news page of a site (a static ASP page), but not the homepage of the site (a Teamsite templated page). We would like to do this by reading the extended attributes of the respective files and either removing the button or "greying-out" the button if the user should not have the ability to edit the file.

I've had no problem using the NT permission value to "gray-out" the edit button, and likewise no issues in doing branch / directory regex's in iw.cfg, and while this simplified example can be done with these methods, we have some other parts of the site where we would like to base the visual preview bar's buttons on the extended attributes (or something similar).

Any thoughts would be greatly appreciated.