Hey Mario

Just a quick note - I think github handles uniqueIDs and 
linking wonderfully. Each PR, Issue, etc gets a unique sequential ID. When 
you want to link to one you can type # and a popup appears with the ID *and* 
the 
title. That is automatically added as a reference in the original issue 
(our backlinks). It would be wonderful to have a similar workflow on TW.

On Tuesday, December 18, 2018 at 6:07:07 AM UTC-6, PMario wrote:
>
> Hi Diego,
>
> Thanks for your nice words!
>
> TL;DR I'll implement it!
>
> --------------
>
>
>    1. 
>>    
>>    what I want to type
>    
>    - about: "Edit-Comptext dropdown plugin" ... That's a good idea. ... 
>       I'll have to have a closer look
>       - I've seen the discussions about "frictionless writing". I think 
>       aliases can help here. 
>       2. 
>>    
>>    where I want it to go
>    
>    - I've seen the discussions about UUIDs. They started 5+ years ago. 
>       ... As we can see. ... It doesn't work out (1 exception TiddlyMap) It 
> is 
>       way to complicated to use for "ordinary" users. 
>       - TW already uses a UUID -> The title. 
>       - It is uniqe within 1 tiddlywiki by design. And it's super 
>          convenient for new users to use. The problem now is, how can we make 
> it 
>          universal unique 
>          - I think I have an Idea, which is not directly related to 
>          uni-link. 
>          3. 
>>    
>>    what I want to render
>    
>    - I can see the issue. And I think, the solution is generic enough, to 
>       be part of the plugin. 
>       
>
> I do like your BibTeX example. That's straight to the point. It would be 
> possible to write *[[citationKey|?cite]]* or *[[alias|?cite]]*. But I'm 
> not sure, if this type of functionality is "overpowerd". With the current 
> code, in these examples cite is a macro name. something like <<cite 
> alias>>
>
> With the existing TW version it could be written as: 
> {{tiddlerTitle||cite}} ... The only difference is, that using an alias will 
> survive tiddler renaming. ... Which I think is huge! 
>
> BUT 
>
> Can you see the duplication of syntax / functionality? I'm not sure, if we 
> really should do this. ... I know, that you didn't ask for an 
> implementation that I describe above. Your usecase is "simpler", ... but 
> the consequences are the same. 
>
> have fun!
> 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/b29bae33-5e7e-4cc8-a20a-7ef51b20a8da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to