On Sunday, May 12, 2019 at 12:45:45 PM UTC+2, @TiddlyTweeter wrote:
... 

> The confusion for me, I think, is Tiddlers Have Fields Already so why are 
> we adding others a different way rather than changing field behaviour? 
>

The problem is, that we don't have a structure, that allows us to use 
multi-line fields with the .tid file format. 
eg:

title: tiddler-title
tags: a b c [[d e]]
my-field: 1 line of text is possible 

text field starts here. Fields can't handle muliti-lines.

As you can see, there is no way at the moment to add multi-line fields in a 
sensible way. 

There are 2 main points which are important:

1) It must be easy for humans to read and modify
2) It should be relatively easy for machines to parse the content.

No. 1) is more important than No. 2! 

I personally think, that the existing field editing mechanism (UI) is 
cumbersome. Especially since fields are alphabetically sorted ... 

ATM there are differences between core-fields eg: created, modified, ... or 
tags. ... They have built in behaviors, which are hard for ordinary users 
to duplicate. Eg: It's hard if I want to create a field eg: my-tags, that 
behave like the tag field. Especially I want to have an automatic UI, that 
let's me handle my-tags the same way as the existing tags-dropdown. 

My proposal makes this possible with eg: 

\field my-tags(type:tag)
a b [[c d]]
\end

Since fields can have a user defined "type" now, it will be possible to 
automatically create the tag-like UI for my-tags field ... and so on ... 

-mario

-- 
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/bd45e618-c504-4eec-8eab-abfe0bdc3050%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to