Adrian, Your example may not depend on another component but is did depend on a file that was outside of the OFBiz app control and broke when that file changed. This will never happen in the proposed solution. All files for a webapp are generated from a single docbook file so there are no external dependencies.
You can have external links in the webhelp files and there are examples in the current upload. In the solution each locale has it's own file and would point to an appropriate external reference for that locale. Naturally if that external reference changes the link will break. I searched the trunk for http in *UiLabels.xml and there are 120 matches. I found only one of them that references more then one locale (CommonUiLabels.xml CommonLookupAnywhoLink), so as a practical matter this is a solution that has not been used very much. Help in the proposed system is at the webapp level. UiLabels are more (and I would argue too) fine grained for screen level context help. UI labels can be used any where pointing to any thing. It would be very hard to maintain a coherent help system using all the fragmented files that could spring from labels. This is not to say that there is not a place for labels in cases like CommonLookupAnywhoLink. The two mechanisms can co-exist but I think they serve different purposes. A system like webhelp is better suited for creating help documents for which it was designed while UiLabels were designed for the purpose of providing i18n support for lables. Tom -- View this message in context: http://ofbiz.135035.n4.nabble.com/OFBIZ-4941-tp4637418p4637442.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
