[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110129 User sb changed the following: What|Old value |New value CC|'brinzing,kendy' |'brinzing,kendy,sb' Assigned to|sb|pulsifer --- Additional comments from s...@openoffice.org Fri May 14 08:39:34 + 2010 --- "new configmgr have a purely UNO interface": issue 110491 "I'm willing to do": so passing this issue back to you for now - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
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 Tue Mar 23 00:54:38 + 2010 --- After studying this issue for some time, it looks to me fairly straightforward to pull an additional configuration layer into the new configmgr. There are a few related problems I see though: (1) how to notify the configmgr that the data in an external layer has changed (would the external layer be polled, and if so, when?); (2) what would the configmgr do when the external layer has changed (does the entire config data tree need to be rebuilt, or just part of it, or can the rebuild begin with an intermediary result?); and (3) would property change notifications be sent to listeners when data changes in an external layer, and if so, how? My thought is that these issues require some experimentation, and at this point, early in the v3.3 release cycle, I'm willing to do that, try to figure out what will work best, and potentially offer some patch sets or further feedback. I would still like to see the new configmgr have a purely UNO interface though, so it would be easier to extend. - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110129 User sb changed the following: What|Old value |New value Ever confirmed| |1 Status|UNCONFIRMED |NEW Priority|P1|P2 --- Additional comments from s...@openoffice.org Wed Mar 17 09:19:39 + 2010 --- @pulsifer: I'm afraid there is no quick and easy way to bring back the feature of hooking additional backends into the current configmgr. I see two possible ways ahead: 1 Replacing the C++ dependency between configmgr and extension manager with an (unstable, for now) UNO interface would indeed be easy. It would enable replacing all the configmgr service implementations with your own implementations of those services. I am not sure this is what you want to do, though (you do not currently do this, right?). 2 Designing the missing functionality into the new configmgr (using mechanisms that are as close as reasonably possible to the old mechanisms). For this, it would be necessary that you provide a description of the exact services/interfaces you used, and how you modified the configmgr ini file. - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110129 User kendy changed the following: What|Old value |New value CC|'brinzing'|'brinzing,kendy' - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110129 User brinzing changed the following: What|Old value |New value CC|''|'brinzing' --- Additional comments from brinz...@openoffice.org Tue Mar 16 07:24:23 + 2010 --- . - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
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 14:52:19 + 2010 --- >> "As long as configmgr has a private C++ interface, it cannot be replaced >> by another UNO component." > I assume this is only of theoretical interest, right? This is not a theoretical interest. We would use this mechanism to implement our our custom configuration layer, the one we have been using with OOo since v2.0. (The oor:external mechanism you added to the new configmgr is not sufficient for our purposes.) This would be simple change in the new configmgr, and would bring it back on par with the configmgr that has been in OOo since v1.1.0, which was an UNO component with a pure UNO interface. - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
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 s...@openoffice.org Mon Mar 15 14:18:23 + 2010 --- @pulsifer: Out of curiosity, what does your additional backend do? ("As long as configmgr has a private C++ interface, it cannot be replaced by another UNO component." I assume this is only of theoretical interest, right?) - 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
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 + 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
[framework-issues] [Issue 110129] configmgr no longer uses ini file and backend UNO API
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110129 User sb changed the following: What|Old value |New value Summary|implement new configmgr as|configmgr no longer uses i | an UNO service |ni file and backend UNO AP | |I --- Additional comments from s...@openoffice.org Mon Mar 15 12:11:34 + 2010 --- What the new configmgr implementation indeed no longer supports are the configmgr ini file in the basis program directory and the ability to hook in additional backends. I was not aware that any client code used those features, so took the liberty to drop them for simpler and potentially more efficient code. The new configmgr still is a UNO component, however (I adapted this issue's summary accordingly). The private C++ interface between configmgr and the extensions manager is an implementation detail; I see no need to revise it. @pulsifer: Do you have any specific usage scenarios that are broken now? - 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