Ignore macros

Comments

13 comments

  • Avatar
    K15t Support Team

     

    Hi Yann,

    • {scroll-ignore} is actually a macro, which you can use to wrap content, which you want to be ignored by Scroll (Office).
    • the 'scroll-ignore' labels are not processed currently.  I have opened an issue, and I will discuss tomorrow, whether we can include this as a last minute fix in Scroll Office 2.0.1 (actually due tomorrow.)

    -Stefan

    0
    Comment actions Permalink
  • Avatar
    Yann

    Ok, cool for this new release! (BTW, what are the confluence version supported? We tried to install it on our confluence 3.0.2 and that doesn"t seem to work)

    What about the {wiki-ignore} macro for scroll office?

    Yann.

    0
    Comment actions Permalink
  • Avatar
    Yann

    Ok for the version, this is indicated on the attlassian plugin exchange page, thanks.

    0
    Comment actions Permalink
  • Avatar
    K15t Support Team

    Hi Yann,

    we just discussed this internally and decided NOT to include scroll-ignore as a default ignore.  Instead, you can define an exclusion on export by specifying ^scroll-ignore  (see attached screenshot).

    We decided so, as we want to avoid to implement implicit logic not obvious to (new) users.

    WRT {wiki-ignore} i am not sure what you mean. I have not seen this before.  Is that a user macro?

    -Stefan

     

    PS: Scroll Office should work on Scroll 3.0.2 (just tested it locally). What error are you getting?




    10064_Screen+shot+2010-08-06+at+8.56.37+AM.png
    0
    Comment actions Permalink
  • Avatar
    Yann

    Hi Stefan,

     

    Thanks for the quick responses! I love support with great reactivity :)

    Ok for the management of the labels, seems to be good like that (the only things I ask myself is why the two plugins have different behaviour with the labels and the scroll-ignore one mostly?)

    And {wiki-ignore}, yes it's a macro brings by scroll wiki exporter. This comes from your documentation:

    "

    Scroll comes with two predefined semantics scroll-ignore and wiki-ignore. Using these semantics you can define if the annotated content is displayed as regular content of your exported document or even rendered in the wiki.

    • scroll-ignore: hides content from being rendered in the export
    • wiki-ignore: hides content from being rendered in wiki

    "

     

    Yann.

    0
    Comment actions Permalink
  • Avatar
    Yann

    Just one remark: it would be good to make the export settings available during a whole session, to "save" them in fact.

    Because for the moment, user have to type everytime his parameters (choose the template, write the label he doesn't work to export etc)

    Yann.

    0
    Comment actions Permalink
  • Avatar
    Yann

    I made this remark to quickly... In fact, every parameters are saved but the "This page and all children with label" text input.

    Can you also kepp this parameter?

     

    Thanks,

    Yann.

    0
    Comment actions Permalink
  • Avatar
    K15t Support Team

    Hi Yann,

    yes you are right - your quoted text refers to the {annotation} macro which is part of Scroll Wiki Exporter. There you had the option to use a wiki-ignore semantic. In the new versions we will use annotations only to express real semantics.

    However we still support the concept of hiding content from being rendered in the wiki. We call it {scroll-only} which is basically the opposite of the {scroll-ignore} macro.

     

    - Tobias

    0
    Comment actions Permalink
  • Avatar
    Yann

    Okay, that sounds great! :)

     

    For the other subject, the compatibility, I will open a new thread because it seems that wa have many problems to deploy scroll office.

    We think that we have conflicts with one of our plugin (https://plugins.atlassian.com/plugin/details/20346), we're still analysing and I'll inform you.

     

    Thanks again,

    Yann.

    0
    Comment actions Permalink
  • Avatar
    K15t Support Team

    Regarding saving the settings. I already created an issue for this in our JIRA. I am not sure if we manage to get this included in the release today - but definitely in the next one.

    0
    Comment actions Permalink
  • Avatar
    Yann

    Ok, no worries.

    Thanks guys.

    0
    Comment actions Permalink
  • Avatar
    Yann

    Is it possible to get your jira url?

    0
    Comment actions Permalink
  • Avatar
    K15t Support Team

    Here it is: http://k15t.jira.com/ (respectively http://k15t.jira.com/browse/OFCE-51)

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk