[tw5] Re: TW 5.2.0 + CouchDB ?
I can't speak for everyone, only myself. When I picked TiddlyWiki several years ago, I imposed the following constraints on myself (brief reason in square brackets): * Lightweight text markup that included hyperlinking [these are among the things that separate the solution from text-only] * Searchable * Open source [the content I generate for myself is too important to me for it to go dark if a startup shutters] * Offline-first [travel or an internet outage shouldn't completely separate me from my "second brain"] The first two are basic notetaking sorts of things, but the other two are why I use the default file saver with TiddlyDesktop. A single file + synchronization happens to be among the easier ways (to me) of accomplishing offline first. Everything is a trade-off. I will say that document databases are a dime a dozen. Plain text and HTML are probably the two most stable interfaces in technology today. I (and, I suspect, a great deal of TiddlyWiki's user base) value that sort of stability. On Monday, November 22, 2021 at 4:26:58 AM UTC-6 V wrote: > Hi. > > I have been following the TW project for years and I am still very > surprised that the community continues to actively support super strange, > inconvenient and limited ways of saving and synchronizing – but at the same > time all developments using normal technologies on which synchronization > could be easy, seamless and safe, such as CouchDB, are not supported in > official release and abandoned by community. > > Especially considering the new data storage format in JSON, with which > synchronization with object databases has never been easier. It's even > easier than maintaining the current server solution on files, which in > principle cannot work offline, unlike a solution based on > IndexedDB+PouchDB→CouchDB or IndexedDB→Mongo/Posrgres. > > I have used PouchDB adapter from NoteSelf, but it's outdated and contains > a lot of bugs. Other solutions were outdated even earlier. > > If IndexedDB/CouchDB solution were supported out of the box, there would > be no reason at all to use paid solutions like Evernote or Notion for > personal notes. > > Based on discussions & repo, it seems that no movement in this direction > is planned. > > I have only one question – why? > Is it really more convenient for everyone to save files in Dropbox using > crutches, constantly losing changes between devices and merging conflicts? > > Are these some kind of ideological reasons? > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/665e3ab6-5079-4c59-bb59-ebe112a842f3n%40googlegroups.com.
[tw5] Monowikis vs. Microwikis
I'm sure this has come up before, but what are the downsides to keeping one large wiki vs. several smaller ones? I mostly use mine as a sort of commonplace book and have two wikis, one that is related to work (technical stuff + project notes) and the other that is everything else of interest. I've been considering merging them together and the couldn't really think of a reason not to. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ce332959-203e-4c27-a936-a830b0e6e521o%40googlegroups.com.
[tw5] Re: How to model relationships between tiddlers
I've been tinkering with this approach and it fills the need pretty well. I hadn't really thought of using title lists in fields before, so using that + the list macro + transclusion has helped a great deal. The only thing that has felt a little awkward has been having to create strings of tiddlers connected by fields to model some of the more sophisticated relationships. Thanks for the pointers! On Monday, February 3, 2020 at 7:20:31 PM UTC-6, Eric Shulman wrote: > > On Monday, February 3, 2020 at 4:03:51 PM UTC-8, Michael McDermott wrote: >> >> Is there a way to semantically model some relationship between two >> tiddlers? >> For example, in a graph database, you might create a relationship like >> this: >> [Leonardo da Vinci] Painted--->[The Mona Lisa] >> Is there a good option in TiddlyWiki I've missed? >> > > You can create any "custom" fields you like on a tiddler. > > To represent a one-to-one relationship between painting and painter, you > could define > a "paintedby" field for a painting, the value of which would be the title > of a "painter" tiddler. > > e.g., [[The Mona Lisa]] tiddler would have a "paintedby" field containing: > "Leonardo Da Vinci". > > Conversely, to represent one-to-many relationships, you could define a > "painted" tiddler for > an artist, the value of which would be a space-separated list of titles of > paintings. > > e.g., [[Leonardo Da Vinci]] tiddler would have a "painted" field > containing: [[The Mona Lisa]] [[The Last Supper]] [[Salvator Mundi]] > > Then, to display a list of all his works, you can write in the [[Leonardo > Da Vinci]] tiddler: > <$list filter="[list[!!painted]]"><$link /> > > Alternatively, if not all paintings by Da Vinci are entered into the > "painted' field, you can still list all his paintings using a filter that > looks for his name in the "paintedby" field of other tiddlers, like this: > <$list filter="[all[tiddlers]paintedby]">... > > For a more complex example, let's suppose that each artist tiddler is > tagged with "artist". Then, you could create a list of all paintings in > the document, grouped by artists, using something like: > <$list filter="[tag[artist]]"> ><$link /> > > <$list filter="[all[tiddlers]paintedby]"><$link /> > > > > The outer $list finds all artist tiddlers and displays their titles, while > the inner $list shows all the tiddlers for the current artist (inside a > blockquote for nicer formatting > > enjoy, > -e > > > > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/57e2a0a7-8af7-4995-9a74-20a833f8b526%40googlegroups.com.
[tw5] How to model relationships between tiddlers
I make fairly heavy use of tags in TiddlyWiki and that works very well for broad categories. Is there a way to semantically model some relationship between two tiddlers? For example, in a graph database, you might create a relationship like this: [Leonardo da Vinci] Painted--->[The Mona Lisa] It's pretty easy to see creating tiddlers for The Mona Lisa and Leonardo da Vinci, but the only real way to link them is either tags or hyperlinks, but I don't see a good way to model that relationship. The closest I've seen is the TiddlyMap plugin, but that stores all of the relationships as JSON content, which can only really be manipulated through the map plugin itself. Is there a good option in TiddlyWiki I've missed? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/771ca45a-2c29-4db9-b570-d054c7ca25da%40googlegroups.com.
