Are you getting them in sets of data 4 at a time, or like a giant listing?
In the basic, set of 4 case, you can use the nth operator like this: <$set name="myList" value="[[tid A]] 234234 [[meta data for tid A]] [[]] "> <$list filter="[enlist<myList>nth[2]]"> Item: <<currentTiddler>><br/> </$list> </$set> The problem is, if you try this, is that empty [[]] field will disappear. This will happen if any of your fields are empty. So you might need to have any fields that could be empty prefixed with some indicator value (e.g. "m:my meta data") and then use the removeprefix operator to present it. I'm also a little nervous that your list might "sort" itself if you apply any other operations first. I'm not sure that the order of the list items is guaranteed for every browser. So you might have to prefix all the fields just to be sure. -- Mark On Sunday, September 16, 2018 at 12:23:55 PM UTC-7, Mat wrote: > > Thanks for reply Mark > > I don't know what you mean by "a list data". Do you mean some type of list >> field? >> > > Typo. I meant a "list of data". To give an example; > > [[tid A]] 234234 [[meta data for tid A]] [[]] > [[tid B]] 546235 [[previous tid had no version but this one does]] [[version > 3.5]] > ... > > So in this case the each "item" has four pieces of information. It is just > a listing of data but what the exact data is *can* be controlled. > > > I don't know what you mean by "wikitext" only. Are you including or >> excluding Widgets? >> > > Yes, all tools provided by TW. This restricition is because I'm pretty > affluent "in TW" but I don't know e.g js. > > > It might help to understand the reasons behind your suggested limitations. >> > > The background is that Jed and I are working on TWederation. The purpose > behind this particular issue is that I want users to get a "pre peek" at > what tiddlers he will import if he decides to use a particular "fetch > filter". So to get this "peek", the user first imports this supposed "list > of data" containing meta-data about the to-be-imported tiddlers. It is the > format of this list that I'm asking about. I will then use this list and > present the data in some nice way. But I am limited to work with this data > using "TW tools" so the list should ideally be in some easy-to-work-with > format. The problem is that if the list is in a format where manipulating > it demands knowledge beyond TW then I, and many other TW users, cannot > easily manipulate its content (due to lack of coding knowlege). However, if > anyone has a good insight or a strong argument for why the list ought to be > formated in some certain way, then I'm happy to hear about it. > > <:-) > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2839c1dd-ef22-4c1d-8353-60db77f2ac33%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
