Hello Jeremy,
Why adding another mechanism instead of using the ones that exists already?
El 09/09/2015 14:05, "Jeremy Ruston" <[email protected]> escribió:

> Hi Evolena
>
> I was busy spreading the word by using Tiddlywiki in a project with others
>> people (so I went further in interface customization than I ever did
>> before, with forms to create tiddlers or selectable fields in edit mode),
>> but I've always kept an eye on the Google Group and on the new things on
>> GitHub (except maybe between around the v1.0.8).
>>
>
> Great, I hope you'll be able to share some of the fruits in due course.
>
> The more I practice Tiddlywiki, the more I think that tags should remain
>> for user/content-oriented structure (I can accept system tags since they
>> are less visible), and that fields are the best way to manage all that is
>> "below" the application (all that "make it work", the interface, etc.).
>> Because we can give a semantic to the values of fields through the field
>> name, but it is not as easy for tags.
>> I've once reuse the whole toc-macro recursive logic to use a "parent"
>> field instead of tags (+ some cosmetic changes).
>>
>
> Interesting. Would you think that we should migrate away from the current
> system tag mechanism. For instance with a new "system-tags" field that
> contains a list. We could support the new schema alongside the old.
>
> Best wishes
>
> Jeremy
>
>
>
> --
> Jeremy Ruston
> mailto:[email protected]
>

-- 
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 http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAHfj67U3eFsmAOK_cTGmSkCyx5w%2Bh-4wJ%2B-_12dq_d4hmaNPwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to