How to snatch tags from another tiddler?

#6

Give this a try:

\define temp() $:/temp/copytags

<$let inputid={{{ [<temp>] [<qualify>] +[join[]] }}} popid={{{ [<temp>] [[/list]] [<qualify>] +[join[]] }}}>
<$edit-text tiddler=<<inputid>> tag=input class=tc-popup-handle focusPopup=<<popid>>/>
<$let tid={{{ [<inputid>get[text]] }}}>
<$button class="tc-button" disabled={{{ [<tid>is[tiddler]then[no]else[yes]] }}}>copy tags
   <$action-listops $tags="[<tid>get[tags]enlist-input[]]"/>
</$button>
<$set name=all filter="[all[tiddlers]!is[system]!has[draft.of]]">
<$set name=items filter="[enlist<all>search:title:literal<tid>]">
<$set name=items filter="[enlist<items>match<tid>]" value=<<all>> emptyValue=<<items>>>
<$reveal state=<<popid>> type="popup">
   <$select tiddler=<<inputid>> size={{{ [enlist<items>count[]min[10]max[2]] }}}>
      <$list filter="[enlist<items>]"><option><<currentTiddler>></option></$list>
   </$select>
</$reveal>

Put the above in a tiddler (e.g., “MyEditTemplates/CopyTags”), tag it with $:/tags/EditTemplate and add a list-after field containing “$:/core/ui/EditTemplate/tags”.

enjoy,
-e

3 Likes
#7

Marvelous @EricShulman :clap:

Personally, I’d wrap the $edit-text in keeping with the tag field itself:

<div class="tc-edit-add-tag"><div class="tc-edit-add-tag-ui">
<$edit-text tiddler=<<inputid>> tag=input class="tc-edit-texteditor tc-popup-handle" focusPopup=<<popid>>/>
</div></div>
#8

Using the same classes as the tag field controls does look better.

I’d even go slightly further and use:

<div class="tc-edit-tags" style="float:right;">
<div class="tc-edit-add-tag"><div class="tc-edit-add-tag-ui">
<$edit-text tiddler=<<inputid>> tag=input class="tc-edit-texteditor tc-popup-handle" focusPopup=<<popid>>/>
</div></div>
...

and then move the template to occur before $:/core/ui/EditTemplate/tags. The “float:right;” style places the added UI on the same line as the tags field controls and the “tc-edit-tags” class wraps it in an enclosing box with the same padding, so everything aligns nicely.

-e

1 Like
#9

… your <$action-delay ...> widget to remove the current selection from the $edit-text after clicking the copy tags button (set to say, ~3000ms).

I do that for a number gizmos in my wiki (thanks again for that).

@vuk Let us know how this works for you – otherwise Eric and I could be here all day tinkering with this :wink:

1 Like
#10

41 minutes? I think Eric must be slipping. It used to be these would be done in under 20 minutes.

:wink:

#11

True statement. I watched him last night.

#12

I hope it’s clear that there’s no disrespect involved.

Only awe!

#13

There’s no need for a dependency on the $action-delay widget: when the copy tags button is clicked, we can just delete the <<inputid>> tiddler to clear the input field and the current list selection.

I’ve added a bit of CSS to handle long tiddler titles in the $select list (using “text-overflow:ellipsis”)

Here’s my newly-published TiddlyTools edit template: TiddlyTools/Templates/CopyTags

which contains this wikitext code:

\define temp() $:/temp/TiddlyTools/CopyTags

<style>
.tt-copytags {
	& select { width:100%; }
	& option { overflow:hidden; text-overflow:ellipsis; }
}
</style>
@@float:right;.tt-copytags.tc-edit-tags
<$let inputid={{{ [<temp>addsuffix<qualify>] }}} popid={{{ [<temp>] [[/list]] [<qualify>] +[join[]] }}}>
<div class=tc-edit-add-tag><$edit-text tiddler=<<inputid>> tag=input class="tc-edit-texteditor tc-popup-handle" focusPopup=<<popid>>/></div>
<$let tid={{{ [<inputid>get[text]] }}}>
<$button>copy tags<$action-listops $tags="[<tid>get[tags]enlist-input[]]"/><$action-deletetiddler $tiddler=<<inputid>>/></$button>
<$set name=all filter="[all[tiddlers]!is[system]!has[draft.of]]">
<$set name=items filter="[enlist<all>search:title:literal<tid>]">
<$set name=items filter="[enlist<items>count[]regexp[0|1]]" value=<<all>> emptyValue=<<items>>>
<$reveal state=<<popid>> type=popup>
	<$select tiddler=<<inputid>> size={{{ [enlist<items>count[]min[15]max[2]] }}}>
		<$list filter="[enlist<items>]" variable=item><option title=<<item>>><<item>></option></$list>
	</$select>
