Hi Saq,
I checked out the new get-stream-root and it seems to deal with a missing
parent tiddler correctly now. I am fine with installing relink ... it is a
great plugin on its own and I'm not sure why I don't have in installed in
all my tiddlywikis.
The specific use cases that I have for cloning parent nodes are Daily logs,
Action item logs and Agendas. But thinking more about it, it almost seems
like those need something like sub-streams where you could have a common
linked stream structure with tiddler-specific sub-streams. I don't think
the complexity is worth the gain. I think just a clone-stream button that
will copy the existing structure to a new tiddler would be sufficient. That
is something I could likely hack together given enough time ... dealing
with title lists is not my forté but maybe I can reuse some of the results
of my previous struggles.
The other automation that I want to figure out is how to best import
unordered lists via copy and paste from other sources into streams as I am
always bringing in lists from other places. Copying bulleted lists from
LibreOffice and MSOffice products seems to copy the bullet characters so
those could likely be cues to break a part the list in the proper way. I am
not sure what copying a list from a webpage would do ... maybe they come
with the <ul/li> tags.
-
Item one
-
item two
-
sub-item of two
-
sub-sub-item of two
-
item three
Copying from LibreOffice Writer gives the above and I think that matches
what Word and Outlook give. I have no idea how to trigger that parsing
action on pasting the text but maybe a keyboard shortcut or bullet dropdown
option is doable.
/Mike
On Thursday, April 22, 2021 at 6:17:40 PM UTC-3 [email protected] wrote:
> Hi Mike,
>
> Relink is indeed a necessary dependency for Streams to handle renaming of
> tiddlers. I wish there was a way to make it mandatory to have installed, if
> not installed automatically with Streams.
>
> The get-stream-root[] filter is completely broken. Thank you for making me
> realize that. I wrote that in about 5 minutes at the end of a long day
> before posting this version.. I really shouldn't have. I am surprised it
> works at all! So as to not make the same mistake twice, I'll wait until
> tomorrow to push a new version.
>
> One thought, what makes more sense:
>
> [[mytiddler]get-stream-root[]] or [get-stream-root[mytiddler]] ?
> Note that with the suffix includeall, you can get all the intermediate
> tiddlers as well, starting with the root and ending with the tiddler you
> started at.. e.g.: [[mytiddler]get-stream-root:includeall[]]
>
> This form makes me wonder if [get-stream-root[mytiddler]] is the way to
> go, so that the filter can only ever have one input title.
>
> Regarding cloning a root tiddler, it will break some of the keyboard and
> drag and drop behaviour as well. If the desire is to be able to create a
> node structure easily for things you do frequently, the code and approach I
> posted for Arun above is probably the way to go rather than cloning
> tiddlers. If I am misunderstanding the use case, please do elaborate.
>
> Regards,
> Saq
>
>
> On Thursday, April 22, 2021 at 4:08:47 PM UTC+2 [email protected] wrote:
>
>> Thank you for your hard work, Saq. I am getting a lot of use out of
>> streams.
>>
>> I played around with get-steam-root on your site. As I understand it, the
>> use of the relink plugin is recommended/necessary for doing stream-root
>> tiddler renames and having everything work since the built-in rename
>> doesn't seem to keep all the connections. Is that the case? The main
>> functionality of streams works through a standard rename (with the renaming
>> of all tags and list fields) but get-stream-root breaks because the
>> "parent" fields don't get updated and returns the input node rather than
>> the last valid parent found. For instance, given this example stream,
>>
>> Parent
>> |node
>> ||subnode
>> |||sub-sub-node
>>
>> [[sub-sub-node]get-stream-root[]] will return "sub-sub-node" if "Parent"
>> doesn't exist (because of deletion or rename). I would have expected it to
>> go as far as it could and return "node" but maybe just returning itself is
>> more useful from a diagnostic point of view.
>>
>> I'm also playing around with the consequences and handling of cloning the
>> stream-root to reuse streams for agendas/daily logs. get-stream-root
>> doesn't detect that extra root (likely outside the scope of your intent)
>> but there are other ways to detect if something isn't the original root ...
>> I just need to figure out the new conditional/comparison filters to compare
>> <currentTiddler> with <stream-list>field:parent.
>>
>> /Mike
>> On Tuesday, April 20, 2021 at 12:59:55 PM UTC-3 [email protected] wrote:
>>
>>> Apologies for the delay with getting Streams 0.2 released, the last few
>>> months have been hectic.
>>>
>>> I've found some time to resolve some of the outstanding issues and hope
>>> to get a new stable release of 0.2 out next week.
>>>
>>> Any testing on this new interim version would be appreciated, just to
>>> help ensure that I haven't accidentally broken anything:
>>> https://saqimtiaz.github.io/sq-tw/temp/streams-0.21-preview.html
>>>
>>> *Changes since the last version posted:*
>>>
>>> - Improved detection and error handling for whether codemirror is
>>> available
>>> - Removed the indent/unindent swipe behaviour in favour of
>>> triggering the context menu
>>> - Added a plugin priority field so other plugins can
>>> override/customize Streams tiddlers. Hopefully this means people will
>>> stop
>>> distributing modified version of Streams which are a real headache in
>>> terms
>>> of providing support.
>>> - Tweaked the CSS for the settings UI to use color palette entries
>>> where possible
>>> - Removed the option to double click to exit editing
>>> - Introduced the filters get-stream-root and get-stream-nodes to
>>> make it easier to work with Streams tiddlers.
>>>
>>> *For anyone including Streams in editions or otherwise distributing the
>>> plugin:*
>>>
>>> - Please do not distribute modified versions of the plugin as this
>>> leads to my receiving support requests that are impossible to
>>> troubleshoot
>>> or manage.
>>> - If you need to customize the plugin, first look at the
>>> documentation to see if there is already a facility for extending or
>>> tweaking the plugin that you can use. If in doubt, ask or request a
>>> hook.
>>> - Otherwise, instead of modifying Streams please distribute Streams
>>> with your own plugin that overrides select tiddlers in Streams and
>>> implements the customization that you need.
>>>
>>> Regards,
>>> Saq
>>>
>>>
>>>
--
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/38254580-8867-4edc-97c0-e088313d73b6n%40googlegroups.com.
