Reluctantly, perhaps, I have to admit that Fields are really better than slices, because you can do filter manipulations on them, and not worry about strange regexp behaviors.
What you can do is create an input template with a drop-down list of tiddlers to filter. Then each field can be edited with a <$edit> widget, giving it as much space as you need for that particular field. Having a little structure in your tiddlers is a good thing if you're going to have lot's of tiddlers with a similar data structure. It makes reporting and extracting much easier. -- Mark On Wednesday, January 31, 2018 at 12:35:57 PM UTC-8, Diego Mesa wrote: > > Thanks all for your comments. > > Tony Im looking forward to your work! > > Mark, thanks for pointing me to Thomas' extract. Ill take a look. Also, I > need to take a look at "slicing" in TW classic. > > Coda thats an interesting idea of actually using a data tiddler to define > fields and their respective sizes for edit fields. > > Personally, I think the most transparent mechanism would just be another > text area, perhaps the same size as the text edit area for a normal > tiddler, where everything you type in there (as per the format above) will > be parsed/interpreted as fields. > > Its really just like when you look at a naked .tid file. Everything is so > transparent, tangible and easy to understand. > > Diego > > > On Tuesday, January 30, 2018 at 4:51:30 PM UTC-6, Diego Mesa wrote: >> >> Hello all, >> >> I *see* how powerful fields are. They create a clear division of text >> that tiddlywiki knows how to deal with well. However, I *hate* >> adding/editting fields. Its cumbersome, and annoying. I would like to >> suggest an alternative: a "field" text box that is default collapsed that >> works something like a dictionary tiddler (not exactly). Each line is a new >> field like: >> >> name: field value >> name2: field val2 >> name3: """ field value with "quotes" and >> multiple lines""" >> name4: etc. >> >> This, to me, seems an easier, more intuitive way to view and manipulate >> field contents. After all, its all text! *Note: *This is *my* opinion. >> Everyone is free to disagree. I would just like to bring up this idea, see >> if anyone thinks something like this is incredibly easy, or absolutely >> impossible to implement. >> >> If anyone has a different idea, please share! >> >> Best, >> Diego >> >> >> >> > -- 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 post to this group, send email to tiddlywiki@googlegroups.com. 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/cde0794d-47b1-4bc3-b4cc-4002335fde72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
