Apache OpenOffice (AOO) Bugzilla – Issue 68892
add automatic HelpIDs to extensions
Last modified: 2017-05-20 11:31:36 UTC
For automated testing every GUI Element needs a HelpId. To ease finding unique HelpIDs they should be changed to aplhanumeric IDs and each UI Element should get an automatic HelpID, as it is done in VCL already. These should contain the “unique identifiers“ mentioned by Stephan Bergmann, the name of the Dialog and the name of the UI Element as mentioned in the XML file describing the Dialog. If necessary for uniqueness the type of the UI Element might also be included (as in VCL)
assign to AB
sdded cd
Grrr
STARTED, Target Milestone OOo 2.0.4 is surely unrealistic. Set to OOo 2.x for now.
set target to 2.1 since we need it asap
ab->gh: Sorry, but the discription is far too unclear. If I remember correctly from our discussion the changes in Basic and concerning the DialogProvider should be based on a new functionality provided by the AWT dialog API. There has to be a separate task for this (-> CD who now is responsible for the toolkit). Based on the new AWT functionality it has to be specified what exactly has to be done in the scope of this task. -> back to you for now
assigned to abi as he wants to implemet a solution for this
accepted, but the solution might be different ...
We missed the fature freeze deadline for 2.1 => 2.2
Correlating dialog and help will not be done in 2.2 timeframe
2.3
ABI->AB: As discussed ...
STARTED
ab->gh: Needs to be discussed again. I still don't understand, what / how should be done here. Is there any description or concept? Seems to be unrealistic for 2.3 anyway due to missing resources, -> 2.4 for now
Not UI relevant, it has to be discussed if this should be done at all / for 2.4 and how this impacts the general help handling (e.g. fallback to parent window)
-> 3.x
Reset assigne to the default "issues@openoffice.apache.org".