Wikiversity:Threaded discussions with NavFrames with subst/20070521200237

Which parts do you find complicated? We can probably hide them.

20070521200704

• Comment: This is experimental. We can hide the scary wikitext with { { { SUBST: } } }

  )

--Hillgentleman|Talk 20:07, 21 May 2007 (UTC)

• reply[1]

What links here

Your previous comment is here /20070519174254.

20070521201312

• Comment: It lies in a deep thread.

That is one drawback of auto-collapsing. Anybody good with .js may try to see if it is possible to make an "expand all" button. For the moment, let us stay on topic. --Hillgentleman|Talk 20:13, 21 May 2007 (UTC)

• reply[2]

What links here

To play this game, simply reply to the exact comment with the reply button under it.

20070521202742

• Comment: Then the threads will sort themselves out.

Threaded discussions tell us: Clearly, human communication is complex. --Hillgentleman|Talk 20:27, 21 May 2007 (UTC)

• reply[3]

20070521211912

• Comment: Is this a precurser to liquidThreads ??? -- CQ 21:19, 21 May 2007 (UTC)

--CQ 21:19, 21 May 2007 (UTC)

• reply[4]

Re: Is this a precurser to liquid threads? No.

20070521213744

• Comment: I don't know what "liquid" means. This is a simple (see the text at /preload) and flexible model of threaded discussion. It is flexible because it is basically a set of pages, indexed by REVISIONTIMESTAMP, transcluded in a tree-like manner. The techniques used here are:

1. transclusion/substitution meta:substitution#optional substitution
2. preload
3. NavFrame
4. The m:magic word REVISIONTIMESTAMP

--Hillgentleman|Talk 21:37, 21 May 2007 (UTC)

• reply[5]

What links here

What links here

What links here