summaryrefslogtreecommitdiff
path: root/desktop/Extension_test-passive.mk
AgeCommit message (Collapse)Author
2018-06-13Add some help content to test-passive.oxtStephan Bergmann
...mainly to test how well/poorly extension help is supported by --with-help=html, but also as a kind of reference implementation. (There are also extensions in odk/examples/ that contain help content, namely odk/examples/DevelopersGuide/Extensions/DialogWithHelp/ containing context- sensitive help for a dialog, a topic that is not covered here.) See <https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/ Help_Content#Integration_into_the_OpenOffice.org_help_system> for the ways an extension's help content can be integrated into the "classic" (plain --with-help) help system (citing sub-section headings used in that document): * Help Viewer Contents page: The contained help.tree provides a "The test-passive Extension" section with a "The test-passive Extension" page (main.xhp). * Help Viewer Index page: The contained main.xhp provides index entries for "test-passive extension" and "extensions"-"test-passive", and---only on the index pages of Calc and Writer ---for "test-passive extension in Calc and Writer". * Help Viewer Find page: The contained main.xhp is indexer="include", so it should be found by e.g. searching for "bla bla". * Context sensitive help and extended tool tips: The contained Addons.xcu has been extended with a small (floating by default) toolbar containing a "native" button (doing the same as the "passive - native" menu entry), and the contained main.xhp provides an extended tooltip of "Show the test-passive extension's native dialog" for that toolbar button (displayed when using "Help - What's This?" and hovering over the button). For context-sensitive help for dialogs, see the mention of odk/examples/DevelopersGuide/Extensions/DialogWithHelp/ above. The contained help is only provided in "en" localization, which should thus be used as fallback regardless for which locale LO is run. The help-related XML files need to provide identifiers in lots of places, many of which appear to be unused for the given example uses. I specified those as empty strings. The workdir/Extension/test-passive.oxt extension can be built with `make Extension_test-passive`. Change-Id: I0e75f35df85683c9fae1d1384fa6afeaeb8a687d Reviewed-on: https://gerrit.libreoffice.org/55736 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2013-10-25stop looking for Jar files in solverMichael Stahl
Change-Id: I4d2a93fa7395354fbf2893df9e254ab39fa365af
2013-10-11do not copy testing extensions to instdirDavid Tardon
Change-Id: Ibd2f18a8998b3e182d8d5b8af9c9f74a8ac00744
2013-03-07Gbuild'ify desktop/test/deployment/passive/Stephan Bergmann
...to manually build solver/*/bin/test-passive.oxt via "make Extension_test-passive". There's still room for improvement in gbuild, though: * There should be no need to add the extension's native library and jar UNO components (which nothing else links againts) to the central Repository.mk. * There should be no need to move manifest.xml around. * There should be no need to move .java files around. * Let "make Extension_test-passive.clean" clean up again. Change-Id: Ib44558061c4c0fda6be5943bd02b5a42cd15c52e