@Tones You are right in what you are saying, my understanding and designing capabilities of TW are limited. A primary purpose of this discussion for me is to learn and understand more, and another main purpose is to provide user feedbacks to developers.
On Sun, 16 May 2021, 01:54 TW Tones, <[email protected]> wrote: > Damcal > > With respect I think you are mixing the design process with the user > activity on your wiki. Cloning is a way of rapid duplication and edit, you > would be far better served using a template or button to build your > "instances" of a standard tiddler. Fortunately in tiddlywiki we can build > tools to fix issues generated in the design phase, but these are best just > one off corrections to the way your wiki is designed. If seems to me you > are operating as a user a tiddlywiki where the design is not finished, this > is in part why you feel you need shortcuts such as clone, because many of > your processes are not as yet automated or simplified (through design). > > To me the relink plugin is a great addition, but to rely on it, may > suggest opportunities for redesign exist. > > Tones > > On Sunday, 16 May 2021 at 09:21:48 UTC+10 Soren Bjornstad wrote: > >> So it's mostly about renaming things? That's an interesting use case. I >> guess I have never had the need to do that on a large scale. I wouldn't >> have expected inheritance to be capable of renaming a field like that, >> either. >> >> I haven't used Tiddler Commander, but renaming a field doesn't really >> seem like it should be difficult, so perhaps something there could be >> improved or a new tool could be created. >> >> On Friday, May 14, 2021 at 10:43:55 AM UTC-5 damscal wrote: >> >>> On Thursday, May 13, 2021 at 1:53:17 PM UTC+2 Soren Bjornstad wrote: >>> > It really would be very helpful if you could give an example use case. >>> >>> I'll try to: >>> >>> 1. Lets say, for instance, that I need to save some contacts info (like >>> names, email addresses and so on). I'm going to create a tiddler for each >>> person and populate them with fields to store their contacts info. I can >>> use the Clone button to statically inherit field keys. But I'm always in a >>> hurry so I'm not going to figure out a set of fields keys which is going to >>> be future proof. Later at some point I'll have the need to rename some >>> field keys (aka field names, not their values), add some, delete some >>> others. >>> >>> 2. Same thing but with tags (relink can be used to rename them, but not >>> to add or delete them) >>> >>> atm to fix problems like these ones I'm using tiddler commander, but the >>> whole thing is quite time consuming and prone to errors for me. >>> I think TW and its community are superb, yet I find it difficult to keep >>> my wikis organized and consistent, which it slows down my workflow. >>> In contrast I've found Trilium's templates approach more intuitive and >>> quick in this regard (note that templates are not based on hierarchy). >>> Trilium is still not as mature and well referenced as TW though. >>> >>> Any tips/useful references? >>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/zDLrmjhDFOA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/01588939-d90c-4785-aff7-fb8aaa084ccfn%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/01588939-d90c-4785-aff7-fb8aaa084ccfn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAPkG9jZh1n86hKC8_v0Opf6T8AopgRvmAPmnhUUoymrP5YUy8A%40mail.gmail.com.
