To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=63706 Issue #:|63706 Summary:|request for new operation oor:op=fuse Component:|framework Version:|OOo 2.0 Platform:|All URL:| OS/Version:|All Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|ENHANCEMENT Priority:|P3 Subcomponent:|code Assigned to:|sb Reported by:|as
------- Additional comments from [EMAIL PROTECTED] Tue Mar 28 02:51:20 -0800 2006 ------- Currently the DTD of our configuration format describes the following operations (as xml attributes oor:op=<...>): modify, replace, remove, reset. But in combination with AddOn's it's not quite useable. Because the creator of an AddOn has to know if the underlying configuration layer already has an entry which must be "replaced" or not (then it's must be "modified"). So the creator of an AddOn cant do the right things. As a "workaround" for these, most often the operation "replace" is used. But then it can happen that different AddOn's (changing the same configuration path) will run into conflicts. And it's not clear which of these AddOn's win ... because our PackageManager does not allow to specify an order for installation of AddOn's. So we need a solution to make it possible to "add or modify but not replace" configuration entries also. Please use the attached ZIP files to install it using Tools- >PackageManager. The attached basic macro can be used then to show the merged configuration entries as they are visible at the configuration API at runtime. As a result of this fix both jobs (Job_1 and Job_2) must be visible. Optional it would be nice if this is also true for all events used inside this example. But it's a must for the events "onFirstVisibleTask" / "onUnknownEvent_1". We need an implementation of "fuse" as it's described already on "http://util.openoffice. org/common/configuration/oor-document-format.html". --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
