[tw5] Re: Javascript to open tiddler

[Saq Imtiaz]

Assuming you want to open the tiddler in the default story river, try this:

let actions='<$navigator story="$:/StoryList" history="$:/HistoryList">
<$action-navigate $to="TiddlerNameHere"/>

'
window.parent.$tw.rootWidget.invokeActionString(actions,this)

On Sunday, July 10, 2022 at 3:29:53 PM UTC+2 andrewg_oz wrote:

> Thanks for your suggestions. Unfortunately, I left out some important 
> details in my OP and so I'm still trying things.
>
> The Google Charts are generated in an iframe, which is where the selection 
> handler is. It means the handler is not in the context of the widget/macro, 
> so 'this' isn't meaningful.
>
> I can access 'window.parent.$tw' and I've seen code fragments that make it 
> look like I should be able to do the following:
>
> window.parent.$tw.rootWidget.dispatchEvent( { type:'tm-navigate', 
> navigateTo: 'Tiddler Name Here' } );
>
> Nothing happens.
>
> I've tried a couple of other event properties too: setting 'param' the 
> same as 'navigateTo', and setting 'navigateFromTitle' to the name of the 
> tiddler hosting the macro call. Nothing for those either. Not even error 
> messages in the console.
>
> Thanks again for your help. Hoping you or anyone else might have some new 
> ideas...
>
> On Sunday, 10 July 2022 at 2:13:06 am UTC+8 BJ wrote:
>
>> or maybe
>> this.dispatchEvent({type: "tm-navigate", navigateTo:tids[i]});
>>
>>
>> On Saturday, July 9, 2022 at 4:12:28 PM UTC+2 BJ wrote:
>>
>>> from within a widget/macro use
>>>
>>> this.caller.dispatchEvent({type: "tm-navigate", navigateTo:tids[i]});
>>>
>>> On Saturday, July 9, 2022 at 9:30:01 AM UTC+2 andrewg_oz wrote:
>>>
 I've recently been experimenting with using Google Charts in 
 TiddlyWiki. It's going quite well (see my other thread), but I can't work 
 out how to open a tiddler in javascript (i.e. the Google Chart selection 
 handler) without using window.location = '#' + tiddlerNameHere;

 That works, but sets the address bar and looks ugly. I'm sure there's a 
 better way.

 Can anyone help?

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b24ebba0-68d5-46c4-b89d-2a83eb422201n%40googlegroups.com.

Re: [tw5] Filter to exclude tiddlers from includeWikis

[Saq Imtiaz]

I think you could try to use the  $:/config/OriginalTiddlerPaths tiddler to 
determine which tiddlers come from a specific path on disk and then exclude 
those.

https://tiddlywiki.com/#tiddlywiki.info%20Files

On Monday, January 3, 2022 at 3:50:09 PM UTC+1 Jeremy Ruston wrote:

> Hi Louis,
>
> I'm running several TW 5.2.1 wikis on node and I use the includeWikis 
> properties in tiddlywiki.info file. Example wiki AAA has
>
> "includeWikis": [
>{"path": "../BBB"}
> ]
>
> Is there a filter expression I can use from within wiki AAA that will 
> exclude tiddlers from BBB?
>
>
> No, there’s no automatic way to distinguish tiddlers from different wikis. 
> You’d have to use tags or other manual criteria to distinguish them.
>
> Best wishes
>
> Jeremy
>
>
>
> Thanks.
>
> -- 
> 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 tiddlywiki+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/316c974c-c76a-44b7-b1dd-794f8a246cc2n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ce533025-ba8c-494e-8e7c-1a4eb85e7e38n%40googlegroups.com.

[tw5] Re: variables in subfilters make TW crash

[Saq Imtiaz]

I suspect you are using TW v5.1.23 in which this is a know issue. Upgrading 
to v5.2.0 should resolve it. If it does not, please report back.

On Sunday, November 21, 2021 at 2:30:27 PM UTC+1 CarloGgi wrote:

>
> Hallo everybody, I go into trouble when using variables in subfilters, 
> they make code as simple as
>
> <$list variable="indx" filter="[tag[myTag]indexes[]]">
>
> <$vars subf="[getindexsplit[,]trim[]match[aword]]">
>
> <$list filter="[tag[myTag]filter]" variable="result">
>  <> 
> 
>
> 
>
> 
>
> to crash TW with Internal Javascript error: "TypeError: widget is 
> undefined"
>
>
> Even narrowing down the outer <$list> to a simple <$set> widget as in
>
>
> <$set name="indx" value="index-01">
>
> <$vars subf="[getindexsplit[,]trim[]match[aword]]">
>
> <$list filter="[tag[myTag]filter]" variable="result">
>  <> 
> 
> 
>
> 
>
> doesn't improve things at all. Same Internal Javascript error: "TypeError: 
> widget is undefined". It really looks like using variables inside 
> subfilters is the problem, as soon as I replace it with a parameter, like 
> for example
>
>   <$vars subf="[getindex[index-01]split[,]trim[]match[aword]]">
>
> Tiddliwiki stops complaining.
>
> Thanks for any hints, suggestions, etc.
>
> CG
>
> Ubuntu 18.04.6 LTS
> Firefox 94.0
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5c476fec-8592-4eb4-b024-2bdbf37af6e1n%40googlegroups.com.

[tw5] Re: Bug in TW 5.2.0 in zoomin view.

[Saq Imtiaz]

Can you please confirm if this was working in TW v5.1.23?

I have opened an issue on Github: 
https://github.com/Jermolene/TiddlyWiki5/issues/6180
On Sunday, November 7, 2021 at 10:40:19 AM UTC+1 Siniy-Kit wrote:

> Jeremy, help me please. I want to update my template to  new version, but 
> it works only with zoomin view. 
>
> четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 
>
>> Old TW5 works good. But now it has bad auto scroll while navigating 
>> between tiddlers 
>> For example open this tiddler https://tiddlywiki.com/#Filter%20Operators 
>> then make zoomin view
>> [image: Снимок экрана 2021-10-28 154440.png]
>>  then go back to Filter Operators tiddler and press "range"
>> [image: Снимок экрана 2021-10-28 154716.png]
>>
>> after click you will see this
>> [image: Снимок экрана 2021-10-28 154853.png]
>>
>> I want to see the top of this tiddler, but it autoscroll to middle. Can 
>> we fix this bug? 
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a6ebf32c-a089-4f0b-ba94-bfa40e37672en%40googlegroups.com.

[tw5] Re: how do stroll and tiddlyblink compare?

[Saq Imtiaz]

Here is a video  courtesy of Defiant_Information 
from reddit  that shows 
how to set up Stroll with TiddlyMap.

If you have further questions I suggest you post them on Talk TiddlyWiki 
, where you may also get input from Dave, the 
creator of Stroll.

On Friday, August 20, 2021 at 8:37:30 AM UTC+2 strikke...@gmail.com wrote:

> Tiddlyblink  is earlier than Stroll. At least in the beginning the main 
> difference was, that Stroll had the two story view.. David Gifford created 
> lots of goodies for Stroll - and Saqs two story was new to all of us - and 
> was and is very interesting. But also the main reason for the difficulty 
> using it with  
> Tiddlymap.
> Tiddlymap is special nothing quite like it.
> Anne found that Tiddlyblink was a fast route for her digital garden set 
> up. But tiddlywiki is used for many purposes mostly note taking - but can 
> be used for lots of things and have very different look and feel. Digital 
> gardening tool is only one of the uses.
>
> Birthe
>
>
> On Friday, August 20, 2021 at 7:34:29 AM UTC+2 jamm...@gmail.com wrote:
>
>> I was trying this tutorial 
>>  and felt stuck when 
>> Anne didn't explain the difference between stroll and tiddlyblink. Wasn't 
>> sure if stroll came out after the tutorial and she didn't update it. Or if 
>> the tutorial is doable without choosing tiddlyblink, and if so, how.
>>
>> I also saw stroll might prevent tiddlymap. Are mindmaps possible in this 
>> case?
>>
>> generally, I am still anxious about choosing a platform to begin 
>> gardening on, but TW seemed to have more support and development than most 
>> others, so as a beginner to gardening, indieweb, and programming, am I 
>> missing anything in my choice of TW? what implications are in this choice?
>>
>> thanks,
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f27137d7-4af1-49eb-9d78-71327b7eae5dn%40googlegroups.com.

[tw5] Re: why TiddlyDesktop does not run my macros ?

[Saq Imtiaz]

Can you please post the code for your macro?

On Friday, August 20, 2021 at 9:45:06 AM UTC+2 vpl wrote:

> Hi
>
> I'm wondering why tiddlydesktop does not run the macro I've developped in 
> javascript
> When I open the tiddly file (.html) into my browser all works fine and 
> macro are executed, by through tiddlyDesktop it remains silent ... Any 
> explanation or special config I would have missed ?
>
> Thanks a lot for your help and support
>
> Regards
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0383a1ee-f918-40b5-aed8-4ed947197c0dn%40googlegroups.com.

[tw5] Re: Use Talk Tiddlywiki instead of Google Forum

[Saq Imtiaz]

Not a feature but a reason:

The plan is to eventually make this group read only and move all 
discussions to Discourse. Actively using Discourse now, and not just for 
testing, will allow us to discover any pain points etc and make a more 
informed decision about whether we do want to make that permanent move to 
Discourse.

On Thursday, August 19, 2021 at 12:34:08 PM UTC+2 Mohammad wrote:

> *Why should we use Talk Tiddlywiki (https://talk.tiddlywiki.org/ 
> ) instead of Google Forum?*
>
>
>1. it mirrors all posts from Google Forum, so you will be notified 
>what is going on Google Forum
>2. it allows previewing your post before sending
>3. it allows editing your post after it was sent! (this is very good 
>feature I frequently need)
>4. it supports pinig other users
>5. it support code block
>6. it supports nice sharing features e.g share to Twitter
>
>
> Please complete this list with features I missed!
>
>
> Best wishes
> Mohammad
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3850f93f-07d7-4bf2-98cb-f05bfdea347dn%40googlegroups.com.

[tw5] [ Streams ] future development plans

[Saq Imtiaz]

Hi everyone,

I've started a thread about future development plans for Streams 
.

Please note that I will no longer be monitoring or replying to Streams 
related matters on the Google Group. Please address any questions, comments 
or feedback that you wish for me to see to either the Discourse forum 
 or Github 
.
Thank you.

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1a28895-d5a4-4866-9a1e-968ab01f4349n%40googlegroups.com.

[tw5] Re: Seeking common misunderstandings

[Saq Imtiaz]

Yes that is exactly what I mean. The GG threads in Discourse are read only.

It would help if people started new threads on Discourse, hopefully we will 
see more of that in the next days.
The plan is to migrate to Discourse and make this group read only after a 
short period where we test out Discourse. So anyone that doesn't try using 
Discourse in anger now will likely miss their chance to have a say in that 
final decision.
On Wednesday, August 18, 2021 at 4:30:33 PM UTC+2 Stobot wrote:

> @saqimtiaz - I might be doing it wrong, but I haven't found a way to reply 
> in Discourse to a GG thread, I assume you mean you'll start a new 'topic' 
> in Discourse, or am I missing something? I only see the reply button in 
> Discourse for Discourse-native conversations.
>
> This is making the "conversion" pretty painful. I'm monitoring Discourse, 
> but for all replies I'm going into GG and finding the thread to reply to 
> (like now).
>
> On Wednesday, August 18, 2021 at 10:16:04 AM UTC-4 saq.i...@gmail.com 
> wrote:
>
>> Hi Soren,
>>
>> I posted a small list an hour ago but due to the vagaries of GG it 
>> doesn't seem to have been posted. Re-writing is never fun but will do so 
>> and post as a reply on Discourse a little later.
>> Regards,
>> Saq
>>
>> On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:
>>
>>> I'm working on adding a chapter (or back-matter section, not sure yet) 
>>> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I 
>>> have two sections:
>>>
>>>- Macros are not function calls
>>>- Constant strings cannot be combined with transclusions
>>>
>>> Are there other common misunderstandings – in terms of incorrect mental 
>>> models of how TiddlyWiki operates, or things one might expect to work that 
>>> don't – that come up here or elsewhere that you'd like to see documented in 
>>> such a section?
>>>
>>> Feedback on the drafts of the two existing sections would be welcome as 
>>> well:
>>>
>>>
>>> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>>>   
>>> 
>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3836fbbe-2ddd-43fd-aa7d-c73fa08a0f96n%40googlegroups.com.

[tw5] Re: Seeking common misunderstandings

[Saq Imtiaz]

Hi Soren,

I posted a small list an hour ago but due to the vagaries of GG it doesn't 
seem to have been posted. Re-writing is never fun but will do so and post 
as a reply on Discourse a little later.
Regards,
Saq

On Wednesday, August 18, 2021 at 3:30:43 PM UTC+2 Soren Bjornstad wrote:

> I'm working on adding a chapter (or back-matter section, not sure yet) 
> called "Common Misunderstandings" to *Grok TiddlyWiki*. Currently I have 
> two sections:
>
>- Macros are not function calls
>- Constant strings cannot be combined with transclusions
>
> Are there other common misunderstandings – in terms of incorrect mental 
> models of how TiddlyWiki operates, or things one might expect to work that 
> don't – that come up here or elsewhere that you'd like to see documented in 
> such a section?
>
> Feedback on the drafts of the two existing sections would be welcome as 
> well:
>
>
> https://sorenbjornstad.com/downloads/temp/gtw-prerelease.html#Common%20Misunderstandings
>   
> 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/55481566-27af-4940-ba4a-a353da9b2c0bn%40googlegroups.com.

Re: [tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

A video from the community call as well as slides are now available at the 
new community forum:
https://talk.tiddlywiki.org/t/aug-17th-2021-community-call-core-savers-syncers-upload-plugin-discourse-forum/28

You will also find a thread there in the Plugins section for feedback on 
the beta release of the FileUploads plugin.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d2859c0f-d7a5-44ae-8aa8-be52b2beda95n%40googlegroups.com.

Re: [tw5] Do you already use https://talk.tiddlywiki.org/ ?

[Saq Imtiaz]

It would be great if we could get more community members to join the new 
forum at https://talk.tiddlywiki.org/ and use it for discussions, and 
provide feedback on how they find the user experience.

Note that you can log in with a Google or Github account, or create a new 
user account specifically for the forum.

Saq

On Tuesday, August 17, 2021 at 11:30:28 AM UTC+2 Jeremy Ruston wrote:

> The new Discourse forum at https://talk.tiddlywiki.org/ is an experiment 
> at this stage. At the moment, there's two way sync with Google Groups, but 
> if people like the new system then we will migrate fully over to it.
>
> We'll be discussing it at the TiddlyWiki community call in a few hours 
> time:
>
>
> https://talk.tiddlywiki.org/t/aug-17th-2021-community-call-core-savers-syncers-upload-plugin-discourse-forum/28
>
> Best wishes
>
> Jeremy.
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 17 Aug 2021, at 09:23, Mohammad Rahmani  wrote:
>
> 
>
> Thanks for sharing BTC!
> I would like to have one central place to be informed about TW!
>
> Is this the one I wished?
>
>
>
> Best wishes
> Mohammad
>
>
> On Tue, Aug 17, 2021 at 12:22 PM BurningTreeC  
> wrote:
>
>> Hi tiddlywikians,
>>
>> there's this new TiddlyWiki forum at https://talk.tiddlywiki.org/
>>
>> Is the google group still a thing for you or are you going to move to the 
>> new Forum?
>>
>> just out of interest :)
>>
>> Best wishes,
>> BTC
>>
>> -- 
>> 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 tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/d1c6b96b-968b-4f67-a602-f7dd1a17d905n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> 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 tiddlywiki+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/CAAV1gMDVzrajBKsk-rNF910mhnV-a79UMD%3Dfk41ojdpkoReq_Q%40mail.gmail.com
>  
> 
> .
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/205a6ce9-0b82-46c2-bd59-7c0251da1864n%40googlegroups.com.

[tw5] Re: A brewing idea: TiddlyWiki on node.js: check for changes

[Saq Imtiaz]

Hi Charlie,

On Tuesday, August 17, 2021 at 8:18:27 PM UTC+2 cj.v...@gmail.com wrote:

> Say I have a TiddlyWiki running on node.js, and two people currently 
> viewing the same TiddlyWiki in their browsers.
>
> Say User 1 is editing a tiddler.  I'm thinking it would be cool if  User 2 
> could know that User 1 is editing the tiddler (or that anybody is editing 
> the tiddler.)
>

I think most of the basics for this are in place and just needs some 
cobbling together.

Note that the nodejs server does synchronize tiddlers from client to 
server,  and from server to client. I believe the default refresh interval 
to get new changes from the server is about a minute if my memory serves me 
well.

 If User 1 is editing a tiddler, that creates a Draft tiddler that will get 
sync'ed to User 2's wiki. This would appear as a red draft indicator at the 
bottom of the screen, though it could easily be used to display a message 
on the tiddler in question as well.
 

