On Mon, 16 Apr 2007, Patrick R. Michaud wrote:

The reason for having a static and dynamic part is that I'd like to be able to generate a trail of pages like this (the names of the pages are completely arbitrary, I just used 'Page<n>' due to lack of imagination)

        * [[Page 1]]
        * [[Page 2]]
        ** [[Page 2a]]
        (:pagelist ???? :)  - results in some pages
        * [[Page 10]]
        * [[Page 11]]
        ** (:pagelist ???? :) - pages that should be listed here

        * [[Page ...]]

        (:pagelist <the-rest>:) - any pages not listed above

This would let me use the trail index page to impose order on the pages
that belong to the wiki trail, and still use (:pagelist:) to make sure
that the trail contains all the pages.

Is the above possible?

Not yet, but I'm planning to make it possible via a
trail=-TrailPage option to (:pagelist:).  This would exclude
all of the pages on TrailPage.

Either that or we'd go with the save/include/exclude mechanism discussed in a previous thread, that would allow arbitrary combinations of pagelists.

Ok. The important thing for me was really to explain the user case.

cheers
/Christian

--
Christian Ridderström, +46-8-768 39 44               http://www.md.kth.se/~chr
_______________________________________________
pmwiki-users mailing list
[email protected]
http://www.pmichaud.com/mailman/listinfo/pmwiki-users

Reply via email to