Hi Yakov, Well, in principle this can be done, sure. I'm not sure about adding this > to the core, though: while I don't use definition lists much, >
My point entirely: Why not? To me, definitions are exactly the natural way to display terms and their corresponding definitions. I understand that having this by default will end up identifying more slices than before, so it could be something similar to Erics Core Tweaks... http://tiddlytools.com/#CoreTweaks > I'm mostly concerned with another two issues: concatenating autoaggregated > and manually written lists/tables and manual sorting of such things so that > sort order is remembered [in a cookie]) What's the overall idea? > The overall idea of GetPlugin really was just to do some playing around with a different kind of transclusion, one that doesn't only give you the value but also the key, so that you don't have to write... !A Section <<tiddler "SomeTiddler##A Section">> but just... <<get SomeTiddler:##A Section'>> A bit like sunyit's poptiddler macro... http://sunyit-pos262-webcampaigning2012.tiddlyspace.com/#UsingPopTiddler which simplifies the slider macro to simply do... <<poptiddler "Name Of Tiddler" "Text to display">> Really? Doesn't work for me (TW 2.6.5) and shouldn't: slicesRE doesn't > account regexps of formatters anyhow.. I mean > > foo: bar //italic bar > more italic bar// > > <<tiddler [[New Tiddler::foo]]>> > > shows what I expected: > > foo: bar italic bar > more italic bar > > bar italic bar > You are right, I neglected the fact that I need to wrap the parameter properly, which I have added to section "Using Slices" here: http://tiddlywiki.org/#Slices So, after all, what I suspected is true which is that calcAllSlices is quite agnostic to wiki-formatting apart for the bold/italic exceptions for the slice-name. > isn't hard to achieve.. the simplest implementation is to add to the > slicesRE something like.. > > |(?:^;([\'\/]{0,2})~?([\.\w]+)\:\1[\t\x20]*\n\:([^\n]+)[\t\x20]*$) > > So, besides the fact that definitions and their terms seem to be good candidates for stuff that can be computationally retrieved, multi-line content being *supported for definitions* is the second main the argument for extending slice support to definition lists. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 http://groups.google.com/group/tiddlywikidev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
