>>> Thanks I realised the Context Menu has some customisation. However
it assumes a button/action where I may just want to display something
conditionally.
I could use a popup to contain something a bit like the rename, but more
info, but I am interested in placing a tag pill or button after the dot
point. I continue to try and see how to hack it.
@Tony I just decided to play around with this idea, and it turned out to be
pretty easy to get something basic working. The relevant tiddler is
$:/plugins/sq/streams/templates/stream-row-template. The <div> containing
the text block of a node is at line 33, so in my case I added the following
after <div class="stream-node-block">...</div>:
<$list filter="[tag[$:/tags/streams/ViewTemplate]]" variable=template>
<div style="padding-top: 4px; padding-bottom: 4px;">
<$transclude tiddler=<<template>>/>
</div>
</$list>
This allows me to add buttons to the right of the text like so:
[image: tags.png]
You could also put it before <div class="stream-node-block"> to have it
appear on the left hand side instead. I also added a context menu option
for adding the to do tag in the first place, then my buttons get
automatically transcluded.
@Saq In general do you think this would be a good feature to add to
Streams? You could pull out <div class="stream-node-block"> into a separate
tiddler tagged with $:/tags/streams/ViewTemplate. Then users can easily
customise what appears on a node just like we can with the ViewTemplate for
normal tiddlers. Obviously I know nothing about the technicals, so I accept
this could have negative effects that I don't understand.
On Monday, 3 May 2021 at 08:09:59 UTC+1 TW Tones wrote:
> Saq,
>
> Thanks I realised the Context Menu has some customisation. However it
> assumes a button/action where I may just want to display something
> conditionally.
> I could use a popup to contain something a bit like the rename, but more
> info, but I am interested in placing a tag pill or button after the dot
> point. I continue to try and see how to hack it.
>
> Regards
> Tony
>
>
> On Monday, 3 May 2021 at 15:02:15 UTC+10 Saq Imtiaz wrote:
>
>> @Tones https://saqimtiaz.github.io/streams/#FAQs
>>
>> On Monday, May 3, 2021 at 5:20:06 AM UTC+2 TW Tones wrote:
>>
>>> Saq,
>>>
>>> With each item in a stream, the bullet has its own menu and drag.
>>> Perhaps a simple way for the user to extend this would be being able to add
>>> an item to the stream item, or menu, just like how we add content to
>>> tiddlers with the view template, would permit many additional requirements
>>> to be added by the user. For example a button to tag the stream entry as a
>>> todo, or set a field aa a priority. Another space where users can display
>>> something per stream item would be similar.
>>>
>>> Tones
>>>
>>> On Friday, 30 April 2021 at 22:42:41 UTC+10 Saq Imtiaz wrote:
>>>
>>>> Hi Mohammad,
>>>>
>>>>
>>>>> Lovely! This is one of my favorite use case! At the end I normally
>>>>> merge the notes!
>>>>>
>>>>
>>>> I need to develop my workflow further but so far I've been dragging and
>>>> dropping to an actions items tiddler or other tiddlers that are relevant
>>>> to
>>>> the topic. At the end there are no nodes left in the original conference
>>>> call notes.
>>>>
>>>>
>>>>> I use this solution! Assume I want to put note or discuss a slide or
>>>>> report in an online meeting!
>>>>> Say tiddler is $:/kookma/courses/CHE403/rk45
>>>>>
>>>>> Yes your way of doing things is one option.
>>>>
>>>> What I am considering is this: imagine that you want to take notes
>>>> using Streams on $:/kookma/courses/CHE403/rk45
>>>> If you add nodes, directly streams will edit this tiddler's stream-list
>>>> field. This is a problem if you want to maybe synchronize this tiddler
>>>> with
>>>> another wiki later, you will get a merge conflict.
>>>>
>>>> So there should be a way to use Streams to take notes on a tiddler
>>>> without having to modify it.
>>>> So the idea is, instead of saving the list of nodes in the stream-list
>>>> field of the tiddler $:/kookma/courses/CHE403/rk45, we can save them
>>>> in a config tiddler called something like
>>>> $:/streams/sidecar/$:/kookma/courses/CHE403/rk45
>>>>
>>>> Streams can then read the list of nodes from this tiddler, instead of
>>>> from the stream-list field in the $:/kookma/courses/CHE403/rk45
>>>> tiddler.
>>>>
>>>> We would not need to do this for every node, just the stream root
>>>> tiddler.
>>>>
>>>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/6470712f-95f2-4dfa-9916-626da44cbe68n%40googlegroups.com.