</$reveal>

enjoy,
-e

#14

I did this (as in I blindly copypasted and followed the algorithm steps, since I’m very far from understanding the code past its final achievement). I can report two bugs (albeit first one can be rather labeled as missing feature):

  1. The edit field does not behave like the “main” search of the TiddlyWiki - the appearing menu stays empty as I type. Only after I type the full name of the tag donor tiddler - its name appears in the dropdown and I can select it.
  2. Tags are getting copied, but there’s a caveat. I created a donor tiddler with the following tags: tag1, tag2, +tag3, +tag4. After I fully type the name of the donor tag so I can select it (see 1. above) and tap the copy tags button - all four tags get imported (I really prefer import over copy here, but this is a cosmetic itch and perhaps a personal thought process caprice). If I tap copy tags again, another tag tag4 appears! What kind of poltergeist is this?! Tapping the button again changes nothing. But if I delete tag4 and tap one more time - it appears again! So it’s reproductible.

PS: this is feedback to the very first version of the code.

#15

Good God man. I’m running out of rockets to send you.

#16

Me too.

<style>
.copy-tags-select {
  option {
    max-width:25em;
    text-overflow:ellipsis;
  }
}
</style>

I added an “exclude” list, too. Getting close to adding a config tiddler but I prefer it self-contained…

#17

Not seen here. Which browser? Which OS?

#18

Tiddloid 2.5.0 on Android.

Same problem in Vivaldi 6.9.3451.114 on Android.

#19

I’m not able to develop/test/debug on mobile, sorry.

#20

This seems to be a side-effect of using a tag that begins with “+”. The $action-listops widget sees the “+” as a filter run prefix. As a result, it adds the remainder of the tag value (i.e., “tag4”) as a new tag.

I strongly recommend never using “+” as the initial character in a tag value, as the leading “+” is has special meaning within filter syntax. The same can be said for the other filter prefix characters, such as “-”, “~”, and “=”.

-e

#21

Mobile browsers don’t render $select lists in the same way as other platforms. They ALWAYS render them as single-line drop-down lists, so no value is displayed until the input exactly matches a single entry in the list. The reason this doesn’t occur for the “main search” is that that interface doesn’t use a $select list at all. Rather, it creates it’s own popup “div” in which it renders clickable tiddler links that navigate to tiddlers, which is completely different from selecting a value to populate an input field.

-e

#22

I asked about this very recently and was told it should be safe :frowning:

#23

I’ve managed to fix the “leading +” issue so it doesn’t add the “poltergeist” tag!

Instead of using

<$action-listops $tags="[<tid>get[tags]enlist-input[]]"/>

my code now uses

<$action-listops $field=tags $filter="[enlist{!!tags}] [<tid>get[tags]enlist-input[]]"/>

As previously noted, the problem was the $action-listops widget handling for $tags="[...]", which treats the parameter value as a subfilter, and thus was interpreting the leading “+” in a tag value as a filter run prefix, which produced the unexpected results.

In contrast, by using $field=tags $filter="[...]", the $action-listops widget does NOT treat the $filter parameter value as a subfilter. Thus, we can explicitly combine the existing tags with the “imported” tags by using [enlist{!!tags}] [<tid>get[tags]enlist-input[]], and a leading “+” in a tag value is no longer interpreted as a filter run prefix.

TA DA!

Of course, we still have the problem of mobile platforms completely screwing up the multi-line list box rendering by forcing it to be a single-line droplist :frowning:

Get the updated TiddlyTools edit template here: TiddlyTools/Templates/CopyTags

-e

1 Like
#24

Thank you very much.

Quite a challenge to browse your site on mobile. For some reason I could not select the code by tapping on it, to copypaste it into a tiddler of my test wiki. But I managed to get it by simply exporting the tiddler from there then importing it.

It’s also very laggy, I don’t know why. Maybe my phone does not have muscle to process it. But I can navigate other wikis fine. It’s a pity, because there’s a lot of useful content there.

#25

It should, and is now with Erics solution. But there are always degrees of safe. Personally just as with tiddler titles, tags with a “symbol” are in a way a compound tiddler title, and this is frought as well, I recomend against compount titles. There is always another way to do it, and each of those ways may on a rare occasions clash with another solution obtained elsewhere.