Fixing Livelink HTML file Publishing

Esam_Al_Dakheel_(tiikbaseAdmin_(Delete)_2175388)

I don't know if anyone else has tackled this 'problem', it is more to do with aesthetics than anything. But I do feel it to be important.BACKGROUND:Many of my colleagues and myself tend to use MS FrontPage to write internal documents; user guides, technical documentation, and so on. The HTML file format is preferential to MS Office files for a number of reasons:- Size; the HTML files are smaller by far.- Web publishing; with HTML files 'what you see is what you get', where as web published MS Office files do not generally look the same as their native format.- Interactive; HTML files end up far more interactive within the context of the browser. Especially when long hyperlinks are inherent in the document. For example user guides relating to Livelink can literally aid the user to complete the specific task they are reading about.THE PROBLEM:As I see it Livelink does not publish HTML files in the same way its publishes other file types.When Livelink publishes none-HTML files the page is constructed in such a way as to present the Livelink titles, menus, functions, the footer that contains version information, around the requested file, before being passed to the browser.However when Livelink publishes HTML files they are passed directly to the browser. The standard Livelink Intranet page is not constructed.As a result you loose all of the Livelink menus and functions, forcing the user to click the 'Back' button if they wish to continue using Livelink in its proper fashion.SUPPOSITION:I know the code exists within Livelink to publish HTML files properly, take for example the custom.html files: these are published with all the usual Livelink menu's and functions.As I see it all that needs to be done in the OSpace is hijack the code used to publish the custom.html file and force Livelink to use this code in relation to any HTML file it passes to the browser. Hence guaranteeing the availability of the standard Intranet functionality.SUMMARY:As yet I have not had the time to delve into the OSpace and tackle this issue myself. If anyone has done this then please mail me: ed@tiikwt.com.If no one has tackled this then perhaps the developers at OpenText may like the idea enough to make the change in a future version (come on guys, its not a lot of coding!!) If this is not to be the case either, then watch this space and I'll get around to it myself.Comments please....Regards,Ed MarsdenThe International InvestorKuwait

John_Rizzo_(fedinvestadmin_-_(deleted))

Well, one way around your problem (though it is definitely not the full scale answer you are looking for) is to copy the html generated by livelink for the header and footer and place it within the html documents you plan to put into the system. You will have to cut out some of the navigation, such as the dropdown folder hierarchy list, but you will at least be able to keep the look and feel the same. Also, you could add some custom javascripting that will let users move back through the history without necessarily having to hit the back button. Just a thought...