Wikiversity:Threaded discussions with NavFrames with subst/20070522105803
--CQ 21:19, 21 May 2007 (UTC)
Re: Is this a precurser to liquid threads? No. 
- 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:
- transclusion/substitution meta:substitution#optional substitution
- The m:magic word REVISIONTIMESTAMP
Grafting /20070519101448 
- Comment: Grafting a thread by JWSchmidt
"Argument:I'm guessing that my comment goes here." , 17:14, 19 May 2007 (UTC)
A one liner may go here. 
Argument: Here we can elaborate....
Here is the point: the REVISIONTIMESTAMP is precisely for that purpose. 
- Argument: BASEPAGENAME/1/1/1/1/1... can only produce a linear structure.
And try not to create your own section. 
- Argument: Use the "reply link" to create a new section, or else you would create a dead end.
I mean, 
My "A one-liner may go here" is a reply to ":I'm guessing that my comment goes here." and "Here is the point: the REVISIONTIMESTAMP is precisely for that purpose." replies "Can there be sections within treads". But that latter section was created articficailly (without pressing the "reply button") and so it hijacked the reply link to the previous comment. Or we can say, two different comments (and two different replies) were merged. That makes the questions and answers crossed. So it is a little confusing.
In short, Don't create your own section. Use the "reply" link. Once you have created a section, you are free to edit your previous comments, correct mistakes, etc.
IF you find this text too small 
go to a subthread by pressing the edit button.
Problem fixed by reintroducing a thread 
- Comment: See above.
Testing the easier preload 
Testing preloadeasy, take 2 
- Comment:variable fixed, and the reply link fixed. Any problems?
testing preload easy, take 3 
- Comment: problems?
so far so good... 
- Comment: so far so good
Can we include a line break in the "Comment=" ? 
- Comment: Line break:->
What about pretext tag? 
This above all, to thine own self be true, And it must follow, as the night the day, Thou canst not then be false to any man.
We may also use subsection headers to clarify the threadings 
such as this 
All threads are created equal 
- Comment: This suggestion is not advisable. All threads are created equal
the test 
We can track new threads with category! This is a thread on 20070604. 
- Comment: This is a thread on 20070604.
We really can track new threads with category! 
- Comment: Fforgot in the previous comment: didn't add the category in /preloadeasy. One should use /preload.
perhaps not too effectively, when a node has many subnodes... See category:threads 20070604 
But it is still okay; just check the time stamp on each reply... 
- Comment: For example, from category:threads 20070604 -->Wikiversity:Threaded_discussions_with_NavFrames_with_subst/20070522105803 --> look through the time stamps --> find the thread "We really can track new threads with category! " with time stamp 20070604063208.
And, of course, if the flow is sufficiently big, we may even use categorytree. 
- Comment: To use the mw:extension:CategoryTree, we need to have the category created in the first place.
Not quite; Categorytree doesn't take a dynamical variable ... 
- Comment: (
Now it does: CategoryTree can now be used as a parser function and can take arguments. 
This is a response test 
- Comments: Testing a response
--220.127.116.11 01:48, 9 October 2008 (UTC)
Again, Just Testing what the headline can do.... 
Exactly. If you have a short comment, just put it on the headline.