Reworking of dialogues Organize macros (make from 5 existing only one).
Today we have four+one dialogues for manage of macros in LibreOffice. You can find it in menu Tools->Macros->Organize macros (plus one from dialogue Tools->Macros->Organize macros->LibreOffice Basic, in it need push button "Organizer" for opening dialogue "LO Basic Macros Organizer").
Problem with existings situation:
1. Dialogue Tools->Macros->Organize macros->LibreOffice Basic don't allow organize library/modules/dialogues/macroses, it needs open additional dialogue for it.
2. There are five dialogues for organize macroses instead one (a-la one Template manager dialogue with some filters for all modules of LibreOffice).
4. Users don't see in one place all macroses if they were wrote on different programming languages.
In my variant I offer make one dialogue (see attach), that allows organize library/modules/dialogues/macroses and run/edit/associate macroses in one window for all four supported macros programming languages.
All libraries (with its modules/dialogues/macroses) on different programming languages will be show in one tree in left side of dialogue. But it need highlight it with different icons or color.
Steps to Reproduce:
1. try organize your macroses uses existing dialogues in LibreOffice
there are five dialogues for organize your macroses in LibreOffice
there is only one dialogue, that will allow make all organize operations for macroses
User Profile Reset: No
Created attachment 145778 [details]
New dialogue Macros Organizer
I appreciate a rework of those dialogs. But you need to be very careful that nothing is lost.
Currently LibreOffice has:
.uno:RunMacro (title "Macro Selector") shows _all_ available macros, regardless of the language, and has a field to show a description of the macro.
.uno:ScriptOrganizer distributes to the before mentioned dialogs.
.uno:MacroOrganizer is only for Basic. It has no "Run", but it allows, to copy/move modules per drag&drop between libraries. That is very useful, if you will put some macros into a document.
To consider beyond what your image shows: How to handle other languages? Drag&Drop of modules. Descriptions of macros. Easy repeated access to the same macro. Does it affects the API?
(In reply to Regina Henschel from comment #2)
> I appreciate a rework of those dialogs. But you need to be very careful that
> nothing is lost.
> To consider beyond what your image shows:
>How to handle other languages?
All library on all languages will be allow in one tree area in left side of dialogue
> Drag&Drop of modules.
It needs realize in tree area, as it is now in dialogue "LO Basic Macros Organizer"
>Descriptions of macros.
what do you mean? User's decriptions?
>Easy repeated access to the same macro.
repeat access to the same macro where?
>Does it affects the API?
I don't know =(
(In reply to Roman Kuznetsov from comment #3)
> (In reply to Regina Henschel from comment #2)
> >Descriptions of macros.
> what do you mean? User's decriptions?
Descriptions made by the macro author. You can see such descriptions for example in "ExportSheetsToHMTL", "HelloWorld", "Highlight", "MemoryUsage" for the Beanshell-macros. You get the dialog, which has this, if you use "Run Macro" or shortcut Alt+F11.
> >Easy repeated access to the same macro.
> repeat access to the same macro where?
If you use the dialog "LibreOffice Basic Macros" and fold out a module and run a macro, the next time you use the dialog, the same module is folded out and you can click on the macro immediately and run it. If you use the above mentioned "Run macro", the next time you use the dialog, all libraries are folded up. You first need to fold out the library, then fold out the module and then you can select the desired macro. That is cumbersome.
> >Does it affects the API?
> I don't know =(
I neither. I don't know whether these dialogs can be reused by a macro author for own content, or whether their exists a method in the API, which uses these dialogs. At least, the existing dialogs are connected to uno-commands and thus can be called via dispatcher in any external macro.
*** Bug 141975 has been marked as a duplicate of this bug. ***