> And/or, it would be cool if User 2 can get a notification that a 
> particular tiddler has changed (because of User 1's editing), and that User 
> 2 should refresh the browser to get that change if he/she wants it.
>

The new tiddler should automatically get sync'ed from the server to User 
2's wiki without need for a reload.

Note that there is work underway on making the server to client sync 
instantaneous:
- https://github.com/Jermolene/TiddlyWiki5/pull/5279
- https://github.com/Jermolene/TiddlyWiki5/pull/5882

Also, Joshua is doing some interesting work on implementing a real time 
multi-user feature.

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ab3e600a-9b85-444f-b900-79c7e5ed8c8cn%40googlegroups.com.

[tw5] Re: I Think I Hacked TiddlyWiki

[Saq Imtiaz]

>
>
> I'd be more concerned about people being tricked into importing a tiddler 
> that contained code like this.
>

>From my perspective this is the only practical concern, and once again 
emphasizes the need to be careful when importing content from others. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/373d5cfb-c7c8-490b-82a4-ca1bad623afan%40googlegroups.com.

[tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Saq Imtiaz]

@cmari perhaps this is closer to what you need?
https://groups.google.com/g/tiddlywiki/c/9hZTwQBuwe8/m/YlRPXrn0BQAJ

Note that you can use the "arrow" buttons to move forwards and backwards in 
time.

I've bookmarked these two habit tracking solutions so they show up at 
TiddlyWikiLinks:
https://links.tiddlywiki.com/topics/daily-tasks/

On Saturday, August 14, 2021 at 8:03:30 PM UTC+2 cmari wrote:

> Yes, I have seen that, thanks. Unfortunately, I lack the necessary 
> skills/time to identify the pieces that would need to be adapted to allow 
> for viewing (and updating) a running overview of the task status for the 
> last 10 days.
>
> On Saturday, August 14, 2021 at 10:04:33 AM UTC-7 saq.i...@gmail.com 
> wrote:
>
>> This is one of the first things that came up with a search, perhaps it 
>> may be of interest:
>> https://rawgit.com/Guitlle/habito/build/build/habito-docs.html
>>
>> On Saturday, August 14, 2021 at 6:54:23 PM UTC+2 Saq Imtiaz wrote:
>>
>>> Just to add a bit more clarification to the issue since I have a bit 
>>> more time now than I did yesterday, this functionality should have been 
>>> implemented as a widget and not a macro. I quickly dropped the link in 
>>> reply yesterday so you would know that there was some follow up on your 
>>> post.
>>>
>>> JavaScript macros in TiddlyWiki5 are supposed to be for simple text 
>>> substitution and do not have any facilities for refreshing in response to 
>>> other changes in the wiki, the input of the macro determines the output. A 
>>> macro should never modify tiddlers. The macro in question both needs to 
>>> refresh itself in response to tiddler changes, and also modifies tiddlers. 
>>>
>>> Such a macro was never intended to be supported but has worked so far 
>>> because we were aggressively refreshing entire tiddlers when anything in 
>>> that tiddler changed. So for example a change to a tiddler "list" field 
>>> would refresh the entire tiddler in the story. However this is suboptimal 
>>> both from a performance point of view and in terms of user experience. Some 
>>> of the annoyances commonly encountered like an edit-text widget in a 
>>> tiddlers text field not being usable to modify a field in the same tiddler 
>>> come from this aggressive and unnecessary refresh behaviour.
>>>
>>> So the question that presents itself now is whether we maintain 
>>> backwards compatibility for a behaviour from third party macros that was 
>>> never intended to be supported and holds back improvements, or break such 
>>> macros as their implementation will trip us up again in unexpected places 
>>> and limit future possibilities.
>>>
>>> Your actual need for the functionality offered by this macro could 
>>> probably be solved with a wikitext implementation as well. It might be 
>>> worth a search to see if someone has shared such a solution.
>>>
>>> Regards,
>>> Saq
>>>
>>> On Saturday, August 14, 2021 at 6:42:38 PM UTC+2 cmari wrote:
>>>
>>>> Thanks Saq, that was certainly not the answer I was hoping for, but 
>>>> it's good to know which way the wind is blowing after so many years (I 
>>>> think the original dailytasks plugin that got me started 13 years ago came 
>>>> from you?).
>>>> cmari (considering changing my name to "offspec user"!)
>>>>
>>>> On Friday, August 13, 2021 at 1:03:59 PM UTC-7 saq.i...@gmail.com 
>>>> wrote:
>>>>
>>>>> See 
>>>>> https://github.com/Jermolene/TiddlyWiki5/issues/5903#issuecomment-898691487
>>>>>
>>>>> On Friday, August 13, 2021 at 9:26:33 PM UTC+2 cmari wrote:
>>>>>
>>>>>> I have been a happy daily user of *Daily Task Macro *(
>>>>>> http://togglers.tiddlyspot.com/) for years, so I am wondering 
>>>>>> whether someone can point me to any tips for how I might update the 
>>>>>> macro 
>>>>>> so that it will continue to work in the new prerelease. 
>>>>>>  
>>>>>> Specifically, the fields in toggler tiddlers do continue to update 
>>>>>> correctly when the images are clicked, but the (svg) images themselves 
>>>>>> do 
>>>>>> not update in response to the click until the tiddler is opened and 
>>>>>> closed 
>>>>>> again.
>>>>>>
>>>>>> Thanks for any help!
>>>>>> cmari
>>>>>>
>>>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/14565e42-4306-482a-aef8-dc62a82784a9n%40googlegroups.com.

Re: [tw5] Re: Parameters into macros

[Saq Imtiaz]

Feel free to post here with your filter code (and of the macro) if you get 
stuck.

On Saturday, August 14, 2021 at 7:24:06 PM UTC+2 Stobot wrote:

> Thanks Saq, actually that sounds like an interesting challenge. From a 
> Javascript standpoint all I've done is tweak the macros of others so it may 
> be a bit over my head, but I'll give it a try. 
>
> On Sat, Aug 14, 2021 at 1:04 PM Saq Imtiaz  wrote:
>
>> The first thing that comes to mind is rewriting the macro as a filter 
>> operator.
>>
>>
>>
>> On Saturday, August 14, 2021 at 6:54:22 PM UTC+2 Stobot wrote:
>>
>>> Is there a way to pass dynamic parameters into macros (javascript) other 
>>> than using <$macrocall/>? 
>>>
>>> For instance I use a modified version of (Jed's I think) add-time.js 
>>> that allows you to use a parameter 'days' to feed days to add to current 
>>> date. So, doing something like <> would return the date 
>>> 10 days from now. If it's a static number like 10, things are easy, but if 
>>> it's dynamic (stored in a field) then things get more complicated - I have 
>>> to use the <$macrocall/> instead, which is less convenient but sometimes 
>>> not a problem. 
>>>
>>> It becomes a problem when I need to use this new date in a filter. I 
>>> *am* excited that in pre-release now we can feed *static* values as 
>>> parameters into macros within filters, but the missing piece is still 
>>> dynamic values as parameters - can't do a <$macrocall/> within a filter. 
>>>
>>> If it's a normal macro, right now I'd surround the <$list/> with some 
>>> <$wikify> runs that run the <$macrocall/>'s and wikify it to be fed in as a 
>>> static value. I'm just wondering if there's a better way that I'm not 
>>> thinking about (I end up with LOTS of wikify's which people tell me is not 
>>> great). 
>>>
>>> For instance, doing something like:
>>>  <$vars days={{!!daystoadd}}><$list 
>>> filter="[duedate]"> would work if it was a regular 
>>> macro instead of a javascript macro. But, even though the parameter that 
>>>  can be fed is called days, it's not picked up by the macro call. 
>>>
>>> Hopefully that makes sense - thanks
>>>
>> -- 
>> 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 tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/82fd0bc8-0322-4ef8-ba51-0b33342e8626n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/82fd0bc8-0322-4ef8-ba51-0b33342e8626n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2c8e661b-2c62-4f1e-b613-a536cb7ce005n%40googlegroups.com.

[tw5] Re: Parameters into macros

[Saq Imtiaz]

The first thing that comes to mind is rewriting the macro as a filter 
operator.



On Saturday, August 14, 2021 at 6:54:22 PM UTC+2 Stobot wrote:

> Is there a way to pass dynamic parameters into macros (javascript) other 
> than using <$macrocall/>? 
>
> For instance I use a modified version of (Jed's I think) add-time.js that 
> allows you to use a parameter 'days' to feed days to add to current date. 
> So, doing something like <> would return the date 10 days 
> from now. If it's a static number like 10, things are easy, but if it's 
> dynamic (stored in a field) then things get more complicated - I have to 
> use the <$macrocall/> instead, which is less convenient but sometimes not a 
> problem. 
>
> It becomes a problem when I need to use this new date in a filter. I *am* 
> excited that in pre-release now we can feed *static* values as parameters 
> into macros within filters, but the missing piece is still dynamic values 
> as parameters - can't do a <$macrocall/> within a filter. 
>
> If it's a normal macro, right now I'd surround the <$list/> with some 
> <$wikify> runs that run the <$macrocall/>'s and wikify it to be fed in as a 
> static value. I'm just wondering if there's a better way that I'm not 
> thinking about (I end up with LOTS of wikify's which people tell me is not 
> great). 
>
> For instance, doing something like:
>  <$vars days={{!!daystoadd}}><$list 
> filter="[duedate]"> would work if it was a regular 
> macro instead of a javascript macro. But, even though the parameter that 
>  can be fed is called days, it's not picked up by the macro call. 
>
> Hopefully that makes sense - thanks
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/82fd0bc8-0322-4ef8-ba51-0b33342e8626n%40googlegroups.com.

[tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Saq Imtiaz]

This is one of the first things that came up with a search, perhaps it may 
be of interest:
https://rawgit.com/Guitlle/habito/build/build/habito-docs.html

On Saturday, August 14, 2021 at 6:54:23 PM UTC+2 Saq Imtiaz wrote:

> Just to add a bit more clarification to the issue since I have a bit more 
> time now than I did yesterday, this functionality should have been 
> implemented as a widget and not a macro. I quickly dropped the link in 
> reply yesterday so you would know that there was some follow up on your 
> post.
>
> JavaScript macros in TiddlyWiki5 are supposed to be for simple text 
> substitution and do not have any facilities for refreshing in response to 
> other changes in the wiki, the input of the macro determines the output. A 
> macro should never modify tiddlers. The macro in question both needs to 
> refresh itself in response to tiddler changes, and also modifies tiddlers. 
>
> Such a macro was never intended to be supported but has worked so far 
> because we were aggressively refreshing entire tiddlers when anything in 
> that tiddler changed. So for example a change to a tiddler "list" field 
> would refresh the entire tiddler in the story. However this is suboptimal 
> both from a performance point of view and in terms of user experience. Some 
> of the annoyances commonly encountered like an edit-text widget in a 
> tiddlers text field not being usable to modify a field in the same tiddler 
> come from this aggressive and unnecessary refresh behaviour.
>
> So the question that presents itself now is whether we maintain backwards 
> compatibility for a behaviour from third party macros that was never 
> intended to be supported and holds back improvements, or break such macros 
> as their implementation will trip us up again in unexpected places and 
> limit future possibilities.
>
> Your actual need for the functionality offered by this macro could 
> probably be solved with a wikitext implementation as well. It might be 
> worth a search to see if someone has shared such a solution.
>
> Regards,
> Saq
>
> On Saturday, August 14, 2021 at 6:42:38 PM UTC+2 cmari wrote:
>
>> Thanks Saq, that was certainly not the answer I was hoping for, but it's 
>> good to know which way the wind is blowing after so many years (I think the 
>> original dailytasks plugin that got me started 13 years ago came from you?).
>> cmari (considering changing my name to "offspec user"!)
>>
>> On Friday, August 13, 2021 at 1:03:59 PM UTC-7 saq.i...@gmail.com wrote:
>>
>>> See 
>>> https://github.com/Jermolene/TiddlyWiki5/issues/5903#issuecomment-898691487
>>>
>>> On Friday, August 13, 2021 at 9:26:33 PM UTC+2 cmari wrote:
>>>
>>>> I have been a happy daily user of *Daily Task Macro *(
>>>> http://togglers.tiddlyspot.com/) for years, so I am wondering whether 
>>>> someone can point me to any tips for how I might update the macro so that 
>>>> it will continue to work in the new prerelease. 
>>>>  
>>>> Specifically, the fields in toggler tiddlers do continue to update 
>>>> correctly when the images are clicked, but the (svg) images themselves do 
>>>> not update in response to the click until the tiddler is opened and closed 
>>>> again.
>>>>
>>>> Thanks for any help!
>>>> cmari
>>>>
>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/58810d81-b325-426f-b065-35dd37eb2a83n%40googlegroups.com.

[tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Saq Imtiaz]

Just to add a bit more clarification to the issue since I have a bit more 
time now than I did yesterday, this functionality should have been 
implemented as a widget and not a macro. I quickly dropped the link in 
reply yesterday so you would know that there was some follow up on your 
post.

JavaScript macros in TiddlyWiki5 are supposed to be for simple text 
substitution and do not have any facilities for refreshing in response to 
other changes in the wiki, the input of the macro determines the output. A 
macro should never modify tiddlers. The macro in question both needs to 
refresh itself in response to tiddler changes, and also modifies tiddlers. 

Such a macro was never intended to be supported but has worked so far 
because we were aggressively refreshing entire tiddlers when anything in 
that tiddler changed. So for example a change to a tiddler "list" field 
would refresh the entire tiddler in the story. However this is suboptimal 
both from a performance point of view and in terms of user experience. Some 
of the annoyances commonly encountered like an edit-text widget in a 
tiddlers text field not being usable to modify a field in the same tiddler 
come from this aggressive and unnecessary refresh behaviour.

So the question that presents itself now is whether we maintain backwards 
compatibility for a behaviour from third party macros that was never 
intended to be supported and holds back improvements, or break such macros 
as their implementation will trip us up again in unexpected places and 
limit future possibilities.

Your actual need for the functionality offered by this macro could probably 
be solved with a wikitext implementation as well. It might be worth a 
search to see if someone has shared such a solution.

Regards,
Saq

On Saturday, August 14, 2021 at 6:42:38 PM UTC+2 cmari wrote:

> Thanks Saq, that was certainly not the answer I was hoping for, but it's 
> good to know which way the wind is blowing after so many years (I think the 
> original dailytasks plugin that got me started 13 years ago came from you?).
> cmari (considering changing my name to "offspec user"!)
>
> On Friday, August 13, 2021 at 1:03:59 PM UTC-7 saq.i...@gmail.com wrote:
>
>> See 
>> https://github.com/Jermolene/TiddlyWiki5/issues/5903#issuecomment-898691487
>>
>> On Friday, August 13, 2021 at 9:26:33 PM UTC+2 cmari wrote:
>>
>>> I have been a happy daily user of *Daily Task Macro *(
>>> http://togglers.tiddlyspot.com/) for years, so I am wondering whether 
>>> someone can point me to any tips for how I might update the macro so that 
>>> it will continue to work in the new prerelease. 
>>>  
>>> Specifically, the fields in toggler tiddlers do continue to update 
>>> correctly when the images are clicked, but the (svg) images themselves do 
>>> not update in response to the click until the tiddler is opened and closed 
>>> again.
>>>
>>> Thanks for any help!
>>> cmari
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/403ef6e8-2580-4497-811c-c498fd78n%40googlegroups.com.

[tw5] Re: Daily Task Macro - buttons no longer change color in 5.2.0-prerelease

[Saq Imtiaz]

See https://github.com/Jermolene/TiddlyWiki5/issues/5903#issuecomment-898691487

On Friday, August 13, 2021 at 9:26:33 PM UTC+2 cmari wrote:

> I have been a happy daily user of *Daily Task Macro *(
> http://togglers.tiddlyspot.com/) for years, so I am wondering whether 
> someone can point me to any tips for how I might update the macro so that 
> it will continue to work in the new prerelease. 
>  
> Specifically, the fields in toggler tiddlers do continue to update 
> correctly when the images are clicked, but the (svg) images themselves do 
> not update in response to the click until the tiddler is opened and closed 
> again.
>
> Thanks for any help!
> cmari
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fc2615e2-0b91-45f0-aaa3-af13323cec88n%40googlegroups.com.

[tw5] Re: Save to Github -- I keep getting "Error while saving: XMLHttpRequest error code: 404"

[Saq Imtiaz]

Is the target repository set to  Pumpapa/pumpapa.github.io ? I cannot be 
sure from the screenshot.

On Wednesday, August 11, 2021 at 9:25:56 PM UTC+2 pum.w...@gmail.com wrote:

> No luck. I tried main and tried retyping it.
> Note that the only branch is in fact master; I'm not sure why, given the 
> link you gave. I created the repo today.
>
> To be sure: what I should do is adapt these settings in 
> ControlPanel/Saving/Github Saver, and then hit save (Ⓥ), right?
>
>
> On Wednesday, August 11, 2021 at 4:14:27 PM UTC+2 Eric Shulman wrote:
>
>> On Wednesday, August 11, 2021 at 6:34:57 AM UTC-7 saq.i...@gmail.com 
>> wrote:
>>
>>> Where it says "master" for branch, try removing that text and typing it 
>>> back in manually.
>>>
>>> On Wednesday, August 11, 2021 at 3:32:03 PM UTC+2 pum.w...@gmail.com 
>>> wrote:
>>>
 Just installed 5.1.23 in a fresh github repo (Pumpapa/pumpapa.github.io
 )
>>>
>>>
>> As of Oct 1, 2020, all new GitHub repositories will use "main" instead of 
>> "master"
>>   (see https://www.infoq.com/news/2020/10/github-main-branch/)
>>
>> So, try setting the "Target branch for saving" to "main" instead of 
>> "master"
>>
>> -e
>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6bb7187b-eb4c-43aa-9e53-0a8eac8d1676n%40googlegroups.com.

[tw5] Re: Save to Github -- I keep getting "Error while saving: XMLHttpRequest error code: 404"

[Saq Imtiaz]

Where it says "master" for branch, try removing that text and typing it 
back in manually.

On Wednesday, August 11, 2021 at 3:32:03 PM UTC+2 pum.w...@gmail.com wrote:

> Just installed 5.1.23 in a fresh github repo (Pumpapa/pumpapa.github.io)
>
> When I try to set GitHub Saver (see attached screenshot) I get 
>   Error while saving:
>   XMLHttpRequest error code: 404
>
> made a fresh OAUTH token for this and tried it both in FF and Chrome 
> (under Linux).
>
> Access to the page is via a domain beginnings.blog (setup as described in 
> https://boffosocko.com/2020/04/04/self-hosting-tiddlywiki-with-github-pages/
> )
>
> Any suggestions would be helpful
>
>
> [image: Screenshot_2021-08-11_14-34-55.png]
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a1ebfe95-2b1f-4ae3-a598-081c2d5c1c95n%40googlegroups.com.

[tw5] Re: How to create a "save to github" button/trigger a save with a specific saver (single file wiki)?

[Saq Imtiaz]

OK I needed to be at a proper keyboard to write this out. Try the following:

\define myactions()
<$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all" 
publishFilter={{publishFilter}} />
<$action-setfield $tiddler="$:/GitHub/Username" text=""/>
\end

<$button tooltip={{GithubSave/Hint}} aria-label={{GithubSave/Caption}}  
class=<> actions=<>>
<$action-listops $tiddler="github save button/private/username" 
$tags="[[private]] [[github save button]]"/>
<$action-listops $tiddler="github save button/private/state" 
$tags="[[private]] [[github save button]]"/>
<$action-setfield $tiddler="$:/GitHub/Username" text={{github save 
button/private/username}}  />

<$list filter="[match[yes]]">
{{$:/core/images/github}}

<$list filter="[match[yes]]">
save to github




On Tuesday, August 10, 2021 at 8:32:33 PM UTC+2 Saq Imtiaz wrote:

> Ah right, I believe there is a race condition which is leading to the 
> double save. 
>
> On Tuesday, August 10, 2021 at 8:20:32 PM UTC+2 Saq Imtiaz wrote:
>
>> Regarding: " It would be best if I could save only to github thus never 
>> overriding my local wiki. Is that possible ?"
>>
>> Have you tried removing the second instance of  $action-sendmessage 
>> $message="tm-save-wiki" in your code?
>>
>> On Tuesday, August 10, 2021 at 8:00:43 PM UTC+2 Télumire wrote:
>>
>>> Hi Saq, 
>>>
>>> The code I shared at the end of my post already use these shadow 
>>> tiddlers.
>>> Thanks for the google thread, I'll try again and ask him for help if 
>>> need be. 
>>>
>>> I just hopped there was a way to do that in wiki text only, since I'm 
>>> not very good with JavaScript ^^
>>>
>>> Le mardi 10 août 2021 à 19:46:26 UTC+2, saq.i...@gmail.com a écrit :
>>>
>>>> I think bimlas' code has most of what you need and could easily be 
>>>> adapted for your purposes.
>>>> You may want to consider speaking with him, see 
>>>> https://groups.google.com/g/tiddlywiki/c/ZU_s6FdUy8Q/m/KeXVnOciBAAJ
>>>>
>>>> Also helpful might be the ability to create a custom save button that 
>>>> does not include the public content. See the following shadow tiddlers:
>>>> $:/core/ui/Buttons/save-wiki
>>>> $:/config/SaveWikiButton/Template
>>>> $:/core/save/all
>>>>
>>>>
>>>> On Tuesday, August 10, 2021 at 7:09:58 PM UTC+2 Télumire wrote:
>>>>
>>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I wish to use tiddlywiki as a semi-private blog using GitHub Pages 
>>>>> (with some of its content never going online until it's ready) and 
>>>>> thought 
>>>>> it would be nice to have a button that allow to choose what saver to use.
>>>>>
>>>>> For example, when I'm finished working on my article, I would hit the 
>>>>> regular save button and the changes would be saved locally. Then, when 
>>>>> I'm 
>>>>> satisfied, I would click a button to save to GitHub.
>>>>>
>>>>> The interesting thing is that we can set a filter to exclude some 
>>>>> tiddler from the save, so if I want to exclude an unfinished tiddler from 
>>>>> the save to GitHub, I would simply tag it with “private” or something 
>>>>> before saving the wiki.
>>>>>
>>>>> The issue is : tiddlywiki does not provide a mean to specify which 
>>>>> saver to use when triggering a save. 
>>>>>
>>>>> I found a workaround : I use a button which first fill in the GitHub 
>>>>> credential, increasing the priority of the GitHub saver, trigger the 
>>>>> filtered save, then remove the credential, allowing the next regular save 
>>>>> to be done with the local saver.
>>>>>
>>>>> The issue is that when I save to github this way, it also save 
>>>>> locally. So to prevent my private tiddlers from getting overridden by the 
>>>>> save, I need to trigger a complete save to finish the process. I think 
>>>>> this 
>>>>> is very risky because if the browser crash between the github save and 
>>>>> the 
>>>>> local save, all my private tiddlers will be lost. It would be best if I 
>>>>> could save only to github thus never overriding my loc

[tw5] Re: How to create a "save to github" button/trigger a save with a specific saver (single file wiki)?

[Saq Imtiaz]

Ah right, I believe there is a race condition which is leading to the 
double save. 

On Tuesday, August 10, 2021 at 8:20:32 PM UTC+2 Saq Imtiaz wrote:

> Regarding: " It would be best if I could save only to github thus never 
> overriding my local wiki. Is that possible ?"
>
> Have you tried removing the second instance of  $action-sendmessage 
> $message="tm-save-wiki" in your code?
>
> On Tuesday, August 10, 2021 at 8:00:43 PM UTC+2 Télumire wrote:
>
>> Hi Saq, 
>>
>> The code I shared at the end of my post already use these shadow tiddlers.
>> Thanks for the google thread, I'll try again and ask him for help if need 
>> be. 
>>
>> I just hopped there was a way to do that in wiki text only, since I'm not 
>> very good with JavaScript ^^
>>
>> Le mardi 10 août 2021 à 19:46:26 UTC+2, saq.i...@gmail.com a écrit :
>>
>>> I think bimlas' code has most of what you need and could easily be 
>>> adapted for your purposes.
>>> You may want to consider speaking with him, see 
>>> https://groups.google.com/g/tiddlywiki/c/ZU_s6FdUy8Q/m/KeXVnOciBAAJ
>>>
>>> Also helpful might be the ability to create a custom save button that 
>>> does not include the public content. See the following shadow tiddlers:
>>> $:/core/ui/Buttons/save-wiki
>>> $:/config/SaveWikiButton/Template
>>> $:/core/save/all
>>>
>>>
>>> On Tuesday, August 10, 2021 at 7:09:58 PM UTC+2 Télumire wrote:
>>>
>>>>
>>>> Hello everyone,
>>>>
>>>> I wish to use tiddlywiki as a semi-private blog using GitHub Pages 
>>>> (with some of its content never going online until it's ready) and thought 
>>>> it would be nice to have a button that allow to choose what saver to use.
>>>>
>>>> For example, when I'm finished working on my article, I would hit the 
>>>> regular save button and the changes would be saved locally. Then, when I'm 
>>>> satisfied, I would click a button to save to GitHub.
>>>>
>>>> The interesting thing is that we can set a filter to exclude some 
>>>> tiddler from the save, so if I want to exclude an unfinished tiddler from 
>>>> the save to GitHub, I would simply tag it with “private” or something 
>>>> before saving the wiki.
>>>>
>>>> The issue is : tiddlywiki does not provide a mean to specify which 
>>>> saver to use when triggering a save. 
>>>>
>>>> I found a workaround : I use a button which first fill in the GitHub 
>>>> credential, increasing the priority of the GitHub saver, trigger the 
>>>> filtered save, then remove the credential, allowing the next regular save 
>>>> to be done with the local saver.
>>>>
>>>> The issue is that when I save to github this way, it also save locally. 
>>>> So to prevent my private tiddlers from getting overridden by the save, I 
>>>> need to trigger a complete save to finish the process. I think this is 
>>>> very 
>>>> risky because if the browser crash between the github save and the local 
>>>> save, all my private tiddlers will be lost. It would be best if I could 
>>>> save only to github thus never overriding my local wiki. Is that possible ?
>>>>
>>>> I've found this js code by bimlas showing how to select a saver : 
>>>> https://bimlas.gitlab.io/demo/tw5/preferred-saver.html#%24%3A%2Fbimlas%2Fpreferred-saver.js
>>>>  
>>>> but I don't know how to adapt it to my scenario.
>>>>
>>>> Here's the code that I use for now :
>>>>
>>>> <$button tooltip={{GithubSave/Hint}} aria-label={{GithubSave/Caption}}  
>>>> class=<>>
>>>> <$action-listops $tiddler="github save button/private/username" 
>>>> $tags="[[private]] [[github save button]]"/>
>>>> <$action-listops $tiddler="github save button/private/state" 
>>>> $tags="[[private]] [[github save button]]"/>
>>>> <$action-setfield $tiddler="$:/GitHub/Username" text={{github save 
>>>> button/private/username}}/>
>>>> <$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all" 
>>>> publishFilter={{publishFilter}} />
>>>> <$action-setfield $tiddler="$:/GitHub/Username" text=""/>
>>>> <$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all"/>
>>>>
>>>> 
>>>> <$list filter="[match[yes]]">
>>>> {{$:/core/images/github}}
>>>> 
>>>> <$list filter="[match[yes]]">
>>>> save to github
>>>> 
>>>> 
>>>> 
>>>>
>>>> Live demo : 
>>>>
>>>>
>>>> https://telumire.github.io/TW-tips/#Save%20a%20private%20copy%20to%20github%20(single%20file%20wiki)
>>>>
>>>> You can import it in your wiki by drag & drop "'open all in the current 
>>>> tab" in tiddlywiki. Click once on the button, then fill in the username in 
>>>> the tiddler "github save button/private/username". 
>>>>
>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7f2dd21e-e916-48db-8f4a-bdf673273ab8n%40googlegroups.com.

[tw5] Re: How to create a "save to github" button/trigger a save with a specific saver (single file wiki)?

[Saq Imtiaz]

Regarding: " It would be best if I could save only to github thus never 
overriding my local wiki. Is that possible ?"

Have you tried removing the second instance of  $action-sendmessage 
$message="tm-save-wiki" in your code?

On Tuesday, August 10, 2021 at 8:00:43 PM UTC+2 Télumire wrote:

> Hi Saq, 
>
> The code I shared at the end of my post already use these shadow tiddlers.
> Thanks for the google thread, I'll try again and ask him for help if need 
> be. 
>
> I just hopped there was a way to do that in wiki text only, since I'm not 
> very good with JavaScript ^^
>
> Le mardi 10 août 2021 à 19:46:26 UTC+2, saq.i...@gmail.com a écrit :
>
>> I think bimlas' code has most of what you need and could easily be 
>> adapted for your purposes.
>> You may want to consider speaking with him, see 
>> https://groups.google.com/g/tiddlywiki/c/ZU_s6FdUy8Q/m/KeXVnOciBAAJ
>>
>> Also helpful might be the ability to create a custom save button that 
>> does not include the public content. See the following shadow tiddlers:
>> $:/core/ui/Buttons/save-wiki
>> $:/config/SaveWikiButton/Template
>> $:/core/save/all
>>
>>
>> On Tuesday, August 10, 2021 at 7:09:58 PM UTC+2 Télumire wrote:
>>
>>>
>>> Hello everyone,
>>>
>>> I wish to use tiddlywiki as a semi-private blog using GitHub Pages (with 
>>> some of its content never going online until it's ready) and thought it 
>>> would be nice to have a button that allow to choose what saver to use.
>>>
>>> For example, when I'm finished working on my article, I would hit the 
>>> regular save button and the changes would be saved locally. Then, when I'm 
>>> satisfied, I would click a button to save to GitHub.
>>>
>>> The interesting thing is that we can set a filter to exclude some 
>>> tiddler from the save, so if I want to exclude an unfinished tiddler from 
>>> the save to GitHub, I would simply tag it with “private” or something 
>>> before saving the wiki.
>>>
>>> The issue is : tiddlywiki does not provide a mean to specify which saver 
>>> to use when triggering a save. 
>>>
>>> I found a workaround : I use a button which first fill in the GitHub 
>>> credential, increasing the priority of the GitHub saver, trigger the 
>>> filtered save, then remove the credential, allowing the next regular save 
>>> to be done with the local saver.
>>>
>>> The issue is that when I save to github this way, it also save locally. 
>>> So to prevent my private tiddlers from getting overridden by the save, I 
>>> need to trigger a complete save to finish the process. I think this is very 
>>> risky because if the browser crash between the github save and the local 
>>> save, all my private tiddlers will be lost. It would be best if I could 
>>> save only to github thus never overriding my local wiki. Is that possible ?
>>>
>>> I've found this js code by bimlas showing how to select a saver : 
>>> https://bimlas.gitlab.io/demo/tw5/preferred-saver.html#%24%3A%2Fbimlas%2Fpreferred-saver.js
>>>  
>>> but I don't know how to adapt it to my scenario.
>>>
>>> Here's the code that I use for now :
>>>
>>> <$button tooltip={{GithubSave/Hint}} aria-label={{GithubSave/Caption}}  
>>> class=<>>
>>> <$action-listops $tiddler="github save button/private/username" 
>>> $tags="[[private]] [[github save button]]"/>
>>> <$action-listops $tiddler="github save button/private/state" 
>>> $tags="[[private]] [[github save button]]"/>
>>> <$action-setfield $tiddler="$:/GitHub/Username" text={{github save 
>>> button/private/username}}/>
>>> <$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all" 
>>> publishFilter={{publishFilter}} />
>>> <$action-setfield $tiddler="$:/GitHub/Username" text=""/>
>>> <$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all"/>
>>>
>>> 
>>> <$list filter="[match[yes]]">
>>> {{$:/core/images/github}}
>>> 
>>> <$list filter="[match[yes]]">
>>> save to github
>>> 
>>> 
>>> 
>>>
>>> Live demo : 
>>>
>>>
>>> https://telumire.github.io/TW-tips/#Save%20a%20private%20copy%20to%20github%20(single%20file%20wiki)
>>>
>>> You can import it in your wiki by drag & drop "'open all in the current 
>>> tab" in tiddlywiki. Click once on the button, then fill in the username in 
>>> the tiddler "github save button/private/username". 
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2836030f-2489-4f91-aec5-2f0d4cc6f973n%40googlegroups.com.

[tw5] Re: How to create a "save to github" button/trigger a save with a specific saver (single file wiki)?

[Saq Imtiaz]

I think bimlas' code has most of what you need and could easily be adapted 
for your purposes.
You may want to consider speaking with him, 
see https://groups.google.com/g/tiddlywiki/c/ZU_s6FdUy8Q/m/KeXVnOciBAAJ

Also helpful might be the ability to create a custom save button that does 
not include the public content. See the following shadow tiddlers:
$:/core/ui/Buttons/save-wiki
$:/config/SaveWikiButton/Template
$:/core/save/all


On Tuesday, August 10, 2021 at 7:09:58 PM UTC+2 Télumire wrote:

>
> Hello everyone,
>
> I wish to use tiddlywiki as a semi-private blog using GitHub Pages (with 
> some of its content never going online until it's ready) and thought it 
> would be nice to have a button that allow to choose what saver to use.
>
> For example, when I'm finished working on my article, I would hit the 
> regular save button and the changes would be saved locally. Then, when I'm 
> satisfied, I would click a button to save to GitHub.
>
> The interesting thing is that we can set a filter to exclude some tiddler 
> from the save, so if I want to exclude an unfinished tiddler from the save 
> to GitHub, I would simply tag it with “private” or something before saving 
> the wiki.
>
> The issue is : tiddlywiki does not provide a mean to specify which saver 
> to use when triggering a save. 
>
> I found a workaround : I use a button which first fill in the GitHub 
> credential, increasing the priority of the GitHub saver, trigger the 
> filtered save, then remove the credential, allowing the next regular save 
> to be done with the local saver.
>
> The issue is that when I save to github this way, it also save locally. So 
> to prevent my private tiddlers from getting overridden by the save, I need 
> to trigger a complete save to finish the process. I think this is very 
> risky because if the browser crash between the github save and the local 
> save, all my private tiddlers will be lost. It would be best if I could 
> save only to github thus never overriding my local wiki. Is that possible ?
>
> I've found this js code by bimlas showing how to select a saver : 
> https://bimlas.gitlab.io/demo/tw5/preferred-saver.html#%24%3A%2Fbimlas%2Fpreferred-saver.js
>  
> but I don't know how to adapt it to my scenario.
>
> Here's the code that I use for now :
>
> <$button tooltip={{GithubSave/Hint}} aria-label={{GithubSave/Caption}}  
> class=<>>
> <$action-listops $tiddler="github save button/private/username" 
> $tags="[[private]] [[github save button]]"/>
> <$action-listops $tiddler="github save button/private/state" 
> $tags="[[private]] [[github save button]]"/>
> <$action-setfield $tiddler="$:/GitHub/Username" text={{github save 
> button/private/username}}/>
> <$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all" 
> publishFilter={{publishFilter}} />
> <$action-setfield $tiddler="$:/GitHub/Username" text=""/>
> <$action-sendmessage $message="tm-save-wiki" $param="$:/core/save/all"/>
>
> 
> <$list filter="[match[yes]]">
> {{$:/core/images/github}}
> 
> <$list filter="[match[yes]]">
> save to github
> 
> 
> 
>
> Live demo : 
>
>
> https://telumire.github.io/TW-tips/#Save%20a%20private%20copy%20to%20github%20(single%20file%20wiki)
>
> You can import it in your wiki by drag & drop "'open all in the current 
> tab" in tiddlywiki. Click once on the button, then fill in the username in 
> the tiddler "github save button/private/username". 
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3be10022-af21-4cfd-99b0-4c1ec77a1f21n%40googlegroups.com.

[tw5] Re: tiddlywiki.info : would a "includeFiles" property make sense?

[Saq Imtiaz]

tiddlywiki.files might do the 
trick: https://tiddlywiki.com/#tiddlywiki.files%20Files

I use them to load files from a subfolder of the wiki tiddlers folder. I do 
believe you could have a tiddlywiki.files file in a subfolder of tiddlers 
that then uses relative paths to files outside that the tiddlers directory.

Also note that if you create a files folder parallel to the tiddlers 
folder, any files in that files folder will be served by the integrated 
static file server at the path /files/
See https://tiddlywiki.com/#Using%20the%20integrated%20static%20file%20server


On Tuesday, August 10, 2021 at 5:01:37 PM UTC+2 cj.v...@gmail.com wrote:

> As I play around with TiddlyWiki on node.js, I had a thought ...
>
> Say I have a folder somewhere with all of my camera pictures, and I want a 
> particular file to be included in a TiddlyWiki, I'm thinking it would be 
> pretty nice to add that to my tiddlywiki.info file, something like:
>
> "includeFiles": [
> {"file": "home/picture/my_dog.jpg",
>  "file": "home/documents/my_dog_pedigree.pdf"}
> ]
>
> It would probably make more sense to have a file server for the files when 
> dealing with a lot of files being included in a lot of TiddlyWikis, but I 
> wonder if this kind of "includeFiles" thing would be useful in certain 
> circumstances.
>
> Or is there already a mechanism for doing this kind of thing? 
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/675870e2-d710-4c61-8b24-995700326786n%40googlegroups.com.

[tw5] Re: Regex Character Classes not working in search-replace

[Saq Imtiaz]

>
>  It works fine with the shortcut class \w, but if I replace that with 
> [a-zA-Z0-9_] it breaks, when logically those should be the same. 


You cannot have the characters [ and ] inside a literal operand to a filter 
operator.
The workaround is to define the regular expression as a variable and then 
use the variable as the operand.

Pseudo code below.

\define myregexp() ((?:.*\s)|^)([a-zA-Z0-9_]+$)

\define compare-by-last-name-with-character-class()
[search-replace:i:regexp,[$2, $1]]
\end

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1de53a2-5e56-4d28-be4b-88395db2f76cn%40googlegroups.com.

[tw5] Re: Dreaming of "TidEdit", an in-browser TiddlyWiki WikiText editor

[Saq Imtiaz]

I suspect you would find this prototype by JD of interest:
http://j.d.fullscreen.tiddlyspot.com/

Click the "fullscreen" button in the tiddler toolbar, and then turn on the 
preview in the editor.

TiddlyWiki has a mechanism to allow you to switch between page layouts 
. So one could 
imagine an alternative page layout which only shows a single tiddler using 
such a fullscreen presentation in edit mode. In other words, I don't think 
you need to grab existing bits out of TiddlyWiki, an alternative layout 
would do the trick. Defining an alternative page layout is all about 
wikitext, HTML and some CSS.

Based on what I have seen of your tiddly tweaking, I am pretty sure this 
would be well within your means if you decided to give it a go.
Regards,

Saq

On Saturday, August 7, 2021 at 4:28:57 AM UTC+2 cj.v...@gmail.com wrote:

> Something like StackEdit , but to create and 
> edit TID files using TiddlyWiki WikiText.
>
> Essentially just a web page (a seriously stripped-down TiddlyWiki?) that 
> looks like a single tiddler in edit mode.  With nothing else except:
>
>- a save button to download the content as a TID file
>- an open button, to find and open an existing TID file
>- a new button to start editing a new TID
>- *minus* some of the edit buttons that normally exist in a TiddlyWiki
>   - excise button
>   - wikitext link button
>   - wrap in square brackets button
>   - wrap in curly brackets button
>   - insert picture button
>   - insert pre-configured snippet of text button
>   - choose the height of the text editor button
>- minus the "tiddler type" and "add a new field" bits
>
> Why?  I like the concept of simple markdown editors for quick 
> note-taking.  
>
> I could use a simple text editor to create and save TID files, but having 
> something like StackEdit as a single HTML file meant for editing TID's, 
> with the preview pane right there like these markdown editors ... that 
> would be pretty frigging cool.
>
> Of course, I do not have the coding chops to build something like this.  I 
> imagine for somebody who knows what he/she is doing, it would be a matter 
> of grabbing the useful pre-existing bits right out of TiddlyWiki.
>
> I'm hoping somebody might find this dream of mine interesting enough, the 
> kind of editor useful enough, to slap it together?
>
> A simple "TidEdit" editor for quick note-taking.  Running in the browser 
> on any device.  That would be pretty cool.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1daa9e91-a3d4-4db5-9c95-e8cc9214210en%40googlegroups.com.

[tw5] Re: filter operator: sort by last part of title

[Saq Imtiaz]

See this thread

https://groups.google.com/g/tiddlywiki/c/ZXunGNpbG4c/m/ZIzuFq5iAQAJ
On Friday, August 6, 2021 at 5:54:09 PM UTC+2 Mohammad wrote:

> 1. goto https://tiddlywiki.com/prerelease/
> 2. create three tiddlers with below titles all tagged with xtx as below
> one: first
> two: second
> three: third
>
> 3. In another tiddler enter the below code
>
> \define myfilter() [split[:]last[]trim[]!sort[]]
> <$list filter="[tag[xtx]filter]">
>
> 
>
> 4. The expected result is
>
> three: third
> two: second
> one: first
>
> BUT it does not work! What is wrong here?
>
>
> Best wishes
> Mohammad
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/055f2af6-da9b-4f11-a6e1-1d2ff5ee0ba5n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

Hi Mark,

That sounds very disconcerting. Please do let me know if you discover a way 
to recreate the problem.
It seems particularly odd that the configuration tiddlers were affected as 
neither the text splitting code nor relink should be touching those.

There have been problems in the past where splitting longer text into nodes 
using alt+enter and having the configuration for new nodes to use the 
unusedtitle macro resulted in some nodes not being visible in the Stream. I 
have attempted to fix that but it is an area that needs further attention 
and upcoming changes in TW 5.2.0 will help clean it up. However, even if 
that bug is resurfacing, it would not explain the issue with configuration 
tiddlers. I will review the code for splitting longer text into multiple 
tiddlers once more.

Saq


On Friday, August 6, 2021 at 3:55:15 AM UTC+2 Mark S. wrote:

> There might be a problem with the text splitter, or maybe relink or relink 
> with the text splitter.  I was looking at my sample Streams file and found 
> I couldn't see any of the notes I had made previously. But all the tiddlers 
> were still in the TW. After some examination, I found that several Streams 
> configuration tiddlers had swapped titles (or swapped contents, depending 
> on your perspective) There were at least a half dozen such configuration 
> tiddlers. So Maximum node width 
> <#m_5305531832700594985_%24%3A%2Fconfig%2Fsq%2Fstreams%2Fnode-max-width>
>  had \n\n in it and so forth. 
>
> I don't see how that could have happened without code that actually 
> changes things. So either relink got something messed up, or the text 
> splitter moved titles around. None of the code I've added (my own search 
> section) changes tiddler's names or contents. The only other code I've used 
> is the command palette, which I've now disabled.
>
> I know this isn't very helpful, but in case someone else encounters 
> similar problems it may help narrow things down. 
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8eac74ed-5cdc-4b5e-94d8-5fb2dee6n%40googlegroups.com.

[tw5] Re: How do I store fields inside *.md files? As if it were a .tid file, without separating fields to the .meta file

[Saq Imtiaz]

 

> I'm not sure if we can and if we should provide this functionality. ... 
> Markdown editors expect a common format if they read .md files. Using TW 
> fields at the top is not standard for markdown.
>

Agreed. If we do add support for meta data in markdown files it would then 
be prudent to consider the YAML frontmatter format which is becoming quite 
commonplace:
https://jekyllrb.com/docs/front-matter/ 
https://gohugo.io/content-management/front-matter/

Now I better duck before Jeremy throws something at me for mentioning YAML.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/bb9faba8-d881-4770-b38e-99a0c0d7dd4cn%40googlegroups.com.

[tw5] Re: Notation editor

[Saq Imtiaz]

Hi Arun,

While I use Notation every day, I haven't had the chance to update it for 
the current core version even for myself since the time of that video. So a 
public release is extremely unlikely. Furthermore I will not be posting a 
demo of the existing code. My experience with sharing public demos has been 
very disappointing in that there are always user who will ignore all 
warnings and disclaimers and try to use the code, run into issues and 
create support work for myself and/or the community that there is never a 
good way to resolve, and I personally feel this reflects poorly on 
TiddlyWiki as a whole. This is why all recent demos I have shared have been 
via videos even though I find that a suboptimal medium.

I have spent whatever time I could spare since the time of that demo on 
slowly introducing to the TiddlyWiki core all of the custom (JavaScript) 
solutions that I had developed for Notation, as well as filters etc that 
make the implementation a lot easier than it was originally. 

*As a result, today anyone experienced with wikitext coding can create a 
similar UX entirely in wikitext.*

A while back before the 5.1.23 release I also posted a demo of a similar 
but simpler UX that used the keyboard-driven-input macro. It displayed the 
editor using my Floats prototype, but could just as easily be shown in a 
modal. That might be a starting point.

I have to say that I still don't think that particular UX and workflow 
would be of interest to most TiddlyWiki users... I use it essentially like 
a text editor with very little usage of other TiddlyWiki features.

If you just want to get an idea of what the user experience is like, it 
modelled after the free OSX application Notational Velocity,  which has a 
newer fork called NValt and a windows clone called ResophNotes. Perhaps 
give one of them a whirl and see if it even makes sense for your workflow.

Cheers,
Saq
On Wednesday, August 4, 2021 at 5:09:28 PM UTC+2 arunn...@gmail.com wrote:

> This is the link  to a 1yr old tiddlywiki 
> hangout video with Saq where he is showing his workflow using Notation 
> editor. I first saw this video one year back when I started using 
> tiddlywiki. I don't think I fully understood the implementation at that 
> point. Yesterday I thought of seeing it again. I haven't seen any other 
> similar implementation in tiddlywiki yet and I wish to use it in my wiki 
> also. But I know that Saq doesn't have enough time to release it for public 
> use as he had told here 
> . 
> May be someone else gets inspired by seeing this video and build a similar 
> plug in for tiddlywiki. Or may be one day Saq can release it at least as a 
> proof of concept, so that we can just experience what we see in that video. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/16986d82-9c89-42fc-b90c-c8bca5c18d4dn%40googlegroups.com.

[tw5] Re: How do I store fields inside *.md files? As if it were a .tid file, without separating fields to the .meta file

[Saq Imtiaz]

Look at the section on "File System Extensions" 
at https://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming

On Wednesday, August 4, 2021 at 12:53:46 PM UTC+2 Shareda wrote:

>
> Hello! I am setting up my workflow using TiddlyWiki 5.1.23 on Node.js. 
> I would like to store and edit all of my tiddlers within the *.md files 
> with all their fields.
>
> How can I switch off the generating of the separate *.meta files for MD 
> format and store the filds the same way as they are stored in .tid files ? 
>
> My own research is about to fail :^)

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0bc282f3-99ba-4efd-9d26-cab3a6d6148cn%40googlegroups.com.

Re: [tw5] Re: Picture based tiddlers

[Saq Imtiaz]

>
> Great Ideas so far. From a developer standpoint, I can recommend the Imgur 
> API for integration. Not only does it give flexibility and a high number of 
> photo uploads per day, but it is also relatively easy to use and combine 
> with existing technologies (ie tiddlywiki in this case.) 
> I would love to build a JS plug-in or tool for TW with this, if any of you 
> are interested. 
>
>>
>>
As Joshua mentioned, there is a file uploads plugin in development that 
supports different uploader modules to support storage backends:
https://github.com/saqimtiaz/tiddlywiki-on-fission/tree/main/upload-files-wiki/plugins/file-uploads

 Writing an Imgur uploader module would indeed be interesting.  The tricky 
bits to figure out would be CORS and authentication. If that is something 
you are interested in working on, I would be happy to discuss further. 

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5e44e579-6a3c-487c-817f-0fcb5cb67bc6n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

@fred
 

> Everything I have tried works but it seems the node still doesn't reflect 
> its new (merged) content; escaping and double clicking to edit again then 
> reflects the new content. It feels like I activate the node's edit mode 
> before the changes have taken place even if the code had the sequence in 
> the right order. Is it a rendering timing issue?
>

When a streams node is presented in edit mode, the core edit-widget that 
creates the input field gets focus. The edit-widget will not update its 
content while it has focus. This I believe was implemented in this manner 
in the core so that refreshes while typing would not lead to data loss or 
the input field suddenly changing while typing.

So it does sound like the node is switched to edit mode too early. The 
timing of actions within a single block of action strings is a bit tricky 
to work with in such situations. I have had issues in the past with the 
opposite, where the editing input field doesn't yet exist when I try to 
focus it with an action string. If you have code that I can look at, I may 
be able to suggest workarounds.
 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1ba9d09-586c-48ac-ac44-8f898712dec1n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

@Fred +1 for making use of the settings UI templates

Note that the settings UI code might change at some point in the future. 
The settings related stuff might get split off into its own plugin that any 
other plugin can make use of if its present, but it shouldn't be a big 
change adapting to that.

On Friday, July 30, 2021 at 5:57:27 PM UTC+2 fred@gmail.com wrote:

> @walt  please give 0.0.7-beta a try; apologies for the poor release 
> quality: http://fastfreddy.gitlab.io/streams-fusion/
>
> @tones to answer your earlier question; the button display logic is 
> provided by Saq (in response to Jan initially I think) in this tiddler 
> $:/plugins/sq/streams/nodes-list-template using this snippet
>
> <$list filter="[all[shadows+tiddlers]tag[$:/tags/streams/root-buttons]]" 
> variable="btnTiddler">
> 
> <$transclude tiddler=<>/>
> 
> 
>
> my $:/plugins/phiv/streams-fusion/fuse-button button has the 
> $:/tags/streams/root-buttons; please note the snippet above is only 
> displayed on a stream root node.
>
> Were you able to try an import on a plain Streams-enabled notebook?
>
> On Fri, 30 Jul 2021 at 10:47, Frédéric Demers  wrote:
>
>> @walt; that is an oversight. I clearly didn't test well enough. I'll try 
>> to fix ASAP.
>>
>> On Fri, 30 Jul 2021 at 10:37, ludwa6  wrote:
>>
>>> Hey @fred: That's a significant upgrade, in terms of functionality and 
>>> polish -all good, except: 
>>>
>>> I seem to have lost the nifty functionality that came with v0.0.3-beta, 
>>> which was handling cleanup of superflous node tiddlers so nicely as part of 
>>> fuse process. 
>>>
>>> Unfortunately: i can't say for sure if this is directly attributed to 
>>> v0.0.6-beta upgrade, because -prior to upgrade- i took the step of deleting 
>>> those 5 tiddlers related to the streams-to-text addon 
>>> . Was that a mistake i wonder?
>>>
>>> Anyway Fred: would love to have that lost cleanup function back, if 
>>> there's anything you can do for me - much obliged!
>>>
>>> /walt
>>>
>>>
>>> On Friday, July 30, 2021 at 12:56:53 PM UTC+1 fred@gmail.com wrote:
>>>

 Greetings everyone, version 0.0.6-beta of Streams-fusion 
  is out. It's quite a 
 bit more flexible and can output raw HTML and/or directly to clipboard. 
 Quick settings available directly from the popup menu (more settings at 
 the 
 bottom of the Streams settings screen, including a fused stream name 
 template option).

 Be careful with the "overwrite stream" option. It seems to work well 
 in full trees or in branches (via node context menu), but nonetheless, 
 backups are recommended

> ...

 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/1f745482-a72b-4d81-a8ef-878beaaecc9cn%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "TiddlyWiki" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> tiddlywiki+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/553fc5ae-a897-42c3-a653-6f32b2a58118n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2d073e79-1f96-4c1c-b931-e37faa6f8f1cn%40googlegroups.com.

Re: [tw5] New JSON Store Area Now in v5.2.0 Prerelease

[Saq Imtiaz]

@Mohammad I recommend posting this as an issue 
at https://github.com/flibbles/tw5-uglify

On Sunday, August 1, 2021 at 8:41:52 AM UTC+2 Mohammad wrote:

> I am testing Tiddlywiki 5.2.0 p with different plugins I use.
>
> Today I noticed Uglify (Uglify — Plugin compression made easy 
> (flibbles.github.io) ) which is 
> used to compress JS and make TW a smaller html works in reverse order!
> I mean using Uglify makes TW 5.2.0 single html files with basic plugins 
> (codemirror, highlight.js, katex,...) get larger in size!
> Strangely I do the unglifing several times, each time I get a bigger file! 
> This is not the case with TW 5.1.23
>
> @flibbles would you please have a look!
>
>
>
> Best wishes
> Mohammad
>
>
> On Wed, Jul 14, 2021 at 4:05 PM Jeremy Ruston  wrote:
>
>> It doesn’t sound very exciting, but the new JSON-based store area has now 
>> been merged into the prerelease.
>>
>> https://tiddlywiki.com/prerelease/
>>
>> This is the big change that has prompted us moving from v5.1.23 to 
>> v5.2.0. It brings one major benefit to all users of TiddlyWIki: the 
>> characters used in field names are now unrestricted, making it possible to 
>> use fieldnames like "My^Field” or “☃️”.
>>
>> While that is an important change that we hope will lead to the 
>> development of interesting new techniques for working with data in 
>> TiddlyWiki, the biggest risk of this change is that it is not fully 
>> backwards compatible.
>>
>> That is to say that *any tools that work directly with TiddlyWiki files 
>> will no longer work as expected, and need updating to understand the new 
>> format*.
>>
>> The new format is documented here:
>>
>>
>> https://tiddlywiki.com/prerelease/dev/#Data%20Storage%20in%20Single%20File%20TiddlyWiki
>>
>> We have tried to anticipate the problems that this change might cause, 
>> for example working with Simon Baird to fix TiddlyHost ready for the 
>> change. You can follow the technical discussions here:
>>
>> https://github.com/Jermolene/TiddlyWiki5/pull/5708
>>
>> But now we need everyone’s help to try the new version, to help us 
>> identify any incompatibilities before the final release.
>>
>> Please try the prerelease with as many different saving mechanisms and 
>> server backends as possible. You can report any problems here, or by 
>> opening a new ticket on GitHub.
>>
>> For me personally this feels like a big milestone. TW5 has used the same 
>> DIV-based tiddler store area since the very beginning in 2011, having 
>> directly inherited it from TiddlyWiki Classic. I reused the old format to 
>> give TW5 compatibility with the ecosystem of tools around TiddlyWiki 
>> Classic. Now that the TW5 ecosystem is so much bigger, it makes sense to 
>> move to a store area format that has fewer restrictions and is easier for 
>> developers to work with.
>>
>> Just for fun, I wrote a Node.js one-liner to extract the tiddlers from a 
>> TiddlyWiki HTML file. In contrast, a few hundred lines were needed to read 
>> the old format:
>>
>> var 
>> 

[tw5] Re: Difference between two timestamps in elapsed time?

[Saq Imtiaz]

Hiya BTC,

It occurs to me that the format:relativedate[] operator could be extended. 
It currently calculates the date relative to now and does not accept any 
parameters. It could be extended to accept a parameter indicating the date 
to compare to, as well as perhaps a format string. The challenge would be 
getting the syntax right so it is intuitive to use.
Might be worth creating a github issue or even a PR if you feel up to it.

Regards,
Saq

On Tuesday, July 27, 2021 at 10:12:37 AM UTC+2 BurningTreeC wrote:

>
> Hi there, tiddlywikians
>
> Let's say I have two timestamps and I want to get the elapsed time from 
> one timestamp to the other, is there a simple way to get this?
>
> I calculate the difference between the timestamps by
>
> <$set name="timestampDiff" value={{{ [subtract] 
> }}}>
> <>
> 
>
> I would appreciate any help :)
>
> best wishes,
> Simon
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e0b62bba-e25b-4ef1-8dc3-46e12d75bd94n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

[Saq Imtiaz]

Hi Flibbles,

No significant changes to saving no node.js. Currently tiddlers of type 
text/vnd.tiddlywiki are saved as .tid, files unless they have mutliline 
fields in which case those tiddlers are saved as .json files. This will 
remain the same with the addendum that a tiddler with field names with a 
colon in them will also be saved as a .json file. 

Saq

On Saturday, July 24, 2021 at 9:21:17 PM UTC+2 Flibbles wrote:

> Hey all,
>
> Question: Is this going to impact the way NodeJS servers saves tiddlers to 
> file? Will they no longer be .tid files, and maybe be .json files instead?
>
> -Flibbles
>
> On Friday, July 23, 2021 at 9:53:46 PM UTC-4 TW Tones wrote:
>
>> Springer,
>>
>> From a design perspective for column headings I would stick to a standard 
>> fields such as column-heading with the value"" on a tiddler called 
>> "tennis", or as the case may be a sport tiddler.
>>
>> Already dynamic tables support alternate column names in a standard 
>> field/value and there is not reason in my view to tamper with fieldnames.
>>
>> I am sure there are reasons, but your suggestion to me, is like I posted 
>> previously, you may be about to hang yourself with the extra rope you have 
>> being given for field names. I would avoid this excursion unless you can 
>> establish a good reason otherwise you are possibly forgoing the ability to 
>> use your tiddlers, with the large library of plugins and macros that have 
>> gone before.
>>
>> Just my viewpoint
>> Tones
>>
>>
>> On Friday, 23 July 2021 at 23:58:23 UTC+10 springer wrote:
>>
>>> Mario,
>>>
>>> Thanks for the bracket fix! (I should have caught that, but was getting 
>>> bleary-eyed.)
>>>
>>> When you say, "you mainly test with tiddler titles, and not fields. Even 
>>> if you have strange field names...," I'm not sure what you mean. I have 
>>> focused mostly on having strange field names that correspond to strange 
>>> tiddler titles, partly because I anticipate that the newly open field-name 
>>> space will get half its value from letting field names correspond to 
>>> tiddler titles. And because of the centrality of Shiraz to my own workflow, 
>>> I have been testing how Shiraz (especially dynamic tables) behaves with the 
>>> new field name possibilities.
>>>
>>> My other anticipated use for strange field names is to serve as compact 
>>> headings in dynamic tables, where the difference between "tennis" and  or 
>>> "recyclable" and ♻︎ (in a field with √ or X values) is conservation of 
>>> horizontal table space.
>>>
>>> So: What other kinds of tests do you (and others) see as important? 
>>> Though my coding skills are minimal, the challenge to test the limits of a 
>>> new feature is one area where I enjoy chipping in as best I can.
>>>
>>> -Springer
>>>
>>> On Friday, July 23, 2021 at 8:37:23 AM UTC-4 PMario wrote:
>>>
 Hi,
 Nice tests, but you mainly test with tiddler titles, and not fields. 
 Even if you have strange field names in your tiddlers. 


 https://springerspandrel.github.io/tw/new-json-tw-experiment.html#Show%20related%20field-table%20(ViewTemplate)
  
 .. The filter is probably broken, because the number of opne/close braces 
 are wrong. The last closing brace is missing ...first[]]

 BUT I didn't test the code. 

 -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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a221df3d-3386-4aa0-bffd-f8632bff0967n%40googlegroups.com.

[tw5] Re: Announcing Editor-Autolist-Markdown

[Saq Imtiaz]

>
> Inheriting from Saq's implementation (and I'm not sure if there's any 
> other way to do it), editor-autolist-markdown works via an 'invisible' 
> toolbar button with the assigned key shortcuts.
>

The alternative would be trying to add event listeners for the keydown 
event to the text area via JavaScript. I think the toolbar button approach 
is a lot more flexible.
 

> This could be addressed by how the Big Text Area is implemented. I'm sure 
> it is more difficult to implement, but it is possible to turn the toolbar 
> invisible rather than removing it via <$reveal>. If the style "display: 
> none" is added to the div containing the toolbar (I think by default it is 
> .tc-text-editor-toolbar-item-wrapper) this would do it. (This would also 
> bring back your bold, italic, etc.)
>

This is precisely how Streams hides the toolbar. All toolbar buttons that 
don't display a popup continue to work via keyboard shortcuts. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/948f1c0d-c30d-4b6a-852a-09b2d097ba5an%40googlegroups.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Saq Imtiaz]

Hi Soren, I mentioned this when I suggested the filter and explained in a 
bit more detail in  a follow up reply which seems to never have been posted.

 You will need the 5.2.0 pre-release for that filter to work, as one of the 
changes is greater consistency in setting the value of currentTiddler for 
:filter, :reduce and :sort and their operator equivalents.  
See  https://tiddlywiki.com/prerelease/#Filter%20Expression

On Friday, July 23, 2021 at 2:17:24 AM UTC+2 Soren Bjornstad wrote:

> Tones, thanks for putting this together, but your solution is slower than 
> mine as far as I can tell (no easy way to instrument that since it has a 
> very different number of filters, but the difference is apparent from 
> clicking around a bit).
>
> Saq, I can't get your filter to work and I can't see how it would work in 
> theory either now that I look at it – the !!condition in the subfilter is 
> getting the condition field on the tiddler in which the tab list is being 
> rendered, whereas it needs to be the *tab* tiddler that's coming in on 
> the input of the subfilter operator…right? Or am I just being dense? In my 
> :reduce version it has a different meaning because :reduce actually 
> resets the currentTiddler variable to match the input value currently being 
> processed .
>
> With the additional optimization work I did the other night, including 
> optimizing the filters on each tab as Saq pointed out, I would say it's now 
> performing acceptably with my current version, if only barely on a slower 
> computer. So if nobody has any other ideas, I think I can leave it where it 
> is for now.
>
>
> On Wednesday, July 21, 2021 at 8:58:05 AM UTC-5 TW Tones wrote:
>
>> Oops;
>>
>> I must add
>> the tab template contains
>>
>> <$tiddler tiddler=<>>
>> <$transclude mode="block" />
>> 
>>
>> and each tab contains 
>> <$list filter={{!!filter}}>
>>
>> 
>>
>> The tabs work stand alone
>>
>> Tones
>>
>> On Wednesday, 21 July 2021 at 23:55:11 UTC+10 TW Tones wrote:
>>
>>> Soren,
>>>
>>> Given this thread, I am not sure if I am on track here, but reading your 
>>> Original post it seems so.
>>>
>>> As I understand it you want to use a filter in a tab tiddler to 
>>> determine if it should have the tab displayed.
>>>
>>> The thing is the tabs macro is not designed for conditional tab display, 
>>> it simply wants a list of tiddlers. If this could all be rammed into a 
>>> single filter then all would be fine. However you not only want to make use 
>>> of another variable or in this case a field but that field contains a 
>>> filter. This is asking too much of the filter syntax.
>>>
>>> What I have done in my solution was to generate the list of tiddlers 
>>> that would be tabs according to you conditions and feed only the result to 
>>> the tabs macro.
>>>
>>>- In my small test not performance issues, and I do not expect their 
>>>to be
>>>- I think what is happening in your case if the reduce etc... is 
>>>adding unnecessary complexity to the performance of the tabs macro.
>>>
>>>
>>> Here is the core logic tested on tiddlywiki.com and pre-release 
>>> incidentally.
>>>
>>> \define tabs-with-content()
>>> <$list filter="[tag[Tag]]" >
>>><$list filter="[all[current]get[filter]]" variable=found-filter>
>>>   <$list 
>>> filter="[subfiltercount[]!match[0]then]">
>>>
>>>
>>>
>>> 
>>> \end
>>>
>>> <$wikify name=tabs-with-content text="<>">
>>> <$macrocall $name=tabs tabsList=<> 
>>> template="tabtemplate"/>
>>> 
>>>
>>> If this does not make sense I will package the tiddlers in this test for 
>>> you.
>>>
>>> The above example may be a good test case if we wanted to invent a 
>>> method to make filters more sophisticated basically permit ones that allow 
>>> you to avoid the nested lists I used, however as stated previously dont be 
>>> shy using nested lists, because each level of nesting allows to generate a 
>>> new variable and keep the old ones in this case found-filter while keeping 
>>> currentTiddler from the first filter.
>>>
>>> My preference would be a shorthand method when presenting variables as a 
>>> parameter, in this case <> such that it is first 
>>> wikified rather than using the ungainly wikify widget and its need to wrap 
>>> the macro call. Eg a a parameter ((tabs-with-content)) or in filters 
>>> (tabs-with-content)
>>> Alternatively TiddlyWiki would detect the need for wikification of that 
>>> variable/macro and do it itself.
>>>
>>>
>>> Regards
>>> tones
>>>
>>>
>>> On Wednesday, 21 July 2021 at 22:15:12 UTC+10 Soren Bjornstad wrote:
>>>
 Saq, the intermittent refresh every 5 seconds updates a clock and 
 Pomodoro timer. The reason it's puzzling is that it doesn't appear by 
 default in the public edition. If you're curious, tick the "clock" 
 checkbox 
 in the FeatureFlags tiddler.

 I'll give the :filter version a try later. I suspect I didn't think to 
 use filter and subfilter 

[tw5] Re: Excising Large Outlines in TW

[Saq Imtiaz]

Mark you can save a plugin tiddler as a 
folder: https://links.tiddlywiki.com/urls/4b5e9c4afc6923035ef9/

Otherwise you can drag and drop the plugin to your wiki and import it and 
it will work, though it will only be installed for that specific wiki to 
which you dragged it.

On Thursday, July 22, 2021 at 9:57:01 PM UTC+2 mark.cu...@gmail.com wrote:

> @David
> Is there a plugin folder to download. I'm not convinced I know how to 
> install your plugin otherwise. I'm running TW via Node.js.
> On Wednesday, July 21, 2021 at 3:44:45 PM UTC-4 Mark Cubberley wrote:
>
>> @David
>> I have been keeping my eye on the Subsume threads and this plugin may be 
>> what I'm looking for. Between my naiveté of TW and, for the moment, a 
>> rather nebulous pedagogical project, I am not convinced I know what I'm 
>> asking, but I appreciate the reply nonetheless.
>>
>> @ Mark S.
>> You are correct. More often than not, there IS too much material and I my 
>> intent is not to add more to an already dense curriculum. I see systems 
>> thinking as pedagogical strategy/framework for my teaching. (Systems 
>> thinking in chemical education is new to me and to chemical education for 
>> that matter.) I do not yet know what content I may have to sacrifice to use 
>> this pedagogy, nor if the loss of this content compromises the learning 
>> objectives of the course(s). I am hoping to figure all this out in a public 
>> facing TW using these concept outlines as a knowledge base.
>> On Wednesday, July 21, 2021 at 2:04:41 PM UTC-4 Mark S. wrote:
>>
>>> The official slicer edition does pretty much what you describe 
>>> https://tiddlywiki.com/editions/text-slicer/ .
>>> But it uses a complicated relationship between the resulting tiddlers 
>>> that may be difficult to manipulate.
>>>
>>> Notowritey (https://marxsal.github.io/various/notowritey.html) allows 
>>> you to split large texts using a regular expression. You can then 
>>> manipulate items into a hierarchical arrangement in a manner similar to a 
>>> regular outliner. The relationship is based on simple listing and tagging.
>>>
>>> I would imagine for a systems approach, you would have to add a great 
>>> deal more of material. What I remember about chemistry is that they already 
>>> give you too much material to remember and often assume you are familiar 
>>> with processes and techniques that you have never encountered anywhere. As 
>>> if someone just ripped pages out of your textbook and threw them away. 
>>> Trying to see how you could fit MORE into the curriculum seems somewhat 
>>> unkind.
>>>
>>> Another Mark
>>>
>>> On Wednesday, July 21, 2021 at 10:06:42 AM UTC-7 mark.cu...@gmail.com 
>>> wrote:
>>>
 I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell 
 over the last several weeks. Most of this time has been just getting stuff 
 into TW and seeing what happens (or doesn't and trying to figure out why). 
 I have not spent any time creating, connecting, etc.. The product of my 
 work thus far is here.

 I have two large outlines (GeneralChemistryACCMOutline and 
 OrganicChemistryACCMOutline) that delineate anchoring concept content 
 maps  for most of the 
 undergraduate chemistry I teach. The hierarchy of these outlines is 
 identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
 differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
 Details).

 I need to excise these outlines and then add open educational resources 
 (text, links to videos, images, and simulations, exercises, etc.) to the 
 resulting tiddlers.

 I am interested in your thoughts on how I might excise these outlines 
 in a (unique?) way that leverages TW’s utility/flexibility as a 
 content-management system considering:

1. The order of Level 1 Big Ideas is consistent with the sequence 
of instruction.
2. I would like to somehow leverage TW and the connected, 
context-free facts derived from these outlines to move away from a 
reductionist approach to teaching and learning to a systems approach 
 to teaching and 
learning. 
3. I do not yet know specifically how I am going to use this 
resource in a teaching setting.
4. I am new to TW…

 Thanks for your help.

 Mark

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a5c8c4f9-eef1-401f-9c63-de24c5200a44n%40googlegroups.com.

[tw5] Re: Simplest way to list all tiddlers that transclude the current tiddler?

[Saq Imtiaz]

>
>  If I get some time in the next couple months and nobody else does it, 
> maybe I will take a look at how to get started with TW core development.
>
>
Would be happy to answer any questions you might have along those lines.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b78c98c7-d4af-4bfd-90c0-1e4f7f9b3cc2n%40googlegroups.com.

[tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

You can see your corresponding local time at the following link:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=TiddlyWiki+Community+Call+and+File+Uploads+Plugin=20210817T18=195=1=30

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e26457d8-7edc-4b70-b35b-573706e40e82n%40googlegroups.com.

[tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

Apologies Soren, I should have specified in UTC as well. CET is indeed 
UTC+2.

So the community call is at August 17th at 16:00 UTC

You can see your corresponding local time here .

On Thursday, July 22, 2021 at 10:18:45 PM UTC+2 Soren Bjornstad wrote:

> Saq,
>
> To clarify for those of us who are not as familiar with European time 
> zones, is this UTC+2 because it is summer?
> On Thursday, July 22, 2021 at 2:33:18 PM UTC-5 saq.i...@gmail.com wrote:
>
>> We will be having a *TiddlyWiki Community call* with Jeremy, Boris and 
>> myself on August 17th at 6pm CET: TiddlyWiki Community: Core Savers & 
>> Syncers, Upload Plugin, & Community Forum - Zoom 
>>
>> I hope some of you will be able to join us for what I think will be a 
>> very interesting discussion. Please register for the event at the link 
>> above.
>>
>> The call will include:
>>
>>- a progress update on my work on the *Uploads plugin* funded by Open 
>>Collective
>>- a summary of some rather exciting and promising avenues for core 
>>development in the areas of *Savers and Syncers* that has come out of 
>>discussions around the Uploads plugin
>>- an update on the *Open Collective* model for funding TiddlyWiki 
>>work and what we have learned from it thus far
>>- some news from Jeremy and Boris regarding improvements to 
>>TiddlyWiki *community infrastructure*.
>>
>> I have been slowly working away on the TiddlyWiki file uploads plugin as 
>> was previously announced 
>> . 
>> The majority of the work thus far has consisted of brainstorming around the 
>> architecture and some very involved but promising and productive 
>> discussions with Jeremy around how such a plugin would integrate with the 
>> core, and the direction that the core might take in the future with regards 
>> to saving and syncing mechanisms. 
>>
>> In particular we have identified some exciting opportunities to explore 
>> in due course for a rethinking of the saver and syncer mechanisms that may 
>> amongst other things eventually make file uploads a core TiddlyWiki ability 
>> alongside saving and syncing and static file publishing.
>>
>> This has necessitated a change in approach to the File Uploads plugin so 
>> as to not introduce changes to the TiddlyWiki core at this time which may 
>> clash with the long term direction of development, and still make the 
>> Uploads plugin available in a timely manner for those that need this 
>> functionality today. I currently have a minimal working prototype that 
>> uploads images imported into TiddlyWiki to Fission, though with no UI or 
>> error handling as of yet and desperately in need of some heavy refactoring 
>> to better be able to support different storage back ends. I hope to present 
>> a demo of an early version of the plugin on the call.
>>
>> I would like to take the opportunity here to thank Boris and Fission. 
>> Despite Boris having chipped in for the vast majority of the funding for 
>> this plugin as it is something he needs in his own TiddlyWiki usage, not 
>> only has he been patient and supportive as we focus on long term core 
>> planning first, but Fission has actively been facilitating those 
>> discussions.
>>
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/83df5210-a937-4272-bf60-169f3f20a7d1n%40googlegroups.com.

[tw5] TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

We will be having a *TiddlyWiki Community call* with Jeremy, Boris and 
myself on August 17th at 6pm CET: TiddlyWiki Community: Core Savers & 
Syncers, Upload Plugin, & Community Forum - Zoom 

I hope some of you will be able to join us for what I think will be a very 
interesting discussion. Please register for the event at the link above.

The call will include:

   - a progress update on my work on the *Uploads plugin* funded by Open 
   Collective
   - a summary of some rather exciting and promising avenues for core 
   development in the areas of *Savers and Syncers* that has come out of 
   discussions around the Uploads plugin
   - an update on the *Open Collective* model for funding TiddlyWiki work 
   and what we have learned from it thus far
   - some news from Jeremy and Boris regarding improvements to TiddlyWiki 
*community 
   infrastructure*.

I have been slowly working away on the TiddlyWiki file uploads plugin as 
was previously announced 
. The 
majority of the work thus far has consisted of brainstorming around the 
architecture and some very involved but promising and productive 
discussions with Jeremy around how such a plugin would integrate with the 
core, and the direction that the core might take in the future with regards 
to saving and syncing mechanisms. 

In particular we have identified some exciting opportunities to explore in 
due course for a rethinking of the saver and syncer mechanisms that may 
amongst other things eventually make file uploads a core TiddlyWiki ability 
alongside saving and syncing and static file publishing.

This has necessitated a change in approach to the File Uploads plugin so as 
to not introduce changes to the TiddlyWiki core at this time which may 
clash with the long term direction of development, and still make the 
Uploads plugin available in a timely manner for those that need this 
functionality today. I currently have a minimal working prototype that 
uploads images imported into TiddlyWiki to Fission, though with no UI or 
error handling as of yet and desperately in need of some heavy refactoring 
to better be able to support different storage back ends. I hope to present 
a demo of an early version of the plugin on the call.

I would like to take the opportunity here to thank Boris and Fission. 
Despite Boris having chipped in for the vast majority of the funding for 
this plugin as it is something he needs in his own TiddlyWiki usage, not 
only has he been patient and supportive as we focus on long term core 
planning first, but Fission has actively been facilitating those 
discussions.

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/86426dff-75ea-49b8-9840-f899adbbe485n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

> Is there a search tool or plugin that works with streams? Streams is neat 
> to take notes with, but searching is problematic since the default search 
> shows you only the titles. Possibly someone has already written a custom 
> search? 
>

@Mark S:

I don't think there is a good generalized solution for this yet. Needs vary 
depending on people's workflow and title naming setup within Streams. I 
have posted a search customization for a specific users workflow at one 
point to show what customizations for search might look like.

If you just want search results to show the root tiddler title as opposed 
to the titles of individual nodes, the attached file adds a tab to the 
search results to do that. If I remember correctly, title matches are 
returned unchanged whereas text matches only return the root tiddler.

The missing piece is of course that once you find and open the root 
tiddler, it can be tricky finding the text you searched for within that 
stream.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1ab33144-87d6-4d95-8c77-e05565891025n%40googlegroups.com.


$__streams_addons_ui_SearchResultList.json
Description: application/json

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

> Also need to find an easy way to delete all the node-tiddlers rendered 
> superfluous, once i flatten using your modal ; this is the one function of 
> Jan's addon that i miss... 
>
> Delete the root tiddler the way you would delete any other tiddler. You 
will be prompted to delete it's nodes as well.

 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/77b1e8bc-ca6f-48fc-aed9-2ab1f3f0c97en%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

On Wednesday, July 21, 2021 at 10:38:28 PM UTC+2 Mark S. wrote:

> So, you have to add manual config even though it's set up in the relink 
> plugin config?


Since your rename is happening outside of the Streams UI, yes. If you 
trigger a rename using the built in affordances, it is handled 
automatically if Relink is installed.  $:/config/RelinkOnRename is the 
default configuration tiddler which controls for both the core and relink 
what happens when renaming a tiddler via the edit template. It would be an 
overreach for Streams to change that behaviour that for users who rename 
outside of the Streams UI.
 

> It might be helpful if this was mentioned in the installation tiddler. 
> Most people are going to assume that if they have the relink tiddler that 
> they're good to go.


 Have not had any reports of this being a problem since the very first 
Streams release. Contributions to the documentation are always welcome.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dc3ac1af-c0d1-4b2c-9085-ca8682d427fdn%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

@Mark S

$:/config/RelinkOnRename is in fact not enabled by default on the Streams 
site. I'll ensure that is next time I push an update.

For now create  $:/config/RelinkOnRename with a text field value of yes

On Wednesday, July 21, 2021 at 10:12:02 PM UTC+2 Mark S. wrote:

> Yes. I'm using direct from your site.
>
> On Wednesday, July 21, 2021 at 11:46:06 AM UTC-7 saq.i...@gmail.com wrote:
>
>> @Mark S
>>
>> Is  $:/config/RelinkOnRename set to yes?
>>
>> Streams does add configuration for Relink to act on the stream-list field:
>> [image: Screenshot 2021-07-21 204538.png]
>>
>> On Wednesday, July 21, 2021 at 7:35:24 PM UTC+2 Mark S. wrote:
>>
>>> Trying streams. I notice that when I change the name of a tiddler, it 
>>> drops out of the original list, apparently because *relink* doesn't 
>>> operate on the streams-list field. Is there a tweak to fix that?
>>>
>>> On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com 
>>> wrote:
>>>
>>>> I think I'll go ahead and change my icon in my next release for users 
>>>> who may want to use both. 
>>>> Would I get away with just changing the colour? Any SVG artist out 
>>>> there?
>>>>
>>>>
>>>> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>>>>
>>>>> Hi Walt, thanks for the kind words.
>>>>>
>>>>> The only side effect of running both in parallel would be the 
>>>>> appearance of two identical buttons that don't behave the same way... (I 
>>>>> think)
>>>>> This problem could easily be avoided if I used a different icon, but I 
>>>>> am not super creative and Jan's icon is just perfect .
>>>>>
>>>>> The plugin does not do any house-cleaning; that would be rude, would 
>>>>> it not?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>>>>
>>>>>> Nice job, @Fred; it renders outlines from Streams not only 
>>>>>> faithfully, but beautifully! 
>>>>>>
>>>>>> One question, before i install this in my primary desktop wiki: you 
>>>>>> say in your Credits that it borrows from -and is incompatible with- 
>>>>>> Jan's 
>>>>>> streams-to-text addon <https://szen.io/stream/>... Does this mean i 
>>>>>> should first remove the several bits that make up that addon before 
>>>>>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>>>>>> house-cleaning?
>>>>>>
>>>>>> /walt
>>>>>>
>>>>>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> ok, here's a beta streams-fusion addon: 
>>>>>>> https://fastfreddy.gitlab.io/streams-fusion/
>>>>>>> please note the troubleshooting step is required until the next 
>>>>>>> Streams release; beta users beware
>>>>>>>
>>>>>>> very open to constructive feedback; and/or different ways of 
>>>>>>> shipping such as rolled in the Streams plugin itself if it is good 
>>>>>>> enough.
>>>>>>>
>>>>>>> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>>>>>>>
>>>>>>>> That is definitely an oversight from when I added that at Jan's 
>>>>>>>> request. If you open an issue on Github, it will be resolved for the 
>>>>>>>> next 
>>>>>>>> release.
>>>>>>>>
>>>>>>>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> @saq
>>>>>>>>> quick question: am trying to package my addon, am a bit of a 
>>>>>>>>> newbie unfortunately. 
>>>>>>>>> is it possible we need to modify this line (bold insert)
>>>>>>>>> <$list 
>>>>>>>>> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
>>>>>>>>> variable="btnTiddler">
>>>>>>>>>
>>>>>>>>> in $:/plugins/sq/st

Re: [tw5] I broke the json pre-release :|

[Saq Imtiaz]

I believe this check for field names is the cause:

https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606

On Wednesday, July 21, 2021 at 9:34:54 PM UTC+2 Saq Imtiaz wrote:

> @Jeremy regarding this bug, I think it is related to having a space 
> character in a field name.
>
> At https://tiddlywiki.com/prerelease/empty.html
>
> Create a new tiddler called "test" with a field name "my field" with a 
> value of "hello".
> Save and open the resultant file.
>
> You get a blank white screen, no errors in the console.
>
> On Friday, July 16, 2021 at 6:32:46 PM UTC+2 Saq Imtiaz wrote:
>
>> I don't have the opportunity to debug this at the moment but I believe 
>> this is the commit responsible:
>>
>> https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265
>>
>> Seems like the boot process just doesn't load anything and we get a blank 
>> screen.
>>
>> On Friday, July 16, 2021 at 6:30:19 PM UTC+2 Jeremy Ruston wrote:
>>
>>> Hi Springer 
>>>
>>> Was it a "red screen of embarrassment" crash? It would certainly be 
>>> helpful to pin it down if we can. 
>>>
>>> > I'd also welcome tips on how to get github to actually download files 
>>> from the history (When I try, I just get html within a new browser tab). 
>>>
>>> It's a bit convoluted: first, click on the three dots at the top right 
>>> of the file in the commit listing: 
>>>
>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4a45238f-904b-4e3b-8c42-cae6b10a8e64n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

With regards to exporting a stream as a wikitext list, I have never pursued 
the option involving wrapping things in DIVs because the resultant output 
is quite difficult to read and edit, at which point just outputting HTML 
might be cleaner.

However one option that might be worth investigating is using @pmario's 
"space space newline" plugin as a dependency, and prefixing every 
line-break in a node with two space characters. Problem is that this will 
interfere with multiline constructs like wikitext tables.

https://wikilabs.github.io/editions/space-space-newline/

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/75d57208-8942-4c2e-806f-db4846a16775n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

[Saq Imtiaz]

@Jeremy regarding this bug, I think it is related to having a space 
character in a field name.

At https://tiddlywiki.com/prerelease/empty.html

Create a new tiddler called "test" with a field name "my field" with a 
value of "hello".
Save and open the resultant file.

You get a blank white screen, no errors in the console.

On Friday, July 16, 2021 at 6:32:46 PM UTC+2 Saq Imtiaz wrote:

> I don't have the opportunity to debug this at the moment but I believe 
> this is the commit responsible:
>
> https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265
>
> Seems like the boot process just doesn't load anything and we get a blank 
> screen.
>
> On Friday, July 16, 2021 at 6:30:19 PM UTC+2 Jeremy Ruston wrote:
>
>> Hi Springer
>>
>> Was it a "red screen of embarrassment" crash? It would certainly be 
>> helpful to pin it down if we can.
>>
>> > I'd also welcome tips on how to get github to actually download files 
>> from the history (When I try, I just get html within a new browser tab).
>>
>> It's a bit convoluted: first, click on the three dots at the top right of 
>> the file in the commit listing:
>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2a2f4b2e-0148-40e0-912b-88c2bbd41b2dn%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

Streams 1.2.22 is now live and should allow other plugins to add buttons at 
the end of a stream.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5467a988-6882-40b9-9408-7a942247085fn%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

@Mark S

Is  $:/config/RelinkOnRename set to yes?

Streams does add configuration for Relink to act on the stream-list field:
[image: Screenshot 2021-07-21 204538.png]

On Wednesday, July 21, 2021 at 7:35:24 PM UTC+2 Mark S. wrote:

> Trying streams. I notice that when I change the name of a tiddler, it 
> drops out of the original list, apparently because *relink* doesn't 
> operate on the streams-list field. Is there a tweak to fix that?
>
> On Wednesday, July 21, 2021 at 7:46:03 AM UTC-7 fred@gmail.com wrote:
>
>> I think I'll go ahead and change my icon in my next release for users who 
>> may want to use both. 
>> Would I get away with just changing the colour? Any SVG artist out there?
>>
>>
>> On Wednesday, 21 July 2021 at 09:42:05 UTC-4 Frédéric Demers wrote:
>>
>>> Hi Walt, thanks for the kind words.
>>>
>>> The only side effect of running both in parallel would be the appearance 
>>> of two identical buttons that don't behave the same way... (I think)
>>> This problem could easily be avoided if I used a different icon, but I 
>>> am not super creative and Jan's icon is just perfect .
>>>
>>> The plugin does not do any house-cleaning; that would be rude, would it 
>>> not?
>>>
>>>
>>>
>>> On Wed, 21 Jul 2021 at 09:35, ludwa6  wrote:
>>>
>>>> Nice job, @Fred; it renders outlines from Streams not only faithfully, 
>>>> but beautifully! 
>>>>
>>>> One question, before i install this in my primary desktop wiki: you say 
>>>> in your Credits that it borrows from -and is incompatible with- Jan's 
>>>> streams-to-text addon <https://szen.io/stream/>... Does this mean i 
>>>> should first remove the several bits that make up that addon before 
>>>> installing streams-fusion plugin?  Or does your plugin do its own proper 
>>>> house-cleaning?
>>>>
>>>> /walt
>>>>
>>>> On Wednesday, July 21, 2021 at 12:45:48 PM UTC+1 fred@gmail.com 
>>>> wrote:
>>>>
>>>>> ok, here's a beta streams-fusion addon: 
>>>>> https://fastfreddy.gitlab.io/streams-fusion/
>>>>> please note the troubleshooting step is required until the next 
>>>>> Streams release; beta users beware
>>>>>
>>>>> very open to constructive feedback; and/or different ways of shipping 
>>>>> such as rolled in the Streams plugin itself if it is good enough.
>>>>>
>>>>> On Wed, 21 Jul 2021 at 06:59, Saq Imtiaz  wrote:
>>>>>
>>>>>> That is definitely an oversight from when I added that at Jan's 
>>>>>> request. If you open an issue on Github, it will be resolved for the 
>>>>>> next 
>>>>>> release.
>>>>>>
>>>>>> On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> @saq
>>>>>>> quick question: am trying to package my addon, am a bit of a newbie 
>>>>>>> unfortunately. 
>>>>>>> is it possible we need to modify this line (bold insert)
>>>>>>> <$list 
>>>>>>> filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
>>>>>>> variable="btnTiddler">
>>>>>>>
>>>>>>> in $:/plugins/sq/streams/nodes-list-template ?
>>>>>>> otherwise, it feels like my new button does not take when it is 
>>>>>>> contained within a plugineven with the $:/tags/streams/root-buttons 
>>>>>>> tag 
>>>>>>>
>>>>>>> thanks much...
>>>>>>>
>>>>>>> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  
>>>>>>> wrote:
>>>>>>>
>>>>>>>> a quick update to everyone;
>>>>>>>>
>>>>>>>> I am making steady progress on packaging this merging solution, 
>>>>>>>> hoping to release as a Streams plugin addon. I have repurposed the 
>>>>>>>> button 
>>>>>>>> from https://szen.io/stream/. I now have it also working as a 
>>>>>>>> Streams context menu, with keyboard shortcuts, and it can export 
>>>>>>>> sub-trees 
>>>>>>>> correctly by adjusting the depth levels of the

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

That is definitely an oversight from when I added that at Jan's request. If 
you open an issue on Github, it will be resolved for the next release.

On Wednesday, July 21, 2021 at 3:15:33 AM UTC+2 fred@gmail.com wrote:

> @saq
> quick question: am trying to package my addon, am a bit of a newbie 
> unfortunately. 
> is it possible we need to modify this line (bold insert)
> <$list filter="[*all[shadows+tiddlers]*tag[$:/tags/streams/root-buttons]]" 
> variable="btnTiddler">
>
> in $:/plugins/sq/streams/nodes-list-template ?
> otherwise, it feels like my new button does not take when it is contained 
> within a plugineven with the $:/tags/streams/root-buttons tag 
>
> thanks much...
>
> On Tue, 20 Jul 2021 at 07:58, Frédéric Demers  wrote:
>
>> a quick update to everyone;
>>
>> I am making steady progress on packaging this merging solution, hoping to 
>> release as a Streams plugin addon. I have repurposed the button from 
>> https://szen.io/stream/. I now have it also working as a Streams context 
>> menu, with keyboard shortcuts, and it can export sub-trees correctly by 
>> adjusting the depth levels of the bulleted/numbered lists.
>>
>> A few ideas I am going to try to roll in and release a beta by the end of 
>> this week
>>
>> Cheers
>>
>> On Sat, 17 Jul 2021 at 09:06, Frédéric Demers  wrote:
>>
>>> with capture:
>>>
>>> On Sat, 17 Jul 2021 at 09:05, Frédéric Demers  
>>> wrote:
>>>
>>>> nevermind, I think I solved it at least, significant progress
>>>>
>>>> here's the wikitext for the challenging nodes; renders pretty well:
>>>>
>>>> * 
>>>>
>>>> ''Streams'' uses the following tiddler fields to maintain the structure 
>>>> of a stream:
>>>>
>>>> * each node tiddler has a field `stream-type`
>>>> * each node that has children, contains their titles in a list in the 
>>>> field `stream-list`
>>>> * each node that has a parent, contains the parent's title in the field 
>>>> `parent`
>>>>
>>>> ''You can manipulate these tiddlers just as you would any other 
>>>> tiddlers, with filters and list and action widgets''
>>>>
>>>> 
>>>> * To make it easier to work with Streams tiddlers and their nodes, two 
>>>> filters have been introduced. See [[Streams 0.2 improvements/Filters]]
>>>> * 
>>>>
>>>> This is an example of a button that can export the content of the nodes 
>>>> of a tiddler whose title is in the variable `myTiddler` and save the 
>>>> combined text to a single tiddler:
>>>>
>>>> ```
>>>> <$button> save to a single tiddler
>>>> <$vars lb="
>>>>
>>>> ">
>>>> <$action-setfield $tiddler="report" text={{{ 
>>>> [get-stream-nodes[]] 
>>>>  :reduce[get[text]addprefixaddprefix] }}}/>
>>>> 
>>>> 
>>>> ```
>>>> Note that this disregards the node hierarchy.
>>>> * 
>>>>
>>>> Similarly to export the combined text of the nodes as HTML you can use 
>>>> the `<$wikify>` widget:
>>>>
>>>> ```
>>>> <$button> export as HTML
>>>> <$wikify name="text" text="""<$list 
>>>> filter="[get-stream-nodes[]]">
>>>> <$transclude mode=block/>
>>>> """ output="html">
>>>> <$action-setfield $tiddler="report" text=<>/>
>>>> 
>>>> 
>>>> ```
>>>>
>>>> 
>>>> * 
>>>>
>>>> Here is an example of a macro that can be used to export a stream using 
>>>> a custom HTML structure:
>>>>
>>>> ```
>>>> \define print-row()
>>>> \whitespace trim
>>>> <$(innerTag)$>{{!!text}}
>>>> <$list filter="[has[stream-list]]" variable="_NULL">
>>>> <$(outerTag)$>
>>>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>>>> <>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> \end
>>>>
>>>> \define print-stream()
>>>> \whitespace trim
>>>> <$(outerTag)$>
>>>> <$list filter="[enlist{!!stream-li

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Saq Imtiaz]

Hi Soren, glad that was helpful. When I worked on performance improvements 
for Streams a few months ago, the biggest gains were from simplifying the 
widget and DOM structure, and replacing macros with transclusions, rather 
than from optimizing filters.

I took a brief look at your wiki just now and the one odd thing I see is 
that there seems to be an intermittent refresh being triggered every few 
seconds. Any idea what that is about? To see what I mean, create a new 
tiddler with the following in the text and then observe the developer 
console:
<$log t=<>/>

This should work on the current pre-release but probably isn't any faster:
[tag[$:/sib/refexplorer/tabs]] :filter[subfilter{!!condition}] +[join[ ]]

I suspect that any real gains would come from optimizing the condition 
filters, as they likely make up the bulk of the time needed for the above 
filter expression. For filter operators that are indexed, the first time 
they run they will take a while but subsequent runs should be faster. 
https://tiddlywiki.com/#Performance

On Wednesday, July 21, 2021 at 4:20:13 AM UTC+2 Soren Bjornstad wrote:

> Thanks Saq, that view is super useful and I never knew it existed!
>
> Armed with that information, I spent most of this evening tinkering on 
> improving some of the other things that have been slowing my wiki down, 
> including adding an Idea tag so I don't have to define it as the negation 
> of a dozen other tags and replacing TiddlyTables with a similar HTML table 
> that needs fewer filters, macros, and transclusions in the most critical 
> paths. (More work needs to be done to bring the rest of the Reference 
> Explorer in line and refactor it to catch it up with a bunch of other 
> changes I've made recently.)
>
> The tabs filter discussed above was and remains the #1 contributor to 
> filter processing time when clicking around the wiki, often something like 
> 30% of the total time, so I'm still interested in suggestions others may 
> have for improving that. I didn't want to publish the wiki in its present 
> state previously since it was so slow it would be difficult for people to 
> use, but I've ameliorated that enough that I am now comfortable 
> republishing it. As mentioned in my previous post, you can start looking at 
> $:/sib/refexplorer/ReferenceExplorer, but now it is a working example 
> rather than something you would have to tweak into a working example by 
> yourself.
>
> On Tuesday, July 20, 2021 at 9:29:49 AM UTC-5 saq.i...@gmail.com wrote:
>
>> @Soren I recommend enabling performance instrumentation and checking to 
>> see which filter runs are the culprits.
>>
>>
>> https://tiddlywiki.com/#%24%3A%2Fconfig%2FPerformance%2FInstrumentation:%24%3A%2Fconfig%2FPerformance%2FInstrumentation%20%5B%5BPerformance%20Instrumentation%5D%5D
>>
>> Note that you need to enable it by setting the config tiddler to "yes", 
>> then save and reload.
>>
>> Also suggest posting a public wiki where the issue (and the condition 
>> filters) can be seen to facilitate debugging.
>> On Tuesday, July 20, 2021 at 4:05:15 PM UTC+2 Soren Bjornstad wrote:
>>
>>> Important note, the condition fields aren't defined in the current 
>>> public version, so you'd have to add them in to get a working test.
>>>
>>> On Tuesday, July 20, 2021 at 9:03:42 AM UTC-5 Soren Bjornstad wrote:
>>>
 Tones,

 :filter was my first thought, but I couldn't figure out how the data 
 would flow through it. Perhaps I was missing something, looking forward to 
 seeing your version.

 If it helps to see the context, have a peek at 
 https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer.
  
 The snippet above (or a replacement) would go inside the ref-explorer 
 macro 
 definition.


 On Tuesday, July 20, 2021 at 8:07:09 AM UTC-5 TW Tones wrote:

> Soren,
>
> Its late here but I have done something similar in the past without a 
> performance hit, and will try and create a solution tomorrow, However I 
> think the answer best answer may be through the use of a filter run as in 
> 5.3.23+ however I am sure I succeeded in something similar a few versions 
> ago.
>
> No need for reduce and accumulators I think.
>
> Regards
> Tones
>
> On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:
>
>> Hi all,
>>
>> I want to determine what tabs of the Reference Explorer in my 
>> Zettelkasten to show on a template, such that if there aren't any 
>> results 
>> on that tab, the tab doesn't appear at all. The results of the tab are 
>> produced based on a filter (of course), so I figured I would also 
>> determine 
>> whether the tab appears by running a filter. The filter is stored in a 
>> field in the tab tiddler.
>>
>> That is, I have a series of tiddlers with a certain tag (say *Tab*), 
>> and each of these tiddlers contains 

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Saq Imtiaz]

@Soren I recommend enabling performance instrumentation and checking to see 
which filter runs are the culprits.

https://tiddlywiki.com/#%24%3A%2Fconfig%2FPerformance%2FInstrumentation:%24%3A%2Fconfig%2FPerformance%2FInstrumentation%20%5B%5BPerformance%20Instrumentation%5D%5D

Note that you need to enable it by setting the config tiddler to "yes", 
then save and reload.

Also suggest posting a public wiki where the issue (and the condition 
filters) can be seen to facilitate debugging.
On Tuesday, July 20, 2021 at 4:05:15 PM UTC+2 Soren Bjornstad wrote:

> Important note, the condition fields aren't defined in the current public 
> version, so you'd have to add them in to get a working test.
>
> On Tuesday, July 20, 2021 at 9:03:42 AM UTC-5 Soren Bjornstad wrote:
>
>> Tones,
>>
>> :filter was my first thought, but I couldn't figure out how the data 
>> would flow through it. Perhaps I was missing something, looking forward to 
>> seeing your version.
>>
>> If it helps to see the context, have a peek at 
>> https://zettelkasten.sorenbjornstad.com/#%24%3A%2Fsib%2Frefexplorer%2FReferenceExplorer.
>>  
>> The snippet above (or a replacement) would go inside the ref-explorer macro 
>> definition.
>>
>>
>> On Tuesday, July 20, 2021 at 8:07:09 AM UTC-5 TW Tones wrote:
>>
>>> Soren,
>>>
>>> Its late here but I have done something similar in the past without a 
>>> performance hit, and will try and create a solution tomorrow, However I 
>>> think the answer best answer may be through the use of a filter run as in 
>>> 5.3.23+ however I am sure I succeeded in something similar a few versions 
>>> ago.
>>>
>>> No need for reduce and accumulators I think.
>>>
>>> Regards
>>> Tones
>>>
>>> On Tuesday, 20 July 2021 at 13:09:18 UTC+10 Soren Bjornstad wrote:
>>>
 Hi all,

 I want to determine what tabs of the Reference Explorer in my 
 Zettelkasten to show on a template, such that if there aren't any results 
 on that tab, the tab doesn't appear at all. The results of the tab are 
 produced based on a filter (of course), so I figured I would also 
 determine 
 whether the tab appears by running a filter. The filter is stored in a 
 field in the tab tiddler.

 That is, I have a series of tiddlers with a certain tag (say *Tab*), 
 and each of these tiddlers contains a filter in some field (say 
 *condition*). For each Tiddler tagged Tab, if and only if the filter 
 Tiddler!!condition, run with the current tiddler as input, has more than 
 zero results, I want to display the tab.

 I came up with the following:

 <$set name="tabList" value={{{ [tag[Tab]] 
 :reduce[subfilter{!!condition}thenaddprefix[ 
 ]addprefix] }}}>
 <$macrocall $name="tabs" tabsList=<>/>
 

 This produces the correct result (well, as long as there are no spaces 
 in the titles of the tiddlers tagged *Tab*; I'm OK assuming that since 
 there indeed aren't any). The problem is that it is horrendously slow to 
 run all these filters. On my dev machine it is tolerable, but this is a 
 machine specced for serious processing power. On my MacBook Air it now 
 takes 1–2 seconds to open a new tiddler, even without anything currently 
 open!

 Probably I am just asking TW to do too much on the fly here, but before 
 I start rethinking the project too hard, can anyone think of obvious 
 optimizations I might be missing here? The filters involved are moderately 
 complex (the basic pattern for each is to gather together links[], 
 backlinks[], and tagging[] for the story tiddler, then filter some things 
 out of that using + and !*operator*[]'s).

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/591dd4e2-d6e5-4b77-8be6-5e95588e3e95n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

@fred
 

> I noticed my solution does not work so well for complex node content, as 
> those in:  
> https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers 
>
> The reason is that wrapping in  tags mangles them badly; I tried a 
> few alternatives (, more white space, ..), no success yet. Any 
> suggestions?
>

This is actually the real challenge and why there currently isn't a default 
export option from Streams. Depending on the nature of the content, it 
seems difficult to generalize a single export format that will work and one 
of the common pitfalls is to think of Streams nodes as a list,* which they 
are not.* 

A stream node is a tiddler which can contain any kind of content, and not 
all kinds of content can be mapped to a list item. It might be easier to 
set limitations in one's usage as to what to put inside of a node and have 
an export format that works accordingly, rather than trying to come up with 
a universal export format that works for all content. Hence my suggestion 
of gathering real world user data to drive the process.

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a0431024-302d-4433-95f0-021234984ab0n%40googlegroups.com.

[tw5] Re: NoteTaking in Streams

[Saq Imtiaz]

@keelan I think for the most part the description of your workflow that we 
have at the moment should be sufficient to aid others in their 
understanding of how they might be able to use Streams. What might be 
useful to add is information about any settings for Streams or other 
plugins in your wiki that together form an essential component of your 
workflow. Is your wiki publicly available online? I assume not. However if 
you would feel comfortable sharing a screenshot or two that might be 
helpful as well.

I will follow up with you separately with regards to my personal interest 
in your workflow.

With regards to flattening/export, yes please do share examples of actual 
content. I prefer development and design to be driven by user feedback and 
real data. The more data we have the higher the chance that we can 
generalize a solution or a set of solutions that are useful to most people. 
The easiest thing might be if you export the tiddlers you want to share to 
a new wiki and attach or link that here.

For the time being Google groups will have to do. However my frustrations 
with Google group and particularly losing my posts are reaching a 
crescendo, so I may soon have to consider alternative avenues for 
discussions around Streams.

I am entering a rather busy period with work expected to last about 4 weeks 
during which time I wont be able to actively work on Streams development. 
However, this is a good opportunity for discussions ahead of further 
development.

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3997cf5d-97ae-4334-aac8-15e234333202n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

@fred nicely done. Quite pleasing to see what the new filter operators have 
been useful in this as well. Would you mind if I add this as another export 
example to the Streams docs?

On Saturday, July 17, 2021 at 5:59:52 AM UTC+2 fred@gmail.com wrote:

> Here's a version that wraps in  only the nodes that have line breaks 
> in them; there's certainly a cleaner way to do this, but here it is as 
> inspiration/proof-of-concept.
>
> wikitext output below code; the screen capture sent previously is 
> unchanged.
>
> \define print-row()
> \whitespace trim
>  <$vars lb="
>
> ">
> <$set name="depth" 
> filter="[get-stream-root:includeall[]count[]]">
> <$set name="prefix" filter="[[*]pad,[*]removesuffix[*]]" select="0">
> <$set name="prewrap" 
> filter="[regexp:text[\n]then[]]" select="0">
> <$set name="postwrap" 
> filter="[regexp:text[\n]then[]]" select="0">
>   <$list 
> filter="[get[text]addprefixaddprefixaddsuffixaddsuffix]"
>  
> select="0" variable="nodetext">
>
> <$text text=<> />
> <$list filter="[has[stream-list]]" variable="_NULL">
> <$list filter="[enlist{!!stream-list}is[tiddler]]">
> <>
> 
> 
>   
> 
> 
> 
> 
> 
>
> \end
>
> \define print-stream()
> \whitespace trim
> <$list filter="[enlist{!!stream-list}is[tiddler]]">
> <>
> 
> \end
>
> <$button> export
> <$wikify name="flat" text=<> >
> <$action-setfield $tiddler="report" text=<>/>
> 
> 
>
>
> -
>
> *''Version 1.0''
> **Add affordance to collapse/expand all nodes of a  stream
> **''CSS''
> ***Update css to respect color palette
> **''Settings''
> ***''Configuration settings for context menu items''
> Include other menu items like demote/promote that are disabled by 
> default
> Config screen for enabling/disabling context menu items
> Allow specifying that a contextmenu item should be displayed on narrow 
> screens (mobile) only?
> ***Config tiddler for node content template
> *Have an option to detach a bullet from a list.
> *''Version 1.1''
> **//Provide a better UI to rename bullets while editing//
>
> **UI ideas re: modals
>
> https://getbootstrap.com/docs/3.4/javascript/#popovers
>
>
> http://www.uxforthemasses.com/wp-content/uploads/2015/08/LinkedIn-edit-example.jpg
> 
> *''Other Ideas''
> **drag and drop considerations
> ***copy/transclude via modifier keys to another tiddler doesnt include 
> nested children
> **option to flatten a bullet list to one tiddler, for publishing/export
> **context menu that applies to entire stream
> **Consider different styling for default bullet
> *''Version 2.0''
> **''templating for list row items and row controls''
> ***Allow for different kinds of stream tiddlers (todo, comments, etc)
> **Use draft mechanism for editing
> ***navigator.js L266
>
>
>
> On Fri, 16 Jul 2021 at 23:20, Frédéric Demers  wrote:
>
>> Greetings all,
>>
>> Using bits and pieces I cobbled together (like a plumber), I found a way 
>> to flatten a stream of nodes into another tiddler and preserve the 
>> hierarchy of the nodes.
>>
>> The key was to 1) use the recursive macro provide by Saq, 2) use the 
>> get-stream-root[]count[] filter to determine depth of the node, and 3) 
>> use the pad[]operator to turn said depth in the correct number of * 
>> characters. 
>> I had to work a bit to extract the wikitext correctly. I wrapped each 
>> node in a  tag pair to allow multi-line nodes... though a smarter 
>> filter set could do that only if line feeds are present in the node text.
>>
>> rendered preview enclosed, wikitext output below the sample code.
>>
>> \define print-row()
>> \whitespace trim
>> <$set name="depth" 
>> filter="[get-stream-root:includeall[]count[]]">
>> <$set name="prefix" filter="[[*]pad,[*]removesuffix[*]]" 
>> select="0">
>> <$vars lb="
>> ">
>>  <$list 
>> filter="[get[text]addprefix[]addprefixaddsuffix]"
>>  
>> select="0" variable="nodetext">
>> <$text text=<> />
>> <$list filter="[has[stream-list]]" variable="_NULL">
>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>> <>
>> 
>> 
>>
>> 
>> 
>> 
>> 
>> \end
>>
>> \define print-stream()
>> \whitespace trim
>> <$list filter="[enlist{!!stream-list}is[tiddler]]">
>> <>
>> 
>> \end
>>
>> <$button> export
>> <$wikify name="flat" text=<> >
>> <$action-setfield $tiddler="report" text=<>/>
>> 
>> 
>>
>>
>> --
>>
>> *''Version 1.0''
>> **Add affordance to collapse/expand all nodes of a  stream
>> **''CSS''
>> ***Update css to respect color palette
>> **''Settings''
>> ***''Configuration settings for context menu items''
>> Include other menu items like demote/promote that are disabled 
>> by default
>> Config screen for enabling/disabling context menu items
>> Allow specifying that a contextmenu item should be displayed on 
>> narrow screens (mobile) only?
>> ***Config tiddler for node content template
>> *Have an option to detach a bullet from a list.
>> *''Version 1.1''
>> **//Provide a better UI to 

[tw5] Re: Plugin packaging question

[Saq Imtiaz]

I am on my phone so this is mostly speculation:

Your plugin seems to be depend on Relink, but your wiki doesn't have it 
installed.
On Friday, July 16, 2021 at 9:47:44 PM UTC+2 David Gifford wrote:

> Maybe I spoke too soon, Saq. There is no list of any kind in my plugin. 
> The subsumes are just macros. And the macros don't display. The macro 
> definition is now in a shadow tiddler.
>
> On Friday, July 16, 2021 at 2:39:17 PM UTC-5 David Gifford wrote:
>
>> D'oh! Thanks *again* (sigh), Saq! Gotta write that one down as a note to 
>> myself in documenting.tw...
>>
>> On Friday, July 16, 2021 at 2:35:41 PM UTC-5 Saq Imtiaz wrote:
>>
>>> Same issue probably: 
>>> https://groups.google.com/g/tiddlywiki/c/7EHujx-J1U4/m/7ouJ73ktBAAJ
>>>
>>> On Friday, July 16, 2021 at 9:01:39 PM UTC+2 David Gifford wrote:
>>>
>>>> If you need to see the problem, the link is 
>>>> https://giffmex.org/gifts/subsume.html.
>>>>
>>>> On Friday, July 16, 2021 at 1:53:27 PM UTC-5 David Gifford wrote:
>>>>
>>>>>
>>>>> I just packaged the Subsume plugin (slider-and-link combo pointing to 
>>>>> tiddler B from tiddler A in one macro). But my system tiddlers are now 
>>>>> shadow tiddlers, thanks to the Tinka packaging process, so the subsume 
>>>>> macros don't show anything in view mode.
>>>>>
>>>>> I could click each shadow tiddler of the plugin so it would become a 
>>>>> system tiddler. But I don't want users to have to do that.
>>>>>
>>>>> Is there a way around this?
>>>>>
>>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/43ae2757-226c-41c3-ac26-130c00850467n%40googlegroups.com.

[tw5] Re: Plugin packaging question

[Saq Imtiaz]

Same issue 
probably: https://groups.google.com/g/tiddlywiki/c/7EHujx-J1U4/m/7ouJ73ktBAAJ

On Friday, July 16, 2021 at 9:01:39 PM UTC+2 David Gifford wrote:

> If you need to see the problem, the link is 
> https://giffmex.org/gifts/subsume.html.
>
> On Friday, July 16, 2021 at 1:53:27 PM UTC-5 David Gifford wrote:
>
>>
>> I just packaged the Subsume plugin (slider-and-link combo pointing to 
>> tiddler B from tiddler A in one macro). But my system tiddlers are now 
>> shadow tiddlers, thanks to the Tinka packaging process, so the subsume 
>> macros don't show anything in view mode.
>>
>> I could click each shadow tiddler of the plugin so it would become a 
>> system tiddler. But I don't want users to have to do that.
>>
>> Is there a way around this?
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1cf214f3-1e08-4027-8b19-bc5873ed7fe9n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

[Saq Imtiaz]

I don't have the opportunity to debug this at the moment but I believe this 
is the commit responsible:
https://github.com/springerspandrel/tw/commit/49a0b1ef1ef37d79e514c0a9cf7685e8f4baa75f#diff-81fd67dbd185daf4f0208c57ff40d029e2c72509417aec3bcb2f651900573431R265

Seems like the boot process just doesn't load anything and we get a blank 
screen.

On Friday, July 16, 2021 at 6:30:19 PM UTC+2 Jeremy Ruston wrote:

> Hi Springer
>
> Was it a "red screen of embarrassment" crash? It would certainly be 
> helpful to pin it down if we can.
>
> > I'd also welcome tips on how to get github to actually download files 
> from the history (When I try, I just get html within a new browser tab).
>
> It's a bit convoluted: first, click on the three dots at the top right of 
> the file in the commit listing:
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fd742834-8b90-4ead-ab54-6cd5d8b824a8n%40googlegroups.com.

[tw5] Re: NoteTaking in Streams

[Saq Imtiaz]

My previous two rather lengthy replies to this thread seem not have been 
published. I am hoping I've accidentally hit "reply to author". If not, 
I'll find the time to try again over the weekend.

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/31f726de-ce8b-43c6-ad94-84994bef6103n%40googlegroups.com.

[tw5] Re: Announcing Editor-Autolist-Markdown

[Saq Imtiaz]

Hi Jason,

That looks fantastic. The original autolist was a plugin hacked up in about 
an hour in response to a reddit request. It was never really meant for 
wider adoption. I worked on support for multiple lines later in response to 
a request here on the group but I don't think I ever published that.

I think a good next step if you are up to it, would be to make it 
configurable to detect whether it is a markdown tiddler or wikitext 
tiddler, and be able to support both. That I thing would add a lot of value 
to the community but I do understand that it may not be a priority for you 
if your primary use case is markdown tiddlers.
Cheers,

Saq

On Thursday, July 15, 2021 at 7:13:15 PM UTC+2 jason...@gmail.com wrote:

> Hi all, I have been learning about TW5 and making increasing use of it 
> over the past ~9 months. It is an incredible tool with a great ecosystem of 
> support, so as I begin to make some customizations I wanted to share these 
> back for the community.
>
> I have put together a plugin based on Saq's excellent editor-autolist. I 
> primarily use markdown for my notes so I have adapted it for markdown lists.
>
> I have used bullet lists pretty extensively in the MS ecosystem in my 
> work, so in addition to the list indent and continuation, I added features 
> to indent/unindent multiple lines, and to move list sections up or down.
>
> Please check out the GH repo 
>  and the hosted 
> plugin . This is 
> the initial release so I welcome your feedback and suggestions for 
> improvement!
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b654190b-d908-4916-b8fb-53fc6fb628can%40googlegroups.com.

[tw5] Re: How to install plugins on TW node?

[Saq Imtiaz]

You can drag and drop and install it in each of your wikis.

Or you can save the plugin to a "source 
folder": https://links.tiddlywiki.com/urls/4b5e9c4afc6923035ef9/

On Tuesday, July 13, 2021 at 5:37:55 PM UTC+2 davou...@gmail.com wrote:

>
> I'm running TW 5.1.23 on node js and I want to install JD's Plain 
> Revisions (http://j.d.revisions.tiddlyspot.com/). I've installed plugins 
> that provide complete source like 
> kookma's commander. Unfortunately JD only provides the drag and drop 
> version. How do I properly install it on node for all my TW instances?
>
> Thanks.
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8de4e6c1-edda-475c-b25d-fbb5d72f3c74n%40googlegroups.com.

[tw5] Re: Teaser of my macros

[Saq Imtiaz]

Ouch that is annoying.

One workaround would be:


<>
<>
<>


On Tuesday, July 13, 2021 at 3:52:28 PM UTC+2 David Gifford wrote:

> Thanks Saq. 
>
> Doing it as <> turns it into a , which forces line breaks above 
> and below. Doing it as a macrocall lets me have each one on the next line.
>
> On Tuesday, July 13, 2021 at 8:46:48 AM UTC-5 Saq Imtiaz wrote:
>
>> Looks spiffy. All this time talking about wanting an outliner in TW and 
>> you could have written it all along.
>>
>> Why
>>
>> <$macrocall $name=det tid="The relationship between the Old and New 
>> Testaments"/>
>>
>> instead of:
>> <>
>>
>> Is it for the autocomplete support? If so, we might be able to do 
>> something about that.
>> Cheers,
>>
>> Saq
>>
>> On Tuesday, July 13, 2021 at 6:08:39 AM UTC+2 David Gifford wrote:
>>
>>> Hi everyone
>>>
>>> I have been asking for help a few times, and you all were very helpful. 
>>> Here is the end result, shared as a silent video with notes in the 
>>> description.
>>>
>>> https://www.youtube.com/watch?v=Uk7MSQjaiuo
>>>
>>> In a nutshell, it is a macro I called 'det' that creates a details 
>>> element slider + link (asterisk) based on the tiddler title. These can be 
>>> nested kind of like Dynalist, so when you open one detail slider, if there 
>>> are more under that, you can open those sliders as well like a giant 
>>> outline. And the links are there to open at any level. I tweaked the 
>>> edit-comptext plugin with Saq's help, and so there is a way to autocomplete 
>>> to create a det macrocall around an existing tiddler title.
>>>
>>> I also uploaded an example file so you can test it out and offer 
>>> feedback: https://giffmex.org/experiments/det.teaser.html
>>>
>>> Maybe at some later point when I have used it for a while I will make it 
>>> available as a plugin. But for now it is just for inspiration for you and 
>>> feedback for me.
>>>
>>> Thank you for all of your help! I hope you enjoy it. Blessings, Dave
>>>
>>>
>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/05390cba-7170-4186-be94-92876022e5f4n%40googlegroups.com.

[tw5] Re: Teaser of my macros

[Saq Imtiaz]

Looks spiffy. All this time talking about wanting an outliner in TW and you 
could have written it all along.

Why

<$macrocall $name=det tid="The relationship between the Old and New 
Testaments"/>

instead of:
<>

Is it for the autocomplete support? If so, we might be able to do something 
about that.
Cheers,

Saq

On Tuesday, July 13, 2021 at 6:08:39 AM UTC+2 David Gifford wrote:

> Hi everyone
>
> I have been asking for help a few times, and you all were very helpful. 
> Here is the end result, shared as a silent video with notes in the 
> description.
>
> https://www.youtube.com/watch?v=Uk7MSQjaiuo
>
> In a nutshell, it is a macro I called 'det' that creates a details element 
> slider + link (asterisk) based on the tiddler title. These can be nested 
> kind of like Dynalist, so when you open one detail slider, if there are 
> more under that, you can open those sliders as well like a giant outline. 
> And the links are there to open at any level. I tweaked the edit-comptext 
> plugin with Saq's help, and so there is a way to autocomplete to create a 
> det macrocall around an existing tiddler title.
>
> I also uploaded an example file so you can test it out and offer feedback: 
> https://giffmex.org/experiments/det.teaser.html
>
> Maybe at some later point when I have used it for a while I will make it 
> available as a plugin. But for now it is just for inspiration for you and 
> feedback for me.
>
> Thank you for all of your help! I hope you enjoy it. Blessings, Dave
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/01be6421-8700-47d3-8e7b-31dca8051e4an%40googlegroups.com.

[tw5] Re: NoteTaking in Streams

[Saq Imtiaz]

Hi Walt,

It seems like we are getting our wires crossed and I think I am partly to 
blame for which I apologize. I am very accustomed to speaking to a 
technical audience, OR a completely non-technical one. However here the 
borders are muddled and it has led to me using terms more colloquially than 
technically accurately, which it seems has caused confusion.

What you have created is very impressive and interesting in its own right, 
but not what I was thinking of. So let me take a crack at explaining it 
once more using every day language. 

There are two separate topics here:

*1) Understanding how other people use Streams and allowing Streams users 
to learn from each other.*
We have in this thread descriptions of how several different users make use 
of Streams for their intended purposes. For example this 
 is 
how Keelan uses Streams. It would be good if we collected and added these 
descriptions of how people are already using Streams to the Streams 
documentation. Assistance with this would be fantastic. 

Later on details could be added to this where relevant, like exactly which 
plugin and wiki settings were used and which other plugins. Some users may 
even be comfortable sharing empty copies of their wiki for others to learn 
from.

The key here is that we are talking about descriptions of how people are 
already using Streams. Not how they might hypothetically use it.

*2) The issue of creating better options around export.*
What would be helpful here is if users that have such a need, shared 
examples of their content. So let's say you used Streams to take notes on 
fertilization methods in a tiddler called "Fertilization". I want to see 
that tiddler and its streams nodes. Additionally, I want to see how you 
would consolidate those nodes into a single tiddler if you had to do it by 
hand.

If you are not comfortable sharing actual tiddlers from your wiki due to 
privacy concerns, then you could create a dummy version that has similar 
content in length etc to your actual tiddlers but does not contain anything 
private. The kind of things I need to understand are: how long are the 
nodes typically? Is it just plain text? Are their widgets? Are their 
images? Tables? etc..

Now if all of your content is similar to the nodes on the Fertilization 
tiddler, then that is enough. However if you are using Streams for creating 
different styles of content, such as say a To Do list, meeting notes and 
writing essays, then such an example for each would be needed.

Let us assume 6 users do this. That will hopefully give me enough examples 
of the content people are writing with Streams to have a better chance at 
coming up with a generalized solution that works for most people.

If any of this still isn't clear, I would suggest we find a time for a call 
to discuss before you put any more effort into it, so as to avoid any 
chance of further misunderstanding.

For the record what you did create is fantastic and if this were a properly 
funded development effort we would indeed be using User Stories 
representing hypothetical users and how they might want to use Streams as a 
starting point to understand what was needed. However, this is  one of many 
side projects for someone that has their fingers in far too many pies, so 
that approach isn't feasible.

Regards,
Saq
On Sunday, July 11, 2021 at 8:14:48 PM UTC+2 ludwa6 wrote:

> OK @Saq: I've taken a little run at creating a wiki to hold UseCase 
> documentation for "TiddlyStreams" ; it's online at tiddlystreams.github.io , 
> and if that looks to you like a move in the right direction, then i'll keep 
> on going with it as time permits.  If you or anyone wants to assist, i can 
> add as users to the "tiddlystreams" organization, or i guess anyone can 
> send a PR (it's a public repo)... or else just click the Comment Link (i.e. 
> mailto:) at bottom of each tiddler.
>
> Funny thing: your feedback has caused me to question my understanding of 
> the term UseCase, so i did a bit of digging; sounds to me like what you 
> want (if this article 
> 
>  can 
> be considered definitive) is more like a UserStory set, while i- the naive 
> (i.e. non-dev) user in this conversation- have been trying to communicate 
> more in terms of a technical solution.  Awkward!  (like when i'm insisting 
> on speaking Portuguese to a local who really wants to speak English with me 
> :-)
>
> /walt
>
>
> On Sunday, July 11, 2021 at 12:13:14 PM UTC+1 saq.i...@gmail.com wrote:
>
>> @walt
>>
>> As to the node-flattening issue i would like to see "wikitext" join 
>>> the other 3 options (bullet list, numbered list and paragraphs)
>>>
>>
>> So when I wrote "an actual real world example of what their content in 
>> Streams is like, and what an ideal exported version in a single tiddler in 
>> TiddlyWiki would look 

[tw5] Re: Adding " in a config that is wrapped in " "

[Saq Imtiaz]

Try this:

"pattern": "///",
  "filter": "[all[tiddlers]!is[system]]",
  "start": "<$macrocall $name=det tid=\"",
  "end": "\" />"

On Sunday, July 11, 2021 at 1:50:17 PM UTC+2 David Gifford wrote:

> Hi everyone
>
> My edit to the edit-comptext plugin config tiddler (
> http://snowgoon88.github.io/TW5-extendedit/#%24%3A%2Fplugins%2Fsnowgoon88%2Fedit-comptext%2Fconfig
> )
>
> Has this:
>
> "pattern": "///",
>   "filter": "[all[tiddlers]!is[system]]",
>   "start": "<$macrocall $name=det tid=",
>   "end": " />"
>
> I would like to have a " after tid= and another " before /> so that when I 
> hit enter, the tiddler that is autocompleted will be wrapped with the full 
> macrocall. Single quotes aren't an option, because tiddler titles could 
> contain single quotes.
>
> What is the secret hack you guys use to sneak those in? Based on the 
> editor toolbar wrap buttons I tried turning " from the code into """, but I 
> destroyed my file. Don't worry, it was a copy, so I didn't lose anything.
>
> Thanks for any help you can give!
>
> Dave
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0ab2eaad-4a1b-4dc7-ab33-31bb17ff9bden%40googlegroups.com.

[tw5] Re: NoteTaking in Streams

[Saq Imtiaz]

@walt

As to the node-flattening issue i would like to see "wikitext" join the 
> other 3 options (bullet list, numbered list and paragraphs)
>

So when I wrote "an actual real world example of what their content in 
Streams is like, and what an ideal exported version in a single tiddler in 
TiddlyWiki would look like" my expectation was for users to provide wikis 
with a representative example of their content in streams nodes, as well as 
a single tiddler version of it that they created by hand. For example one 
tiddler with some stream nodes, the content of which is representative of 
what their content is usually like. Plus one tiddler that is an 
amalgamation of those nodes into a single tiddler.

Having a few such examples might allow generalizing a few export options 
that fit most use cases. The problem with receiving proposals for 
solutions, rather than detailed description of the problem and related 
content, is that often the proposed solutions don't fulfil the actual needs 
or consider technical limitations they would impose. For example, your 
proposed solution would limit you to only ever having single line content 
in all your nodes.
 
Regarding use cases/workflows, I was referring to the manner in which 
people are using Streams for note taking (the original subject of this 
thread). We have a few examples now from Keelan, Si and others. It would be 
good to gather the descriptions of their workflows and add it to the 
documentation. This could later be fleshed out with details on other 
plugins, or wiki settings etc that they use to achieve their desired 
workflow. Since there is not a single prescribed workflow for using 
Streams, nor a vertical TiddlyWiki edition designed to accommodate it, 
having examples of how people use Streams would allow knowledge sharing 
amongst Streams user and be useful to the next person who has the same 
question as you regarding how to use Streams for note taking.

Help with collecting this to add it to the documentation would be greatly 
appreciated. The easiest thing to do would be to collect the information in 
a TiddlyWiki file. 

The other issue you've raised of particular interest to me is the mobile 
> UseCase <#m_3548407170148151557_UseCase> - which may be more properly 
> considered a UserModel <#m_3548407170148151557_UserModel>  that could 
> serve as extension to various UseCases <#m_3548407170148151557_UseCases>. 
> This in my case involves using Quine2 on iOS devices: iPhone and iPad -2 
> different form factors, which lend themselves to somewhat different modes 
> of interaction. What's needed here is the ability to manipulate position in 
> the hierarchy via swipe L/R, drag Up/Down. Is this what you're talking 
> about in that Reddit thread you shared 
> ?
>   
> Or is there some other mode of mobile interaction to consider?
>

Mobile usage is a tricky issue for TiddlyWiki. The design and UX really 
isn't optimized for it. In particular, the drag and drop mechanism doesn't 
work for all mobile browsers. This is a limitation of the browsers not 
implementing the relevant spec at all or properly. As such, implementing 
proper support for this is outside the scope of a single plugin.

As I've expressed during earlier conversations on the same topic, I do not 
intend to work on any mobile specific features or affordances for Streams 
beyond any low hanging fruit that can be achieved with minimal effort. 
Currently in Streams you can swipe on a node on mobile to trigger the 
context menu. Add your own commands to the context menu is the way to go 
for any features you absolutely need on mobile.

The interest in the swipe with visual feedback feature actually comes from 
a technical perspective. It is *very* impressive that such a thing can be 
achieved with just wikitext, so I would like to see it realized (time 
permitting) to serve as an example for others wanting to explore similar UX.

Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9d9f575e-b880-4e3b-a0ec-da7f092b1932n%40googlegroups.com.

[tw5] Re: NoteTaking in Streams

[Saq Imtiaz]

Hi everyone. I've been away on an impromptu leave the last week, apologies 
for the late reply. 

I am very grateful to everyone that provided feedback or even just taken 
the time to acknowledge that they use Streams. Thank you Keelan, Zhang, 
Stan, Steph and everyone else.

*@keelan* It is very good to hear that you are still finding Streams to be 
of value. I thought of you a few weeks ago actually as yours was a workflow 
and use case that really stood out to me, and I wasn't sure if you had 
stuck with or turned to other tools. It is interesting how this works in 
terms of feedback and involvement. From a user's perspective, if you find a 
good tool you just want to use it and be productive rather than focus 
overmuch on talking about the tool. However, for a very small software 
project like this, occasional user feedback or even just holding your hand 
up to acknowledge that you are still using it goes a very long way. So 
thank you for taking the time to chime in here.

*On flattening and export:*
In terms of export formats, the issue is that everyone's content and use 
case is different which makes it difficult to come up with universal 
solutions. One of the approaches here that could be interesting is if 
everyone gave an actual real world example of what their content in Streams 
is like, and what an ideal exported version in a single tiddler in 
TiddlyWiki would look like. It might mean crafting that single consolidated 
tiddler by hand to serve as an example. This might help generalize and come 
up with a flexible solution.

Note also that for some users, such as @si, it is a valid use case to not 
want to consolidate all your nodes but keep them as separate tiddlers.

I think the focus on markdown in this discussion is misplaced as it isn't 
the primary barrier to exports from Streams. It really is two steps. a) 
consolidating your individual nodes into a single tiddler as wikitext, and 
b) then converting it to another format (HTML, markdown, etc.) Figuring out 
the first step is necessary before looking at what comes after.

*Use cases:*
We now have descriptions of a few different workflows with Streams. One of 
the things that would be very helpful if we gathered this information and 
added it to the documentation. This could be the first step towards 
facilitating sharing of tweaks and settings etc that are being used in 
those workflows. Any assistance with this would be very welcome.

*Questionnaire, plugin updates and what comes next:*
I will likely post a questionnaire in the next week or two. A rather 
preliminary one to get an idea of how many people use Streams and recruit 
volunteers for testing new ideas and features.

My policy moving forwards is going to be to make small incremental plugin 
updates whenever I get the chance. Rather than spamming the group with 
announcements, I will provide a simple opt-in plugin updates mechanism 
until we have something in the core that serves the same purpose. 
See https://groups.google.com/g/tiddlywiki/c/5eewU5jOUlc

Group announcements of new updates will only be made if there is a breaking 
change, or a critical bug discovered.

I am tracking ideas for further development at github: 
https://github.com/saqimtiaz/streams/issues
*Constructive and relevant* input is always welcome.

Apart from the plugin update notifications, there are two other features 
that I have prototyped and would like to find time to flesh out:
i) visual feedback for swiping on nodes (mobile): 
https://www.reddit.com/r/TiddlyWiki5/comments/o4wfcq/streams_visual_feedback_for_swipe_experiment/

ii) a mechanism to easily see Streams keyboard shortcuts. In the video, the 
overlay is triggered by holding ctrl+space for 2s, and automatically closes 
when you let go of the keys: 
https://drive.google.com/file/d/1y-hLpDZAhVLKEr9QA_4_jMV2oqla-Kys/view?usp=sharing

Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2a026583-8844-4a8d-9379-9ee525d20b34n%40googlegroups.com.

[tw5] Re: Filter to return tiddlers that do not contain any members of a given list

[Saq Imtiaz]

Assuming your identifiers are alphanumeric and do not contain characters 
that might need to be escaped in regular expressions, something like this 
should work:

<$vars idListRegexp="[tag[Flashcard]get[identifier]join[|]]">
<$list filter="[all[tiddlers]!regexp]">
<>



On Saturday, July 10, 2021 at 4:47:58 PM UTC+2 Si wrote:

> Best explained with an example:
>
> I have a bunch of tiddlers tagged Flashcard, each with a field identifier 
> containing 
> some text.
>
> I want to return all the tiddlers that do not feature the values of *any* 
> identifier fields within their text.
>
> Initially I tried the following:
>
> <$list filter="[tag[Flashcard]get[identifier]]" 
> variable=flashcardIdentifier>
> <$list filter="[!search]">
> <>
> 
> 
>
> Of course this doesn't work because it is applying the search one at a 
> time and is thus returning the tiddlers that don't contain *all* the 
> identifiers. I want to return the tiddlers that don't contain *any* 
> identifiers.
>
> Anyway now I'm stuck, so I'm wondering if anyone can help me out?
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1c9be340-26c9-49c9-a8f7-17252000fb89n%40googlegroups.com.

Re: [tw5] Re: TiddlyWiki5, Raspberry Pi and Vim: A guide for the command line aficionado

[Saq Imtiaz]

Hi Gene,

No attribution needed from my end, if you feel its necessary a link to 
Github would do: https://github.com/saqimtiaz
Cheers,
Saq

On Saturday, July 10, 2021 at 4:20:39 PM UTC+2 he...@preciouschicken.com 
wrote:

> Thank you, interesting, I hadn't seen this plugin previously.  I've put a 
> link to this thread in the addendum; but I will enlarge the section and put 
> an explicit link to the plugin and include your code snippet too.  
> Incidentally do you have a home page / social media profile so I can 
> attribute you correctly (assuming you wanted that)?  
>
> Incidentally my blog posts are always like this - it is only when I've 
> finished them I find half a dozen interesting new ways of approaching the 
> problem :)
>
> Yours
> Gene
>
> On Friday, July 9, 2021 at 10:24:15 AM UTC+1 saq.i...@gmail.com wrote:
>
>> @Gene this plugin might be worth a look too:
>>
>>
>> https://github.com/linonetwo/tiddlywiki-plugins/tree/master/plugins/linonetwo/watch-fs
>>
>> "This plugin enables TiddlyWiki to watch the change in your disk, and if 
>> you edit one of your tiddler using editor likes VSCode and save it on the 
>> disk, the change will immediately reflected in the browser."
>>
>> On Wednesday, July 7, 2021 at 8:01:46 PM UTC+2 he...@preciouschicken.com 
>> wrote:
>>
>>> @Saq - Ha yes, that's a neat way of getting around the need for nodemon, 
>>> that I hadn't considered (mostly as I was ignorant of the API / focussed on 
>>> writing to the folder).  And you could call a bash script from Vim, or as 
>>> @David Shaw points out an even tidier way would be to write it with VimL.  
>>>
>>> If I have time for a project prior to the next release, I might give it 
>>> a whirl.  Thanks for the suggestion / education.
>>>
>>> Yours,
>>> Gene
>>>
>>> On Wednesday, July 7, 2021 at 10:22:19 AM UTC+1 David Shaw wrote:
>>>
>>>> Like Saq, I'm no Vim expert, but there's also the built in VimL 
>>>> language that might be able to do this without having to invoke external 
>>>> scripts.
>>>>
>>>> And thanks for the original post - very interesting and possibly of use 
>>>> to me.
>>>>
>>>> Many thanks,
>>>> David Shaw
>>>>
>>>>
>>>> On Wed, 7 Jul 2021, 09:50 Saq Imtiaz,  wrote:
>>>>
>>>>> Hi Gene,
>>>>>
>>>>> For the specific use case that your video demonstrates, i.e. creating 
>>>>> short new tiddlers rather than editing existing ones, have you considered 
>>>>> the following workflow:
>>>>>
>>>>> - don't write your newly created tiddler files to the wiki directory.
>>>>> - instead have vim do a PUT request with cURL to the tiddlywiki to 
>>>>> save the tiddler.
>>>>>
>>>>> API: 
>>>>> https://tiddlywiki.com/#WebServer%20API%3A%20Put%20Tiddler:%5B%5BWebServer%20API%3A%20Put%20Tiddler%5D%5D
>>>>>
>>>>> Example:
>>>>>
>>>>> curl -X PUT -i 'http://192.168.0.12:8080/recipes/default/tiddlers/
>>>>> NewTiddlerTitle' --data '{
>>>>>  "tags": "firstTag anotherTag",
>>>>>  "creator": "gene",
>>>>>  "modifier": "gene",
>>>>>  "text": "The use of knowledge in society"
>>>>> }' -H "X-Requested-With: TiddlyWiki"
>>>>>
>>>>> I don't use VIM myself but as far as I know it can execute bash 
>>>>> scripts so you could set one up to do the PUT with cURL. Alternatively 
>>>>> there seem to be VIM plugins specifically for interacting with APIs.
>>>>>
>>>>> Cheers,
>>>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0c830593-83f3-4da5-964f-97db385ff69en%40googlegroups.com.

Re: [tw5] [ demo ] Automated notifications for plugin updates

[Saq Imtiaz]

Hi Jeremy,

Using HTTPS requests was indeed my first instinct. I held back on going 
that route in this exploration due to two reasons:

i) I realized that the core already had everything in place that was needed 
- including UI - so this was very low hanging fruit for something only 
meant to start a conversation. 

ii) We still need to address the issue discussed in #4537 
<https://github.com/Jermolene/TiddlyWiki5/issues/4537>, namely that simple 
GET requests by the core via $tw.utils.httpRequest trigger an OPTIONS 
request which fails on Github pages and other hosting that has CORS enabled 
but does not support the OPTIONS method. This would need resolving here as 
well, and I also ran into this problem recently when trying to fetch the 
changelog for a plugin on demand via a canonical_uri tiddler.

I am curious though as to whether you are thinking in terms of using HTTPS 
to simply fetch metadata from plugin libraries, or an alternative means of 
publishing plugins that exposes the necessary information to check for 
updates. The plus with going via plugin libraries is that nothing needs to 
change in how plugins are currently published via libraries for them to get 
updates support. On the other hand a new way of exposing and publishing 
plugin version information could cut down on the bandwidth required for 
checking for updates, and perhaps allow including information on what has 
changed in the new version of the plugin.

I agree an opt-in plugin updates mechanism is worth considering for the 
core. I'll open an issue to further discuss requirements and implementation 
details when I get the chance. Some clarity on the potential benefits you 
see in going the HTTPS route for this, and whether you're still thinking in 
terms of interacting with plugin libraries via HTTPS, would be helpful in 
framing the issue.

Best wishes,
Saq

On Saturday, July 10, 2021 at 4:08:01 PM UTC+2 Jeremy Ruston wrote:

> Hi Saq,
>
> I think an easy opt-in mechanism to detect plugin updates would be worth 
> adding to the core.
>
> One thing that has changed fairly recently is that GitHub Pages is now 
> CORS enabled, so it would be possible to just use HTTP requests, instead of 
> the whole iframe shenanigans. It would be reasonable to stick with iframes 
> for everything that we do at the moment, so that 3rd party plugin libraries 
> hosted on non-CORS enabled servers would continue to work, with just 
> automatic update notification requiring CORS.
>
> Best wishes
>
> Jeremy
>
>
>
> --
> Jeremy Ruston
> jer...@jermolene.com
> https://jermolene.com
>
> On 10 Jul 2021, at 13:30, Saq Imtiaz  wrote:
>
> I've been wanting to make it easier to inform end users of my plugins 
> (well really just Streams) that there are updates available via an opt-in 
> mechanism for those that would like such a feature. I realized that for 
> plugins installed via a plugin library, the core actually already does the 
> work and can provide this information, there are just no affordances for it 
> unless one goes and specifically checks.
>
>
>
> It turns out that it is embarrassingly easy to set up visual notifications 
> for updates from a plugin library. Here is a demo of a quick 20 minute hack:
>
>
> https://drive.google.com/file/d/1vIj4BsA5OAhS6eFcKXn0LfJii88E3b6h/view?usp=sharing
>
> Caveats:
> 1. The major caveat is that the above demo re-uses core UI for plugin 
> updates which is geared towards working with one plugin library at a time. 
> If one wanted to use the same technique as what I have shown here to work 
> with multiple plugin libraries, a custom UI would be needed that could show 
> available updates across multiple libraries in one place. Or you know a 
> centralized plugin library that is automatically built at regular intervals 
> from specified plugin sources.
>
> 2. The plugins in question have to have a corresponding plugin library 
> installed. We could definitely make it easier to create plugin libraries. 
> However, personally I would prefer to work towards a centralized community 
> plugin library.
>
> 3. With the above technique, every time the wiki starts each plugin 
> library is fetched and loaded in the background. So this uses some 
> bandwidth. For reference, the official core library which has 61 plugins is 
> 243kb, whilst the demo library in the video which has 4 plugins is 5kb. So 
> for most use cases this shouldn't be a problem. Furthermore, updates could 
> be configured to only run once a day or week.
>
> 4. There are some shortcomings with the core UI for showing available 
> plugin updates.
>
> 
>
> i) the installed plugin version and the version of the update available 
> need to be far more prominent and easier to read.
>
> ii) There is no information displayed as to what co

[tw5] [ demo ] Automated notifications for plugin updates

[Saq Imtiaz]

I've been wanting to make it easier to inform end users of my plugins (well 
really just Streams) that there are updates available via an opt-in 
mechanism for those that would like such a feature. I realized that for 
plugins installed via a plugin library, the core actually already does the 
work and can provide this information, there are just no affordances for it 
unless one goes and specifically checks.

It turns out that it is embarrassingly easy to set up visual notifications 
for updates from a plugin library. Here is a demo of a quick 20 minute hack:

https://drive.google.com/file/d/1vIj4BsA5OAhS6eFcKXn0LfJii88E3b6h/view?usp=sharing

Caveats:
1. The major caveat is that the above demo re-uses core UI for plugin 
updates which is geared towards working with one plugin library at a time. 
If one wanted to use the same technique as what I have shown here to work 
with multiple plugin libraries, a custom UI would be needed that could show 
available updates across multiple libraries in one place. Or you know a 
centralized plugin library that is automatically built at regular intervals 
from specified plugin sources.

2. The plugins in question have to have a corresponding plugin library 
installed. We could definitely make it easier to create plugin libraries. 
However, personally I would prefer to work towards a centralized community 
plugin library.

3. With the above technique, every time the wiki starts each plugin library 
is fetched and loaded in the background. So this uses some bandwidth. For 
reference, the official core library which has 61 plugins is 243kb, whilst 
the demo library in the video which has 4 plugins is 5kb. So for most use 
cases this shouldn't be a problem. Furthermore, updates could be configured 
to only run once a day or week.

4. There are some shortcomings with the core UI for showing available 
plugin updates.
[image: plugin-updates.png]
i) the installed plugin version and the version of the update available 
need to be far more prominent and easier to read.

ii) There is no information displayed as to what core-version the updated 
plugin requires and whether that is compatible with the current version of 
the TiddlyWiki.

iii) While the core UI will display the "readme" tiddler if one clicks the 
dropdown arrow to the left of each plugin, this isn't the most relevant for 
plugin updates. What would be more helpful here is to display a release 
note specific for the new plugin version. Such a release note could contain 
a link to a fuller changelog elsewhere online. Currently the only option is 
to include such a release note in the "readme" tiddler, but this leads to a 
larger size for the plugin library. This is an issue that involves not just 
the core UI but also the plugin library creation mechanism.

Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/68a1febb-e9c5-4f3d-9d5a-5453bca88a16n%40googlegroups.com.

[tw5] Re: [ Streams ] Version number changes

[Saq Imtiaz]

@pmario I can relate.. if I had to manually craft change logs from scratch 
that would likely take up all the time I have for TW tinkering.

If you use the Conventional Commits spec for your commit messages, there 
are a lot of tools that can help generate changelogs:

https://www.conventionalcommits.org/en/v1.0.0/#tooling-for-conventional-commits

I am using Standard version 
, though I use 
it only to bump the version files, and generate the changelog. You can 
configure which steps you want it to skip. I commit the changes and create 
the git tag myself. This also allows me to review and hand massage the 
changelog if needed. What is great is that the tool is smart enough not to 
clobber your manual changes when you create the changelog for the next 
version.

Standard version uses the underlying conventional changelog library which 
also has a lower level 
CLI: 
https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-cli

Personally I think the Conventional Commits spec works well for TW plugins. 
It forces you to try to write a user friendly first line for your commit 
message, and technical details can go in later lines (the body). Each 
commit message starts with a type, eg fix, feat, docs. And you can specify 
those yourself and also decide which ones end up in the changelog.

Some of the other tools from conventional-changelog may be of interest as 
well:https://github.com/conventional-changelog

There may be better tools out there but I've been using these for some time 
on other projects so I am very used to them and have found them reliable.

Cheers,
Saq

On Friday, July 9, 2021 at 10:41:53 PM UTC+2 PMario wrote:

> Hi Saq, 
> Didn't know about Conventional Commits. Looks good. 
>
> How did you create your changelog? 
>
> I'd be interested in a similar workflow for my own plugins. 
> At the moment I'm manually creating my change logs, which is a lot of 
> "boring" work
> -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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ab6ce69f-da75-43a7-ad3a-46e24e861ff4n%40googlegroups.com.

Re: [tw5] Re: TiddlyWiki5, Raspberry Pi and Vim: A guide for the command line aficionado

[Saq Imtiaz]

@Gene this plugin might be worth a look too:

https://github.com/linonetwo/tiddlywiki-plugins/tree/master/plugins/linonetwo/watch-fs

"This plugin enables TiddlyWiki to watch the change in your disk, and if 
you edit one of your tiddler using editor likes VSCode and save it on the 
disk, the change will immediately reflected in the browser."

On Wednesday, July 7, 2021 at 8:01:46 PM UTC+2 he...@preciouschicken.com 
wrote:

> @Saq - Ha yes, that's a neat way of getting around the need for nodemon, 
> that I hadn't considered (mostly as I was ignorant of the API / focussed on 
> writing to the folder).  And you could call a bash script from Vim, or as 
> @David Shaw points out an even tidier way would be to write it with VimL.  
>
> If I have time for a project prior to the next release, I might give it a 
> whirl.  Thanks for the suggestion / education.
>
> Yours,
> Gene
>
> On Wednesday, July 7, 2021 at 10:22:19 AM UTC+1 David Shaw wrote:
>
>> Like Saq, I'm no Vim expert, but there's also the built in VimL language 
>> that might be able to do this without having to invoke external scripts.
>>
>> And thanks for the original post - very interesting and possibly of use 
>> to me.
>>
>> Many thanks,
>> David Shaw
>>
>>
>> On Wed, 7 Jul 2021, 09:50 Saq Imtiaz,  wrote:
>>
>>> Hi Gene,
>>>
>>> For the specific use case that your video demonstrates, i.e. creating 
>>> short new tiddlers rather than editing existing ones, have you considered 
>>> the following workflow:
>>>
>>> - don't write your newly created tiddler files to the wiki directory.
>>> - instead have vim do a PUT request with cURL to the tiddlywiki to save 
>>> the tiddler.
>>>
>>> API: 
>>> https://tiddlywiki.com/#WebServer%20API%3A%20Put%20Tiddler:%5B%5BWebServer%20API%3A%20Put%20Tiddler%5D%5D
>>>
>>> Example:
>>>
>>> curl -X PUT -i 'http://192.168.0.12:8080/recipes/default/tiddlers/
>>> NewTiddlerTitle' --data '{
>>>  "tags": "firstTag anotherTag",
>>>  "creator": "gene",
>>>  "modifier": "gene",
>>>  "text": "The use of knowledge in society"
>>> }' -H "X-Requested-With: TiddlyWiki"
>>>
>>> I don't use VIM myself but as far as I know it can execute bash scripts 
>>> so you could set one up to do the PUT with cURL. Alternatively there seem 
>>> to be VIM plugins specifically for interacting with APIs.
>>>
>>> Cheers,
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3e29ad77-2af2-4907-bcf5-20942f771631n%40googlegroups.com.

[tw5] [ Streams ] Version number changes

[Saq Imtiaz]

If you drop by https://saqimtiaz.github.io/streams/ you will see that the 
latest plugin version is now 1.2.21
This is functionally identical to the previous publicly available release 
0.2.19.

*There is no significance to the increase in version number for users.*
The motivation for this post was to head off any surprise or questions as 
to why the version number changed.

As an end user this is all that you really need to know and can stop 
reading here if you wish.

*Why the change?*
I've been revising the development and release workflow to be more 
efficient. This has included adopting the Semantic Versioning 
 and Conventional Commits 
 specs, which 
amongst other things will make it easy to provide users with a changelog 
for each release. See for 
example:  https://saqimtiaz.github.io/streams/#CHANGELOG

*Updates for new releases*
Overall my approach is likely to be to make small frequent updates and new 
releases *when* I have the time to work on Streams. A changelog will make 
it easier for users to know what has changed. I also have in the works an 
opt-in feature for Streams whereby you can be notified in your wiki when a 
new version of the plugin is available.

I ended up taking some unplanned time off the last week. I am aware that 
there has been some Streams related conversation during this time and will 
catch up in the next couple of days.

Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/88efc4f5-dcb4-4c88-9024-2dd3c347bfd7n%40googlegroups.com.

[tw5] Re: How to display a filtered transclusion with markup formatting?

[Saq Imtiaz]

@si

Try this:

\define context()


<$list filter="[get-stream-root[]addsuffix[: ]] 
[get-stream-root:includeall[]!search[<<*>>]rest[1]butlast[2]get[text]addsuffix[:
 
]] 
[get-stream-root:includeall[]!search[<<*>>]butlast[1]last[]get[text]]"
 
variable="x">
<>




\end

Throw in an extra line break before and after <> if you need it in block 
mode.

Alternatively if you really want to use the triple brace syntax:
{{{ filter || template }}}
Where template is a tiddler that just contains:
<>

On Wednesday, July 7, 2021 at 8:35:56 PM UTC+2 Si wrote:

> Hi Charlie.
>
> >>> Me thinks we are going to need to see the macro and/or a description 
> of what you're trying to do. 
>
> To be honest I don't think it is that relevant: the simplest way to 
> display the filter {{{ [[`test`]] }}} with wikitext formatting (and not 
> as a link) is all I want to know.
>
> The macro I am actually using is very messy, but here it is:
>
> \define context()
> 
> 
> {{{ 
> [get-stream-root[]addsuffix[: ]]
> 
> [get-stream-root:includeall[]!search[<<*>>]rest[1]butlast[2]get[text]addsuffix[:
>  
> ]] 
> 
> [get-stream-root:includeall[]!search[<<*>>]butlast[1]last[]get[text]]
> }}}
> 
> 
> 
> \end
>
> Edit: I pasted the wrong thing so deleted my previous message.
> On Wednesday, 7 July 2021 at 18:14:52 UTC+1 cj.v...@gmail.com wrote:
>
>> Me thinks we are going to need to see the macro and/or a description of 
>> what you're trying to do.
>>
>> On Wednesday, July 7, 2021 at 1:07:09 PM UTC-3 Si wrote:
>>
>>> Hi Eric, thanks for your reply.
>>>
>>> That doesn't seem to work for me? Adding the filtered transclusion 
>>> directly gives me the 'literal' text as a link.
>>>
>>> Even when I try it if I try something like this: {{{ [[`test`]] }}}. 
>>> This just displays `test`, but as a link.
>>>
>>> On Wednesday, 7 July 2021 at 16:56:54 UTC+1 Eric Shulman wrote:
>>>
 On Wednesday, July 7, 2021 at 8:43:11 AM UTC-7 Si wrote:

> I have a macro where I use the $text widget where the "text" 
> attribute is a filtered transclusion (i.e. {{{ [myfilter] }}} ).
> I've noticed that occasionally [myfilter] produces something 
> containing markup, which obviously gets rendered as plain text.
> E.g. <$text text={{{ [myfilter] }}}/> might output A __sentence__ 
> with ''formatting''.
> Is there some equivalent of the $text widget that will output the 
> text with the formatting applied?
>

 Don't use the $text widget.  Just put the filtered transclusion 
 directly in your wikitext, e.g.,
 {{{ [myfilter] }}}
  
 By default, the transcluded content will be "wikified", which will 
 automatically process any formatting syntax.

 enjoy,
 -e

>>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/495f70d4-f748-4f2c-bedb-d84959dd7c08n%40googlegroups.com.

[tw5] Re: TiddlyWiki5, Raspberry Pi and Vim: A guide for the command line aficionado

[Saq Imtiaz]

Hi Gene,

For the specific use case that your video demonstrates, i.e. creating short 
new tiddlers rather than editing existing ones, have you considered the 
following workflow:

- don't write your newly created tiddler files to the wiki directory.
- instead have vim do a PUT request with cURL to the tiddlywiki to save the 
tiddler.

API: 
https://tiddlywiki.com/#WebServer%20API%3A%20Put%20Tiddler:%5B%5BWebServer%20API%3A%20Put%20Tiddler%5D%5D

Example:

curl -X PUT -i 'http://192.168.0.12:8080/recipes/default/tiddlers/
NewTiddlerTitle' --data '{
 "tags": "firstTag anotherTag",
 "creator": "gene",
 "modifier": "gene",
 "text": "The use of knowledge in society"
}' -H "X-Requested-With: TiddlyWiki"

I don't use VIM myself but as far as I know it can execute bash scripts so 
you could set one up to do the PUT with cURL. Alternatively there seem to 
be VIM plugins specifically for interacting with APIs.

Cheers,
Saq

On Tuesday, July 6, 2021 at 10:21:56 PM UTC+2 he...@preciouschicken.com 
wrote:

> Sorry for delay in response, my first attempt seemed not to get picked up 
> by Google Groups.
>
> Anyway, I appreciate the reply; your set up sounds a lot more 
> sophisticated.  I too will use the new version as a prompt to see if I can 
> refine how I'm doing this, nodemon is fine but definitely feels slightly 
> kludgy.
>
> NB - I've added a video to my original blog post, realised my description 
> of creating tiddlers from the command line is clearer when you can see it.
>
> Yours
> Gene
>
> On Sunday, July 4, 2021 at 6:41:32 PM UTC+1 saq.i...@gmail.com wrote:
>
>> That is a very interesting setup, thank you for taking the time to share 
>> it.
>>
>> My use case for notes also involves interacting with them via text 
>> editors and other tools as well as  having them in TiddlyWiki. What I set 
>> up a few years back was a combo of fswatch + cURL + the tiddlywiki server 
>> API. Watching for file system changes wasn't as reliable at the time so the 
>> setup was a bit finicky and tricky to get it right. So I've never fiddled 
>> with the config or even upgraded the wiki once I had it working.
>>
>> The next version of TW includes a server sent events feature with which 
>> tiddlers propagate from the server to client almost instantly, so that will 
>> be my queue to upgrade that wiki. I will need to consider if moving to 
>> nodemon might make sense as well, I use it for TW dev at the moment and it 
>> does seem to work well enough.
>>
>> Cheers,
>> Saq 
>>
>> On Sunday, July 4, 2021 at 3:27:35 PM UTC+2 he...@preciouschicken.com 
>> wrote:
>>
>>> I hesitate slightly in posting to this group as my use case covers such 
>>> a niche audience, I'm not sure how much utility there is in sharing it.  
>>> However in short I wanted to host a TiddlyWiki on a Raspberry Pi, create 
>>> tiddlers from the command line and edit them with vim.  Once I figured out 
>>> how to do that I thought I'd blog about it (mostly so I can retrace my 
>>> steps later on):
>>>
>>>
>>> https://www.preciouschicken.com/blog/posts/tiddlywiki5-raspberry-pi-guide/
>>>
>>> I'm not sure the nodemon hack will be required in future, I think I read 
>>> another thread suggesting that this form of updating functionality might be 
>>> built in (though I could have got that wrong)?
>>>
>>> Many thanks to the creator and the maintainers of TiddlyWiki.  Really 
>>> enjoy using and playing around with it.
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1a6d434d-a720-47a7-8ea1-d7de680953b7n%40googlegroups.com.

[tw5] Re: TiddlyWiki5, Raspberry Pi and Vim: A guide for the command line aficionado

[Saq Imtiaz]

That is a very interesting setup, thank you for taking the time to share it.

My use case for notes also involves interacting with them via text editors 
and other tools as well as  having them in TiddlyWiki. What I set up a few 
years back was a combo of fswatch + cURL + the tiddlywiki server API. 
Watching for file system changes wasn't as reliable at the time so the 
setup was a bit finicky and tricky to get it right. So I've never fiddled 
with the config or even upgraded the wiki once I had it working.

The next version of TW includes a server sent events feature with which 
tiddlers propagate from the server to client almost instantly, so that will 
be my queue to upgrade that wiki. I will need to consider if moving to 
nodemon might make sense as well, I use it for TW dev at the moment and it 
does seem to work well enough.

Cheers,
Saq 

On Sunday, July 4, 2021 at 3:27:35 PM UTC+2 he...@preciouschicken.com wrote:

> I hesitate slightly in posting to this group as my use case covers such a 
> niche audience, I'm not sure how much utility there is in sharing it.  
> However in short I wanted to host a TiddlyWiki on a Raspberry Pi, create 
> tiddlers from the command line and edit them with vim.  Once I figured out 
> how to do that I thought I'd blog about it (mostly so I can retrace my 
> steps later on):
>
> https://www.preciouschicken.com/blog/posts/tiddlywiki5-raspberry-pi-guide/
>
> I'm not sure the nodemon hack will be required in future, I think I read 
> another thread suggesting that this form of updating functionality might be 
> built in (though I could have got that wrong)?
>
> Many thanks to the creator and the maintainers of TiddlyWiki.  Really 
> enjoy using and playing around with it.
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c8b8fbff-198c-49b9-b82f-2714b01ab274n%40googlegroups.com.

[tw5] Re: Streams : "strange behaviour" when transcluding a root tiddler

[Saq Imtiaz]

Or alternatively this is probably faster:

{{{ [has[stream-list]!has[parent]] }}}

On Sunday, July 4, 2021 at 2:38:22 PM UTC+2 Saq Imtiaz wrote:

> @Walt
>  
>
>> Puts me to wonder (not exactly on-topic, but related): is there some such 
>> simple script i could plug into a tiddler to display a list of all the 
>> other tiddlers that have any n>0 number of nodes (i.e. Streams) attached?
>>
>>
> {{{ [has[stream-list]get-stream-root[]] }}}
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/64c59be2-0e0d-417f-9b81-522b0ee77e51n%40googlegroups.com.

[tw5] Re: Streams : "strange behaviour" when transcluding a root tiddler

[Saq Imtiaz]

@Walt
 

> Puts me to wonder (not exactly on-topic, but related): is there some such 
> simple script i could plug into a tiddler to display a list of all the 
> other tiddlers that have any n>0 number of nodes (i.e. Streams) attached?
>
>
{{{ [has[stream-list]get-stream-root[]] }}}

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/141771cb-81cd-4fa0-a7f7-01bc3e39dc0fn%40googlegroups.com.

[tw5] Re: Streams : "strange behaviour" when transcluding a root tiddler

[Saq Imtiaz]

Since the nodes are separate tiddlers, they don't show up with a normal 
transclusion.
You need to transclude through a template: 

{{TiddlerTitleHere||$:/plugins/sq/streams/nodes-list-template}}

On Friday, July 2, 2021 at 9:27:45 PM UTC+2 FrD wrote:

> Hi (specially Saq) !
>
> Thank you Saq for your fine piece of sofware. Its works flawlessly for my 
> occasionnal note taking (or organizing).
> Recently I've being trying to organize notes from watching a video.
> I wanted to transclude in a tiddler, below the video, the root tiddler of 
> my notes : {{Personal Notes for Class 01}}. And nothing shows.
> Maybe I missed something from the documentation ...
> I've tried on your demo site to transclude the tiddler "Streams 0.2 
> improvements" inside a new tiddler and same problem. The only tiddlers that 
> are showing as transclusions are the "leaf" tiddlers.
>
> Is there a way to make a root tiddler appear when transcluded ?
>
> Thanks in advance
>
> Best regards
> FrD
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/23d037a7-49c3-48cc-9657-77cc57a5383fn%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

@walt

For the flatten capability you only need the tiddlers numbered 1-5
In particular I would advise caution against using the  stream-row-template 
override.

If you drag and drop and import those 5 tiddlers, the flatten button will 
turn up at the bottom of the stream as long as the stream has some nodes.

On Tuesday, June 29, 2021 at 7:16:58 PM UTC+2 ludwa6 wrote:

> Hey @Jan: Great to hear!
> So following these instructions , i have 
> installed everything on that page below the Streams and Relink plugins 
> (which i already have) -everything but the German language thingy.  That is 
> to say: additional tiddlers numbered 1-5, plus stream-row-template, the two 
> things under "A button to show the keyboard shortcuts," plus the 
> MobileTweaks... But for all that, i cannot get any new button to reveal, 
> nor does alt+f do anything useful ( on my mac, it enters the ƒ character).  
> Of course i've saved, refreshed, tried in different browsers, etc.
> Any idea what i might have got wrong, or what else must i do, to get this 
> add on working?
>
> /walt
>
>
> On Tuesday, June 29, 2021 at 12:42:47 PM UTC+1 Jan wrote:
>
>> Hi Walt, I am happy to announce that the streams to text is finally 
>> updated: https://szen.io/stream/ . Thanks to Saq who has gently helped 
>> me and provided hooks within the plugin, that make it fun tinkering with 
>> the plugin, this version should be more future-proof than the last ones
>> . 
>> As always: Backup before using it to recompress the ideas, you collected 
>> with streams. 
>>
>> Enjoy,
>> Jan
>>
> ... 
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f3163bb7-a6a5-4a9a-9539-61fdc3e26bc6n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

>
> It seems the *breadcrumbs feature* could be split out into a generic 
> plugin itself...
>

@Tones please feel free to do so. It is only about ten lines of wikitext. 
As I've previously mentioned, the initial motivation for writing Streams 
and doing so almost entirely in wikitext was to motivate and inspire others 
in terms of what was possible in wikitext.

Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/708834df-9cfb-470d-95c7-6c056dce0ac2n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

Thank you Stan and Steph. 
I'll post a link here and on reddit once the questionnaire is ready. 


On Tuesday, June 29, 2021 at 1:07:37 AM UTC+2 stan...@gmail.com wrote:

> You can add me to the list for the questionaire.  Streams is an excellent 
> addition to TW.
> Stan
>
> On Monday, June 28, 2021 at 1:44:26 PM UTC-4 saq.i...@gmail.com wrote:
>
>> @si
>>  
>>
>>> I've also been considering asking for volunteers for a small group of 
 regular users of Streams for testing new features..
>>>
>>>
>>> I'm happy to test stuff out as required.  
>>>
>>
>> I think I will start out with a questionnaire and also use that as an 
>> opportunity to ask for volunteers for testing.
>>
>> I will give some more thought to the breadcrumbs.
>>
>> 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3d0dde82-8027-45e6-9b1f-cb227ed0534fn%40googlegroups.com.

[tw5] Re: butlast filter operator

[Saq Imtiaz]

This is essentially an oversight and will be fixed. Thank you for bringing 
this up.

https://github.com/Jermolene/TiddlyWiki5/issues/5833

On Sunday, June 27, 2021 at 8:28:50 PM UTC+2 History Buff wrote:

> All,
>
> I have a general question about the butlast filter operator. I had a 
> filter where I had the butlast operator as the last item with a variable 
> for the parameter. All worked fine until the variable was 0.  I expected 
> that it wouldn't remove any of the last items, but what I got was no 
> results at all. I fixed it be making sure that the variable was never 0, 
> but I don't understand why a 0 in the butlast operator would yield no 
> results. Can anyone explain that to me? 
>
> Thanks so much!
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8671095c-6891-47c0-b2b9-979149a4af46n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

@si
 

> I've also been considering asking for volunteers for a small group of 
>> regular users of Streams for testing new features..
>
>
> I'm happy to test stuff out as required.  
>

I think I will start out with a questionnaire and also use that as an 
opportunity to ask for volunteers for testing.

I will give some more thought to the breadcrumbs.

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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5d07bccc-60ad-4725-8d4b-fc1c1e7e2000n%40googlegroups.com.

Re: [tw5] Artwork for v5.2.0

[Saq Imtiaz]

It is probably worth mentioning that the logo does not *have* to do with 
any new features being introduced. So if anyone has other ideas, go for it.

On Sunday, June 27, 2021 at 7:02:55 PM UTC+2 springer wrote:

> I've tweaked a *bit* more, and added Mohammad's submission to our gallery 
> at:
>
> https://tw-logo-contest.tiddlyhost.com/
>
> -Springer
>
> On Sunday, June 27, 2021 at 12:49:06 PM UTC-4 springer wrote:
>
>> Hi all, I had an exchange with Mohammad about the actual graphic file, to 
>> which he does not have access.
>>
>> But the work was based on his own sketches, and it's not too hard to 
>> replicate after discovering that the font is open-source Saira (google 
>> font), apart from the curly brackets, whose font isn't yet clear to me. So 
>> here's a rough mockup of Mohammad's design, though I admit I haven't 
>> obsessed about replicating all the details:
>>
>> [image: Mohammad's JSON logo mockup.png]
>>
>> On Saturday, June 26, 2021 at 1:56:58 PM UTC-4 Mohammad wrote:
>>
>>> Just to have a little fun in this competition!
>>>
>>> These are my designs, but I'm not sure if they are suitable for the new 
>>> release logo! 
>>>
>>> [image: image.png]
>>>
>>>
>>>
>>> [image: img_342_chrome.png]
>>>
>>>
>>> and also!
>>>
>>> [image: img_341_chrome.png]
>>>
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Sun, Jun 13, 2021 at 3:44 PM Jeremy Ruston  
>>> wrote:
>>>
 This is to announce our regular competition for the artwork for the 
 next release of TiddlyWiki 5. The next release is planned to be called 
 v5.2.0, which requires a little explanation.

 We've bumped the minor version number because of a single very 
 important change: for the first time in a decade, we're changing the 
 format 
 used to encode tiddlers into the HTML file.

 The new format is based on JSON, making it much easier to develop tools 
 that produce or consume TW5 standalone HTML files. While there is some 
 limited backwards compatibility, the developers of many existing tools 
 will 
 need to make modifications to keep things working with v5.2.0.

 Hence the version number change: it's intended to make every developer 
 ask "Gosh, what could have changed to warrant such a big jump", and helps 
 us to make sure that the news of the change is promulgated as widely and 
 prominently as possible.

 The change also brings one big improvement for all users: field names 
 now have no restrictions on which characters can be used, and are 
 case-sensitive so that "MyField" is a valid fieldname, and refers to a 
 different field than "myfield" (just like tiddler titles). Finally, we can 
 have fields called "⛄️".

 These changes will be merged shortly, but in the meantime can be 
 inspected here:

 https://github.com/Jermolene/TiddlyWiki5/pull/5708

 So, with that, back to the artwork competition. The task is to design 
 the banner image that is shown on the splash screen and within the opening 
 HelloThere tiddler. It is traditional for the artwork to reflect some of 
 the changes in the new version.

 The rules for the competition are:

 * The version number (with the correct punctuation) must be clear and 
 readable even when the banner is shown at a reduced size
 * The image must be a PNG, JPEG or SVG of exactly 560x315 pixels
 * The bottom 46 pixels will be obscured by the banner text “What’s new 
 in 5.2.0” when it is displayed within HelloThere
 * Feel free to enter an updated version of artwork that was a runner-up 
 in a previous competition
 * Reply to this message with your entry, or any questions

 Here are the posts about previous artwork competitions:

 v5.1.23 - 
 https://groups.google.com/g/tiddlywiki/c/cTgPWl8b_9c/m/VtrMFHBGAwAJ
 v5.1.22 - 
 https://groups.google.com/g/tiddlywiki/c/rYrja18_SfQ/m/JAklPfjfAwAJ
 v5.1.21 - 
 https://groups.google.com/g/tiddlywiki/c/l47ZZzWdDb8/m/6s0p_3QeCgAJ

 If you’ve got a great idea for the banner image, but don’t have the 
 skills to produce finished artwork, do feel free to share your ideas in 
 case somebody else would like to work on the artwork.

 The competition will be open for a week, at which point if there is 
 more than one submission I’ll set up a Google Form for voting.

 Best wishes and many thanks,

 Jeremy

 --
 Jeremy Ruston
 jer...@jermolene.com
 https://jermolene.com

>>> -- 
 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 tiddlywiki+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/41EF749B-8AC8-412E-BE59-BBFCE7164340%40gmail.com
  
 

[tw5] Re: Restyling a drop zone

[Saq Imtiaz]

 

> Saq, thanks, that was *very* helpful. (For anyone else who comes along, 
> that should be "tc-dragover", with a dash, not a dot.)
>
 
 Happy it helped and apologies for the typo.

Another neat trick when trying to inspect tricky CSS that involves 
transient states is to trigger the debugger after a time out by executing 
this in the console:

setTimeout(function() { debugger; }, 2000);

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7ef74a3d-53dc-4828-a3ac-61dba5c9c801n%40googlegroups.com.

[tw5] Re: Restyling a drop zone

[Saq Imtiaz]

Inspect the dropzone DOM node with the browser dev tools and add the class 
"tc.dragover". This will allow you see what CSS is active during the drag 
over and make it easier to arrive at a solution.

On Sunday, June 27, 2021 at 1:18:07 AM UTC+2 Soren Bjornstad wrote:

> I'm creating a horizontal list of my open tiddlers that runs across the 
> top of the wiki, like this:
>
> [image: Screenshot from 2021-06-26 18-13-01.png]
>
> It's based on *list-links-draggable* and works great except for when I 
> try to drag something to a different position. When I try, the bar scrolls 
> to fit the dropzone on a separate line, so that I can no longer see where 
> I'm moving the tiddler to:
>
> [image: 2.png]
>
> I tried poking through the theme CSS for a bit, but wasn't able to find 
> anything that worked. It doesn't help that it's impossible to carefully 
> inspect the DOM with the browser devtools since the mouse is tied up with 
> the drag. Can someone point me to how I'd make the dropzone end up 
> horizontally inline with the items, instead of above/below them?
>
> Here's the code of the tiddler/CSS that I currently have:
>
> 
> <>
> 
>
> 
> div.sib-quick-tiddler-jump {
> background-color: <>;
> position: fixed;
> z-index: 850;
> display: inline-block;
> top: 0;
> right: 0;
> left: 0;
> text-align: center;
> height: 25px;
> overflow: auto;
> border-bottom: 1px solid <>;
> padding-bottom: 3px;
> padding-top: 3px;
> font-size: 12px;
> }
>
> div.sib-quick-tiddler-jump a {
> color: <>;
> }
>
> div.sib-quick-tiddler-jump a.tc-tiddlylink-shadow {
> font-weight: normal;
> }
>
> div.sib-quick-tiddler-jump .tc-dropzone.tc-dragover:before {
> display: block;
> position: relative;
> top: 0;
> left: 0;
> right: 0;
> }
>
> div.sib-quick-tiddler-jump ul {
> list-style-type: none;
> margin: 0;
> padding: 0;
> }
>
> div.sib-quick-tiddler-jump ul li {
> display: inline-block;
> }
>
> .sib-quick-tiddler-jump ul li div:after {
> padding-left: 5px;
> content: "·";
> padding-right: 5px;
> }
>
> /* not last-child because there's a dropzone after it */
> .sib-quick-tiddler-jump ul li:nth-last-child(2) div:after {
> content: "";
> }
> 
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ec86298b-8daa-4139-ad67-cfe6e62bc635n%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

@walt 

> Saq, i just hope that the enthusiasm of your user community here is 
> sufficient to retain your continuing interest in Streams.  
>

Unless something very unexpected happens, I am committed to at least 
maintaining Streams in its current form for the long term. So you need not 
worry that it will stop working or not be updated for new TW versions etc.

Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/da770578-625b-4987-b002-37d997ef84e1n%40googlegroups.com.

[tw5] Re: Streams Plugin - Splitting text

[Saq Imtiaz]

Hi Steve,

trying using just split instead of /split/gi
Under the covers, the value provided is being used as an operand to the 
filter operator splitregexp:
https://tiddlywiki.com/#splitregexp%20Operator

Hopefully this will help you better formulate your regular expression. I'll 
add some disambiguation to the docs about this when I get the chance. 

Do note that this split feature was born out of a need to get data quickly 
into Streams for testing purposes during its development. As such it is a 
relatively simple implementation. Streams mostly focuses on writing content 
and dividing it into tiddlers as you write.

For a richer solution for splitting existing content, perhaps have a look 
at Notowritey:
https://links.tiddlywiki.com/urls/83843a24db5f93e7248d/


On Saturday, June 26, 2021 at 11:41:18 AM UTC+2 SteveH wrote:

> Hi again,
>
> I've  changed the settings to try using a word per:
>
> Regular expression used to split text : /split/gi
>
> - unfortunately can't get this to work.
>
> Regards
> hsteve
>
>
>
> On Saturday, 26 June 2021 at 7:56:21 am UTC+10 SteveH wrote:
>
>> Thank you Saq and Si for your help. Much appreciated.
>>
>> On Friday, 25 June 2021 at 10:47:21 pm UTC+10 Si wrote:
>>
>>> Hi hsteve. There are two ways to split text:
>>>
>>> 1. If you are editing a node and press enter, the stream will be split 
>>> at the location of the caret/curser.
>>> 2. If you are editing a node and press alt+enter, the text will be split 
>>> at every place there is a new line.
>>>
>>> Note that /n/n is a regular expression that represents any new line. 
>>> It's not something you have to actually add to the text.
>>>
>>> On Friday, 25 June 2021 at 12:27:04 UTC+1 SteveH wrote:
>>>

 Hi,

 A basic question relating to text splitting within a single long text 
 tiddler.

 The plugin settings show 

- Regular expression used to split text = /n/n
- Split text at caret position

 Inserting /n/n/ or a claret didn't seem to work .  

 Looking for help here.

 Regards

 hsteve




-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a7470c66-6af3-4527-aa6e-6f85ec6fe08cn%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

@Walt hopefully you are getting some helpful feedback here. Apologies for 
the slight digression caused by my replying to Streams specific comments 
and feedback.

@fred you can also export using a filter from the Filter tab in Advanced 
Search

@Si,
 

> On the topic of how many people use it, maybe you could consider creating 
> a Google Form and linking to it from the download page, asking users if 
> they would take a second to answer some brief questions?
>

I've been considering it for some time actually. Apart from feedback on 
workflow, just knowing whether the number of people regularly using Streams 
is < 10, 10-20, or 20+ would be very helpful.
 

> I was also wondering if you had considered setting up a way for users to 
> donate? Not necessarily to fund development, just to show appreciation for 
> great free software! I am not currently in a position to contribute much, 
> but in the future I would certainly be happy to subscribe to a patreon or 
> whatever.
>

I think the most value for myself would be in just getting regular, precise 
and on-topic feedback. Implementing new features in the absence of user 
feedback is just driving blind from my perspective. I also find it very 
frustrating and motivation sapping when I post ideas or demos and at times 
get feedback that is far off topic or just so poorly written that it is 
more frustrating than helpful.  Mind you, I try to be very understanding of 
users for whom English is not their first language. It is actually very 
pleasing how constructive and helpful this thread has been thus far in 
comparison.  

I've also been considering asking for volunteers for a small group of 
regular users of Streams for testing new features.. from my perspective 
however how, much effort I put into adding new features to Streams is 
highly dependent on how many people regularly use it and find that it 
imparts value. Call it a personal quirk but wanting to impart the most 
value possible is something that often drives my decision making in terms 
of what I dedicate my time to. Otherwise the motivation for work on Streams 
is just whatever seems interesting for me personally from a technical 
perspective.
 

> I would add that like Mario I am very happy with the current features of 
> streams, though I have made the following tweak to the text display for the 
> breadcrumbs. It's a very minor thing, but in my opinion looks nicer than 
> just cutting off the title mid-word:
>
> <$text text={{{ 
> [length[]compare:number:lt[40]then] 
> ~[split[]first[40]join[]trim[]addsuffix[...]] }}}/>
>

That is definitely a nice idea. I wonder if we might take it a step further 
and just drop the last word (which may be incomplete). This is untested:

 <$text text={{{ 
[length[]compare:number:lt[40]then] 
~[split[]first[40]join[]trim[]search-replace:g:regexp[(.*)\s(\w+)$],[$1]]
 
}}}/>

What do you think?
Cheers,
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0b65a408-28d6-4709-8e16-feb01355858en%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

>
>
> +@saq: you will however note this pattern of moving nodes from one tiddler 
> to another also disrupts the powerful relink tool when you rename the root. 
> Only child nodes that match the title prefix are updated; meaning anything 
> you dragged from a different origin retains its old name. The alternative 
> would be the drag n' drop action also updates the child node title to the 
> destination tiddler.
>

I've added an issue so that the idea isn't 
lost: https://github.com/saqimtiaz/streams/issues/22

However, note my reservations about how such a behaviour would be highly 
dependent on the title configuration being used and therefore adding it may 
not be feasible. This is the downside of allowing such a high level of 
configuration and customization.

 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8f88ad8d-2002-4512-b00e-8f2756044d2an%40googlegroups.com.

Re: [tw5] NoteTaking in Streams

[Saq Imtiaz]

@Fred could you please elaborate on what this side effect is that you 
mention?

I my workflow, I treat them as sub-tiddlers really. You could say I 
> replaced larger tiddlers with multiple headings with much smaller streams 
> nodes (but not single line ones); main advantage is I can move nodes 
> around, indent them, etc... and drag them from one tiddler to another 
> (although I have recently noted this has an unfortunate side effect).


Thank you. 

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5407c9c6-b723-4d61-88c1-ad3a1bef24e5n%40googlegroups.com.