Hi, With TWclassic we had a transclusion mechanism, that worked with "section headings". eg:
<<tiddler [[tiddlerTitle##sectionHeading]]>> .... this is TWc syntax. In the example belwo <<tiddler [[my-movie##Title]]>> ... would return: Movie Title - bla bla .. With this mechanism, you could transclude parts of 1 tiddler into an other. With this mechanism, users could create a "database-like" structure, using different heading levels. eg my-movie: ! Title Movie Title - bla bla .. ! Description Short info about the movie. !! Actors * Actore A * Actore B * ... ! Details Other stuff, that may be interesting. Using headings, the user could create a structure. If several tiddlers did contain the same heading-structure, this structure was an "intrinsic" database schema. ... Transcluding ##Description would transclude everything until ##Details section starts. ------------------------ The main problem is, that this mechanism is "heavy weight", in terms of performance, since everything has to be calculated during tiddler rendering phase. That's why it was replaced with TW5 DateTiddlers. ... The problem with DataTiddlers [1] is, that JsonTiddlers are NOT convenient to edit for humans AND DictionaryTiddlers can't handle multi-line values. -m [1] https://tiddlywiki.com/#DataTiddlers On Sunday, May 12, 2019 at 11:40:59 AM UTC+2, @TiddlyTweeter wrote: > > Ciao PMario & all > > Regarding the AIM: *to provide ability to have line breaks in fields*. > > I don't understand the underlying architecture. But I understand the need. > > This is a basic example where this utility would add to TidlyWiki and ease > usage. > > Take the case of MOVIES. Each movie is SINGULAR (one & unique). > > -- At the moment if you want to maintain a dataset organised by Movie > Title that includes rich content, including line-breaks, its over > complicated. You have to have several Tiddlers per Movie as soon as you > include lines breaks. A simple example is ACTORS. Say you have 35 actors in > a movie. Is that 35 fields? 35 Actor Tiddlers? Or *better* 1 field with > 35 lines? > > > -- A "Movie" is a good example of a referenced object that is a whole. It > does not need to be spread over multiple Tiddlers. Currently for richer > data you have to (over)break it down. > > > -- One might argue a solution here is to emulate a relational database via > JSON structures. But actually, I think complex (tree-nested) JSON is > unnecessarily complex for the specific USE CASE. > > > -- The Use Case Supposition (with good reason) is one-movie is one-thing. > A movie is one object... Even IF George Clooney appears in 13 other movies, > when I'm looking at the record for one movie I could still link to Clooney > but I think over-spawning "actor-tiddlers" would pretty soon ruin a TW's > utility in over-complexity. > > > --- > > *Crucial point*. In my usage I want to send students ONE Tiddler per > movie so they can easily import it. Its needs to have a way to include line > breaks in fields so that I can include Plot, Logline, Actor Field & Crew, > all as a unit. Other routes get far too complicated. > > Just thoughts > Josiah > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/5bbb870e-53d3-42a0-a557-6eb67d0a3109%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
