Thanks Mario. A hierarchical structure of tags that you described should work for my purposes. I'll need to be able to distinguish between a tiddler that is a tag (used for categorization) and a tiddler that isn't a tag (used for content). I suppose I could do this with a naming convention, as tags are supposed to begin with lower-case, but do you know of other ways? I could use the "tagging" filter, but if a given tag doesn't happen to be tagging tiddlers at a given moment, it seems that it would indicate that it isn't a tag. Hope that makes sense.
Thoughts? Jim On Tuesday, December 3, 2013 1:32:56 PM UTC-5, PMario wrote: > > Hi Jim, > > I think what you describe is the standard TW tagging mechanism. > > eg: > > - if you create a tiddler named "task" .. and > - several tiddlers eg: > - "Go to Mordor" > - "Get the Ring" > - tag those tiddlers as "task" > > What you get is a "parent" child relation between "task" = "parent" and > "Go .." / "Get .." = "children" > > I'm using those examples, because you can find exactly that at > http://five.tiddlywiki.com > So you can open it and see the stuff described below. > > If you open the tiddler "Go to Mordor" you can see, that it is tagged > "task" ... > If you click the "task" pill, > - You can see all other tiddlers tagged with "task" > > If you open the "task" tiddler > - click the (i) info button > - open the "Tagging" tab ... you'll see all tiddlers that are tagged > with "task" > > IMO the mechanism is, (almost) what you described. ... But I think the > implementation is different, to what you expect. ... because > > The "tagging" list is created at runtime. > So if you click the "tagging" tab, the TW core searches for all tiddlers > that are tagged "task" ... the tiddler named "task" doesn't contain a field > "tagging" or in your case "children". > > IMO adding "parent" and "children" fields (or RDF tiddlers) can be done. > But there is a whole lot of "syncing problems" that will pop up. Every time > you rename / create / update / delete / import / export ... a tiddler, > you'll need to check all tiddlers and keep them in sync. Exactly at that > point you create a "real database" behaviour. ... and databases are kind of > complicated, highly optimized beasts. ... > > I think a similar usecase was introduced by Leo at a hangout #19 [1]. > IMO if we need a real database behaviour, we should use a real database. > May be the storage is not so important, but I think the query language to > retrive the data is ... and TW is no database, even if it is quite close :) > > After the hangout 19 I did stumble upon ArangoDB [2] which imo would be a > nice backend for TW5. It supports tiddlers out of the box (key-value store) > and it would be possible to create "real" graph indexes with a graph query > language. > > @Jeremy, > Did you know ArangoDB? > > have fun! > mario > > [1] http://www.youtube.com/watch?v=wYaFsOzXnPY#t=509 > [2] http://www.arangodb.org/ > > > > > > > > > > > > > > -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
