Apache OpenOffice (AOO) Bugzilla – Issue 87264
resource Ids used in wizards
Last modified: 2017-05-20 11:33:30 UTC
following up issue 87245: the java wizards seem to use resource Ids from at least svtools by their direct numerical id. This breaks as soon as someone changes the Id in svtools since he does not know that the wizards depend on that Id but cannot include svtools.hrc I think a better approach than to use the direct values would be to use a c++ program that can include svtools.hrc and then creates a java import file that can be used by the wizards.
pl->bc: if you're not the owner of the wizards anymore, please send this on to the new owner.
@mba: please dispatch appropriately
Hey cool, someone already found the bug that broke my build some weeks ago. :-) Silly me - I just forgot about that. Perhaps instead of polluting the build we should solve that at runtime by providing a UNO service that provides resource IDs.
polluting the product instead ?
Not really. The generated output would be included in the product also, as a java library. I think that adding a small C++ file implementing the UNO service won't add more to our build. It does not need to be a UNO service, but that would be the most simple implementation. And it would be usable anywhere where UNO can be used, not only in Java applications.
Usable ? This would be a service, that translates local resource IDs of a wizard into numbers (aka global resource IDs) which would the be passed to the UNO service that actually loads the resource (as it already does). I think that is not really a good concept and in fact would not be reusable at all.
No; here we have the case that the wizard reuses a string resource that is already defined and used elsewhere. This string is kind of a part of the "interface" of the svtools library. If there was an "svtools" object, I would make that string a part of its interface. As such an object doesn't exist, why not creating one? If that string was only made for the wizard, there would't be a reason to put that string into the svtools resource.
Reset assigne to the default "issues@openoffice.apache.org".