Expand Text User Macro

Is this possible (adding the expand functionality around the child page listing)?

doh! cloak and toggle-cloak macros even hehe

speaking of which, is there any way to get the toggle macro to "fold" to the side?

Good idea. Would you document that above as an alternative installation method Version 1.2?

What happens when a user deletes your JS, not knowing what it is?

he he. I think I already submitted "include this macro in content formatting macros" or "composition plugin" as either a comment on your page, or a feature request... I think it fits extremely well in either of those plugins.

• if you do override the {expand} macro, please do me two favours
  • maintain the parameters (you can extend them, but maintain what is there for backward compatibility)
  • keep it light-weight in implementation: I'm not sure why, but the way that 'cloak' was implemented was much slower when you had 50+ expand tabs on a page.
  • keep it light-weight in syntax: i.e. do not require using {composition-setup}, or having to define both a cloak trigger and cloak block. Those are very handy features in advanced pages, but this 'expand' is easier for beginners to understand and use.

Updated source above so as to NOT conflict with attachments macro anymore

Thanks Guy!

• Thanks. That seems like a good suggestion. I haven't noticed any problems with the current version, however.

• The images were carried over from the original version, as I only added the backwards compatible rendering script, added anchors and fixed up the parameters

• Would you please make the appropriate changes and release a v1.3 in the page source above?

How do you bold the titles? The only way I could do it was to bold the entire block, which will bold the bullets of course.

*{expand:bold}
reg
- test
- test
{expand}*

this did not work, because we don't 'render' the title

{expand:*bold*}
reg
- test
- test
{expand}

and this did not work because of the logic of the confluence rendering engine

*{expand:bold}*
reg
- test
- test
{expand}

• If this is how you do it, instead of a 'bug report' this would be a 'feature request' to 'allow wiki syntax formatting in the title'. - currently not supported, but could be done given the code above.

• if you want to 'hard code' the title to be bold, you should be able to update this text (near the bottom of the script):

  <expand-title style="vertical-align: middle">$generalUtil.htmlEncode($expandtitle)</expand-title></

with something like this:

<expand-title style="vertical-align: middle"><b>$generalUtil.htmlEncode($expandtitle)</b></expand-title></

or

<expand-title style="vertical-align: middle;font-weight:bold;"><b>$generalUtil.htmlEncode($expandtitle)</b></expand-title></

1) good idea. Can't think of any issues with this. Have you tested it on your own server? if so, go ahead and modify and document the code to reflect this.
2) good idea. What version of confluence was the $!body versus $body feature introduced? If was introduced recently, just use an #if($body)$body)#end instead.
3) re: splitting that JS from the expand macro: beginner users don't often 'get' split macros like that. for that type of macro, see the 'composition plugin', I think. A better way would be to just add a 'includejavascript=[true]/false' parameter that 'optimizers' can put the 'false' value, but the basic 'expand' will always work for novice users.

Excellent enhancement idea. I'd like to use that too! Please contribute it when you find an answer

• if you could simply detect if you are in preview mode, then at least, you could render all the expand macros expanded by default.
• have the authors of the composition plugin or content-formatting plugin created a java version yet? if so, you might want to see if they've been able to make it 'preview friendly'.