Ciao Mr Dragon "There can be no doubt that TW is a really great concept"
TW is NOT a concept. It exists. Titling in TW is a pain in the arse. But that is not a "federation" issue. In the best of worlds every Tiddler would have a unique number so you could title many tiddlers the same. As is it won't work.The title IS the index. Josiah On Sunday, 17 July 2016 01:13:24 UTC+2, Dragon Cotterill wrote: > > This is just a quick list of some of the thoughts following on from > conversations with Mat and Mario at the Pub after the TWEU Meetup. As with > any Pub conversations it is likely that most of these ideas will fall by > the wayside, but some of the ideas have got me thinking and it's worth > getting them logged whilst they are fresh in my mind. > > There can be no doubt that TW is a really great concept. But now that > we're joining them together (by TWederation) we are going to run into some > seriously big road blocks if we're not careful. For example how do we > handle the importing of Tiddlers with the same Title? > I feel that it is very disingenuous to force users to create shared > Tiddlers with different names. At the moment we are doing this by adding > the creators name to the end of the Tiddler's Title. This I feel is a big > mistake. The naming of the Tiddlers should NOT be enforced like this. The > creator should be free to name them however they want. But of course this > throws a spanner in the works when names clash. > > What we need is a unique way of identifying the Tiddler that is visible to > TW, but not necessarily to the users. Pretty much every database system has > a Key or a Unique ID and I think we need the same. > Now I know that Jeremy would say that your should be able to link to the > Tiddler via the Title, and I fully agree. In any given TW the Title is > unique (Shadows not withstanding). So that is the link you would use when > linking to them in a given instance. But when a TW is federated, with the > same name, which "New Tiddler" do you mean? Because they should all be > available. > > I propose that each TW should have a UID. It should be comprised of the > hash of the URL of the TW, and the hash of the date/time when it was > created. And that ID should stay with it for the life of it's existence. > Even if it's federated into a new TW, then the ID stays. The only time it > should gain a new ID is if it was copied, the copy getting a new UID. > > Now when it comes to TWederation, the structure is clear. HASH1 is the > parent. HASH2, HASH3 are children of the parent, HASH4 is the child of > HASH3. Using this it is very clear how the individual tiddlers should be > displayed, now matter what the actual content of them. If a Tiddler is a > reply, then it has a parent. If no parent, it's a top level entry. > Tiddlers change. At present if a federated tiddler is changed, that change > is not propagated (or have misunderstood the workings of TWederation? > Mat?). If a parent tiddler is deleted, what becomes of the orphans? Yes, > there is still much to discuss on this. > > > Now one of the other thoughts I had was in the concept of data Tiddlers. I > know Mario wants to see all the data of any given Tiddler, but that's a > different matter. :) You should be able to have data WITHOUT the concept of > how it should be displayed, but use another Tiddler as the actual layout. > We have the ViewTemplate tiddler, but if you break that down to a smaller > level you can start to build up the Tiddlers to produce stronger concepts. > At present TW is geared around Text components. Title, Text and Tags as > core values (yes I suppose created, modified and change count are other > values too). TW Classic has the Data Plugin ( > http://tiddlywiki.abego-software.de/#DataTiddlerPlugin ) which kind of > uses this concept. TW5 allows you to add further fields relatively easily. > But what if you took it further? > By opening up TW to the concept of data you could really build up > applications. For example a remote weather station server simply outputs a > raw tiddler stream of weather data. You can TWederate that data straight in > to get an idea of rainfall. Others could get the exact same data but be > more concerned with wind speed and direction. Or both. Or temperature. > You would write a macro which would take all of the data and display it > using the layout of another Tiddler. An iteration over that list would give > us a simple table. Another version would format it for feeding into a chart > (HighCharts anyone?) Or a data connector that changes it in some way to > feed into other components (temperature delta over time? Temp vs Rain?) > This would give us an extremely powerful, dashboard like configuration. > > > > As I said, these are just some random thoughts, typed up on a train > journey back to London after the TWEU Meetup. They need refining in so many > ways, but I feel that they may have some merits. > > Discuss... > > > > -- 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/62ad3ea1-c315-470c-95df-26f3fc0eb141%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
