XML Skins again

Andrea_Ilari_(DNMMIL011_(Delete)_2335380)

Hello. I'm experimenting with the XmlExport function, transforming it with XSLT.I find all this really great, but I cannot understand if, using this pattern, it is possible to really rebuild the entire LL interface.I mean, when I have, say, a folder shown by XML/XSL, how do I remap the various available functions that a user can perform on a specific item ?To keep things simple, how can I know which functions a user can perform on a document or on a discussion ? Is there a way to get this list of functions, keeping also in mind permission problems ?Hope my question is clear... thanks.

John_Shoun

We have been doing some work with the XML export as well. Hopefully, this will provide some guidance.It may be possible to re-implement the entire LL interface with XSLT, but I don't think that is is worth the trouble. The main benefit we are going for is createing a "read only" interface that provides a web publishing view to the end user. Trying to re-implement all the 'Add Document' and 'Permission Administration' screens would be a huge undertaking (I'm not even sure that it would ultimately be possible.)You can get the ACL list exported along with the user name that issued the request. With this information you can customize the links on the page. There is nothing in the export that defines the valid actions for a given object. You have to build that logic into the XSL that constructs URLs. For example, if a particular LLNODE is a folder then it can be browsed, whereas a document can be fetched, viewed, downloaded.Hope this helps some.