Well, I know linking via ids is not readable in edit mode, however in a
non-edit mode, the id translates to a name, so that is ok for me.
As for semantic-alias (i.e. a real second title) vs. ids, I rather chose
ids as their purpose is only to allow exact references. same as in SQL
autoincrement primary keys...
And I rather place them inside a field because I like them to be more
"invisible" as they have no semantic meaning.
However I took a closer look at you example in your space and it is a
really nice workaround you are using, I mean exploiting the masking-title
of the link as a variable to use it in a local macro.
This way I could do something like
{{ 415241 | id }}
and put the filter in the macro instead of directly writing
{{{ [field:id[]!has[draft.of]first[]] }}}
that will make a nice shortcut...
On Monday, June 2, 2014 3:30:38 PM UTC+2, Stephan Hradek wrote:
>
> I can't see a fundamental difference between my alias approach and using
> IDs. Except that ID's tend to be unreadable.
>
--
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.
For more options, visit https://groups.google.com/d/optout.
