To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110129
------- Additional comments from pulsi...@openoffice.org Mon Mar 15 13:36:15 +0000 2010 ------- As long as configmgr has a private C++ interface, it cannot be replaced by another UNO component. That of course is the whole point of the UNO framework on which OOo is built and that was used by the former configmgr. It would not be difficult to implement the new functions as an UNO service that is accessed through the UNO service registry (services.rdb), and that would bring the new configmgr on par with the former implementation, which as I mentioned, has been in OOo since v1.1.0. I would also like to request that all of the directory paths used by the new configmgr be put back into variables in the configmgrrc file. This would include all of the paths configmgr searches for .xcd, .xcu and .xcs files, as well as the location where user data is stored. The hard-coding of the paths is a step backward from implementation that was in OOo from v1.0 to up to the latest v3.2 release, and it no doubt had little effect on performance. It again makes OOo less usable by downstream developers and users with non-standard environments. Yes, I do have a particular usage scenario in mind: trying to integrate a custom backend with the new configmgr. This backend was implemented in the manner described by joerg.barfu...@sun.com in the post I linked to above. It has run fine under every version of OOo since v2.0 but does not work with the new configmgr as it is currently implemented in CWS sb111. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org