Jeremy; The title is a unique key. If you want to address tiddlers by a non-unique > key then you’d use a field. >
I can see how we could use a tiddler name as a tablename, and within that use fieldnames as unique keys, and the value without polluting the tiddlername space. However to do this effectively It would be nice if we could hide the fields defined in such tiddlers such that they do not pollute the field name list when clicking on the drop down. This could replace the datatiddler model but faces the same problem if you want each record to contain multiple columns. I can also see now how we could have $:/tablename/records/tiddlerkeyvalue when this tiddlers fields are the columns in a record/row called "tiddlerkeyvalue". The lookup operator helps with this but perhaps it could be extended to permit the provision of a fieldname so we can retrieve more than the text field, effectively additional columns. Are you saying that you’d like TW5 to have better interop with existing > JSON files and APIs? I think Joshua is exploring the approach of extending > the existing data tiddler mechanism. In some of my own work I have explored > a different approach, “exploding” JSON documents into multiple tiddlers, > where each tiddler represents a node of the document. It’s one of many > incomplete plugins that I must get around to releasing. I expect my own work and Joshua's will achieve what I am looking for here. You suggestion would be interesting if applicable to other JSON data (rather than just tiddlers) as I kind of have the tiddler handling (See recent post of mine here). I’m not sure I’m following your exact meaning, but it sounds like you want > TW5 to behave more like a database. Yes and no, I just want to insure there is not data structure that tiddlywiki can not represent. But of course it is already in many ways a database. I’m not sure what you mean by namespaces, but some of what you’re > describing sounds like the plugin mechanism. Perhaps if I understood that more? Now I see the operation of Import more closely. Namespaces are like just as $:/ is treated one way the possibility of having other tiddler prefixes with other qualities. For example tablename, or even username. Perhaps where they can be searched for by their caption. Maybe you’re talking about something like TiddlyWeb’s “bag” model of > storage? We have considered implementing that model within TW5 itself, > whereby the store would be a list of independent bags. Maybe I do not know enough about bags. Some discussions about bags scared me off tw5 for a while in the early days. Fortunately there is not too much conversation about this today :) I have no desire to influence the core or standard distribution unless there are well demonstrated reasons. As suggested above perhaps the extent of this is; - The lookup operator extended to permit the provision of a field name - A way to use WidgetMessage: tm-import-tiddlers such that it does not destroy the import tiddler (or any JSON file with tiddlers) Regards Tony -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/3a11a1c4-00ab-4cd6-8a3b-acaff7a19143%40googlegroups.com.
