On 19 Sep 2018, at 14:47, Adel Atallah <[email protected]> wrote:
On Wed, Jul 18, 2018 at 5:00 PM Vincent Massol <[email protected]> wrote:
On 5 Jul 2018, at 12:06, Vincent Massol <[email protected]> wrote:
On 4 Jul 2018, at 12:07, Thomas Mortagne <[email protected]> wrote:
Here are more details on the actual use case we need to support:
In include/Display macro either you set:
* "reference" and "type" (which default to DOCUMENT) * or you set “page"
Globally I think we need to add 3 concepts to macro parameter descriptor:
1) The concept of “deprecated” parameter. For example for “document” in the include macro. 2) The concept of aliases or groups, i.e the ability to list parameters that are mutually exclusive. Example: reference + type vs page for display/include macros. This would mean that in the Macro Dialog UI if you select one of those the other gets unselected/cleared out (you cannot have mutually exclusive params have values). 3) The concept of Advanced parameters. For example, we should put reference + type as advanced parameters so that they are not shown to the user by default (and so that the page parameter is more highlighted). Users would need to click on Advanced to see advanced parameters. I think we’re doing something automatic today (I don’t remember the details) to try to hide some parameters but we should probably review this.
WDYT?
Ping!
Do we agree about this? If we do we can then create jira issue about it and take it for implementation.
+1, I can create the jira issue if it's ok.
Please do :) @Marius: Ok for you? thanks -Vincent [snip]