date:20200630

Mark S. wrote:

Below is a modified

   $:/core/macros/export 
> tiddler. Now when you click on the "export tiddler" option, you get two 
> more choices. One copies the rendered tiddler to HTML, and the other copies 
> to plain text.
>
> I don't think copying the all-up wikitext would be easy. There are no 
> tools for collecting the *rendered output* of a tiddler as wikitext. You 
> can get the parsetree(s), but then you'd have to turn them back into 
> wikitext, which is likely to be non-trivial. You could capture the exact 
> wikitext for the single tiddler, but that wouldn't be very useful.
>

Very useful! That, along with your Tiddler WikiText collector in Noto 
covers most any situation.

FYI, the pure text one is particularly interesting to me as that is what 
screenplays are. Using it you can "capture" pure text (even when produced 
by a specialised parser, e.g. Fountain.io rules).


Best wishes
TT

-- 
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/6c29de97-5415-4271-bb59-d8bcaa1c168do%40googlegroups.com.

[tw5] Re: Request for some feedback

Ash Rubigo wrote:
>
> It'd be great to get some feedback on on the aesthetic, layout, and 
> navigability of my wiki http://www.ashrubigo.com/. 
>


   - Am I the only one who doesn't get any scrolling when clicking the 
   links? (win/chrome)
   - I'm on desktop: It says "Show/hide sidebar" but it not obvious that 
   the whole upper part of the page, which is actually the whole default 
   viewport, is what is referred to.
   - The first default tiddler is... unclear; why is the title (if it is 
   the title?) in brackets? Or maybe the big blue is the title? But there seem 
   to be tag pills under both? 
   - If it is a public site, you should probably remove most of the tiddler 
   tool button showing only the close button (X) and page tools.
   - Blue fine links on black... IMO not good for visibility.
   - Aesthetics: I understand the darkness is intentional but you do ask 
   for feedback so I'll just mention that I don't like these dark themes other 
   than as "night" themes. Just my opinion.


<:-)

-- 
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/ea3fed82-5097-4407-85b8-6e59cc3c1375o%40googlegroups.com.

[tw5] Re: Adding text to newly imported tiddlers

As Tony notes, is it the same text that is to be inserted for them all?
Would it be OK if it was really inserted via a viewtemplate rather than to 
manipulate the text field? This would appear the same when you look at the 
tiddler. A viewtemplate solution would be simpler but the text would e.g 
not register in standard "search"... (which might be a good thing if it is 
a recurring text.)

<:-)

-- 
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/6a1ad222-79a5-4ff3-90b2-174da334784bo%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

Ciao Mark

I spent a while working with the outliner. 

I had hoped to get the entries in TiddlyWiki Toolmap into it (simply to 
help me track issues I want to report to David.)

It brought up the problem I encountered before with performance.

My current impression in Outliner Mode Noto does a great job until you 
start to get to larger numbers. Though could be me trying to do too much at 
once in splits.

For instance, After prep, I was able to get it to accurately split 
Gifford's list at all the main "Section" headers. And then started 
splitting each section into individual items for each entry under it. 
Pretty quickly changing things got super slow.

If I get a chance I might try it a different way by fully preparing 
Tiddlers in Noto format First.

Just comments.
Best wishes
TT



On Monday, 29 June 2020 05:04:57 UTC+2, Mark S. wrote:
>
>
> I thought I'd add a little to the documentation, and then I discovered a 
> bug in the split routine. I'm surprised no one else came across it. 
> Hopefully it's fixed now.
>
> Plugins are now a standard part of the NW distribution. So any time you 
> want to upgrade your existing NW file you can just drag and drop the plugin 
> in from the plugins section. Note that you should first delete the 
> following individual (non-shadow) tiddlers from your file if they exist:
>
>- $:/core/images/chevron-down 
>- $:/core/images/chevron-left 
>- $:/core/images/chevron-right 
>- $:/core/images/chevron-up 
>- $:/core/images/fold-button-minus 
>- $:/core/images/menu-button-hamburg 
>- $:/core/images/unfold-button-plus 
>- $:/plugins/MAS/NotoWritey/readme 
>- DocumentTemplate 
>- Folding Macros 
>- MoveSelection 
>- NotoWritey Macros 
>- NotoWritey Styles 
>
> Currently there is no separate project for the plain editor vs. the 
> outliner -- it's all outliner. I probably won't be pursuing the dynaview 
> option, since that didn't seem to improve performance.
>
>
> As a reminder, the NW file can be found at:
>
>
> https://marxsal.github.io/various/notowritey.html
>
>
>

-- 
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/a8818875-183b-41ce-b4c6-c358c7f9ad41o%40googlegroups.com.

[tw5] Re: TiddlyWiki Hangout #107 with Matt Lauber and Reece Shaw

I enjoyed the video

Great to see and hear being done what I imagined could be done. I was a DND 
play when in high school and University.

The ad hoc or extensible database that can develop overtime is I believe a 
key feature of tiddlywiki. With DND you could even build virtual 
multi-sided dice and other things needed. 

TiddlyMap shows that tiddlywiki is not wanting for features.

Regards
Tony

On Tuesday, June 30, 2020 at 4:47:19 PM UTC+10, Saq Imtiaz wrote:
>
> I feel like this is a more common use case than one first realizes, there 
> have been regular posts and questions about usage for running role playing 
> games since the days of TWC.
>
> The combination of TiddlyMap and images could be translated back to our 
> own world. Use a world map or portion there of, to map/plan trips or keep a 
> visual travel log. Add in KML/KMZ support and the combination could be 
> powerful.
>
> On Monday, June 29, 2020 at 2:04:24 PM UTC+2, Jeremy Ruston wrote:
>>
>> TiddlyWiki Hangout #107 is now out, with special guests Matt Lauber and 
>> Reece Shaw:
>>
>> https://www.youtube.com/watch?v=Imx-EzCOWGc
>>
>> Matt and Reece show how they use TiddlyWiki to run tabletop Dungeons and 
>> Dragons games, demonstrating some interesting techniques, including a novel 
>> integration with TiddlyMap, handling lots of custom data, and performing 
>> arithmetic on custom calendars for Earth-like planets. It’s a fascinating 
>> journey whether or not you know anything about D&D.
>>
>> Unfortunately, we suffered some frustrating technical problems, resulting 
>> in some audio dropouts, and the loss of video for the last few minutes. My 
>> apologies. I’m shortly recording the next hangout with David Gifford with 
>> hopefully improved technology!
>>
>> My thanks again to Matt and Reece,
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>

-- 
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/b42de180-5c1d-436e-b16d-cc35959f4f33o%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW


Mark S. wrote:
>
>  I probably won't be pursuing the dynaview option, since that didn't seem 
> to improve performance.
>
>
> As a reminder, the NW file can be found at:
>
>
> https://marxsal.github.io/various/notowritey.html
>
 

Ciao Mark

Regarding performance and Dynaview---looking at the eBook version of 
TW---seems to indicate its optimal for fully prepped, pre-ordered Tiddlers.
I don't fully understand how it works yet, especially its "chunkology". Xavier 
helpfully commented this though ...

 Xavier wrote:
>
> Hi TT,
>
> In order to fulfil some of the user interface requirements, like keeping 
> track of the current reading location or creating annotations anywhere 
> inside the text, Jeremy introduced Dynaview, then Dynannotate.  In the 
> context of ePub reading, Dynaview's aim is to reveal on demand the little 
> chunks that have been produced at ePub parse time, along with their 
> possible annotations. Once you have this collection of chunks (aka 
> tiddlers), the performance, while still subject to optimisation, is not 
> much of a worry: these chunks are not tangled nor even weaved together 
> through any complex cross-references system. At the time Dynaview comes 
> into play, the list of chunks is already sorted, waiting to be displayed at 
> reading pace. That's because ePub is a much poorer and linear format than 
> TiddlyWiki of course. Fortunately, what can do more, can do less.
>
> By the way, being able to split any ePub into chunks is probably the 
> hardest part of the project. Not only because choosing the chunks limits 
> can be hard, but also because styles are often used very loosely by 
> publishers : for instance, you may find paragraphs that are expressed as 
>  style="font-size: 11pt;display: block;text-indent: 0pt;">The first 
> paragraph of a section, as you have to guess. because the WYSIWYG 
> tools that helped producing the ePub are generally misleading. I spare you 
> the table and images issues :-)
>
> Cheers,
> -- Xavier Cazin
>
>
> On Sat, Jun 27, 2020 at 6:43 PM TiddlyTweeter  wrote:
>
>> Xavier
>>
>> There is interest in it growing.
>>
>> I think the very good PERFORMANCE aspect is particularly interesting 
>> since eBooks are large documents.
>>
>> Over in GG we did some tests with Dynaview but still hitting issues which 
>> the eBook version does not have. I think better understanding the eBook 
>> edition of TW will help a lot.
>>
>> Fingers crossed x
>>
>> Best wishes
>> TT
>>
>> Xavier wrote:
>>>
>>>
>>> Not yet ready because of some pressing redesign, but it will eventually 
>>> be released as a normal 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/bf575701-1124-40c5-a5c4-b57c8b4aaeb9o%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

2020-06-30 Thread Saq Imtiaz

@TT could you post the document with TiddlyToolmap imported? I have a suspicion 
about where the performance hit on editing is coming from and comparing side by 
side to Streams (in which I have Tiddly toolmap imported) will be a quick way 
to check if I'm on the right track... Without having to dive into code.

-- 
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/69ee46b3-3efd-423f-aee5-c4af16a6221co%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

Saq

Sure, I will. Later today I put it on line.

TT

On Tuesday, 30 June 2020 10:37:11 UTC+2, Saq Imtiaz wrote:
>
> @TT could you post the document with TiddlyToolmap imported? I have a 
> suspicion about where the performance hit on editing is coming from and 
> comparing side by side to Streams (in which I have Tiddly toolmap imported) 
> will be a quick way to check if I'm on the right track... Without having to 
> dive into code.

-- 
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/fa53a478-9014-4f41-982b-4ba5b9cf9594o%40googlegroups.com.

[tw5] Re: Presenting: field value selector

2020-06-30 Thread Cyrill Andreani

Mat, 
Thanks to your reactivity. The version is drift, derived from Roam/Stroll 
of course.
I delete the core tiddler and will check the usibility of this edition.
:)

Mat schrieb am Montag, 29. Juni 2020 um 19:55:17 UTC+2:

> @David Gifford and @Cyrill
>
> OK, after having had a look at Cyrills file, I note that the core shadow 
> tiddler $:/core/ui/EditTemplate/fields is modified in... is it called 
> Stroll or Roam (sorry). That core tiddler was updated in October last year (
> here 
> )
>  
> but Stroll/Roam seems to use the older version and possibly with some other 
> customizations (I didn't search).
>
> If this tiddler is deleted, then the core version of it is restored 
> automatically, and fieldvalueselector works. But then any mods critical for 
> Stroll/Roam are of course lost *IF *there in deed are any. That is 
> hopefully something @David can answer - otherwise you (@Cyrill) can 
> investigate any differences between the Stroll/Roam version of that tiddler 
> and the updated core version. FieldValueSelector uses the
> <> instead of the old $:/temp/newfieldname so that is 
> the only difference that I can tell is problematic for sure.
>
> <:-)
>

-- 
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/4f4271e0-b0ea-4dc5-9907-d8626ffbb6fan%40googlegroups.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

Hello

Thank you for responding to my query. It is probably worth outlining what i
am trying to achieve. I have some data in a database and, with Eric's help,
I have transferred that data via JSON into a number of tiddlers with data
in a number of fields. To see the data I have to add the same text to the
body of every tiddler so I would like to add that text to the new tiddlers
on import. Possibly a different solution to the problem that I outlined in
my first email.

Does that help?

Rob

On Tue, 30 Jun 2020 at 09:09, Mat  wrote:

> As Tony notes, is it the same text that is to be inserted for them all?
> Would it be OK if it was really inserted via a viewtemplate rather than to
> manipulate the text field? This would appear the same when you look at the
> tiddler. A viewtemplate solution would be simpler but the text would e.g
> not register in standard "search"... (which might be a good thing if it is
> a recurring text.)
>
> <:-)
>
> --
> 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/6a1ad222-79a5-4ff3-90b2-174da334784bo%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/CAJCYWCsEA%3DeHRXqEzGuMr0dL-VDPM_mCstovur67XAOHBBV%2BiA%40mail.gmail.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

Tony

Many thanks for responding to my query.

This is what i am trying to achieve. I have some data in a database and,
with Eric's help, I have transferred that data via JSON into a number of
tiddlers with data in a number of fields. To see the data I have to add the
same text to the body of every tiddler so I would like to add that text to
the new tiddlers on import. Possibly a different solution to the problem
that I outlined in my first email.

So in answer to your questions:
1. The body is empty so it does not matter
2. Yes, common to all.

I hope this helps and many thanks.

Rob

On Tue, 30 Jun 2020 at 02:38, TW Tones  wrote:

> Robert,
>
>
>- Do you want this to be appended, pre-pended or overwrite the text?
>- Is this text common for all, or do you wish to edit it before adding
>to each tiddler?
>
>
> We can make a full solution, but the first thing is to keep the list of
> tiddlers imported. After import if you rename $:/import to another name you
> can keep the list of tiddlers.
>
> I will come back soon with a way to extract those titles to use for
> further transformation.
>
> Regards
> Tony
>
>
> On Tuesday, June 30, 2020 at 5:57:45 AM UTC+10, Robert Jopling wrote:
>>
>> How do you add new text to the body of all newly imported tiddlers?
>
> --
> 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/2ca36dab-f976-4cf1-bf7f-dea891e3a7c8o%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/CAJCYWCuJAEUkcX7JBtegVuQDXPicbbq6GCx_5MYqhxHfcpYv_Q%40mail.gmail.com.

[tw5] Re: TiddlyWiki Hangout #107 with Matt Lauber and Reece Shaw

2020-06-30 Thread Dragon Cotterill

I have built a TW explaining all the rules, characters, skill and 
attributes for playing my MUD game. The game itself is not finished, it's 
still very much a work-in-progress, but the wiki makes organising it so 
much easier. Which is the point of any TW... it's versatile and can be used 
for pretty much anything.

-- 
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/1d79779c-7f63-4620-a326-c6feaba0o%40googlegroups.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

@Robert, is there any other commonality - besides that they're all imported 
- among the relevant tiddlers? For example, do they happen to be tagged in 
a specific way that is unique for all tiddlers where you want this text to 
show, or are they all prefixed in some way or do they all have some shared 
uniquely titled field?

And will you use the appearing text other than viewing it? Should it be 
findable in regular search? Will you transclude it elsewhere?

IF your reply is that "they all share the common trait X" and "it doesn't 
have to be findable in regular search" then the problem is very simple to 
solve. It is solvable regardless, but IF those criteria are met then it's 
really simple. Just sayin.

<:-)

-- 
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/ddcfe249-cfef-4dd5-8cf4-97d2cff30870o%40googlegroups.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

In response

1. Yes they are all tagged the same
2. Yes they would need to be findable in a regular search

I hope this helps

Rob

On Tue, 30 Jun 2020 at 10:57, Mat  wrote:

> @Robert, is there any other commonality - besides that they're all
> imported - among the relevant tiddlers? For example, do they happen to be
> tagged in a specific way that is unique for all tiddlers where you want
> this text to show, or are they all prefixed in some way or do they all have
> some shared uniquely titled field?
>
> And will you use the appearing text other than viewing it? Should it be
> findable in regular search? Will you transclude it elsewhere?
>
> IF your reply is that "they all share the common trait X" and "it doesn't
> have to be findable in regular search" then the problem is very simple to
> solve. It is solvable regardless, but IF those criteria are met then it's
> really simple. Just sayin.
>
> <:-)
>
> --
> 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/ddcfe249-cfef-4dd5-8cf4-97d2cff30870o%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/CAJCYWCu574vkaimJg%3DF5DpVWMX5Hqi6FcKgdkTgPQu6H933%2ByQ%40mail.gmail.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

OK, modify this and see if it works:

\define append()
$(text)$

My added text

*one
*two
\end

<$button>
clicketyclick
<$list filter="[tag[HelloThere]]">
<$set name=text value={{{ [{!!title}get[text]] }}}>
<$action-setfield $tiddler={{!!title}} text=<> />




<:-)

-- 
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/f7bfa35e-8c29-44d3-bce9-7163b15f4161o%40googlegroups.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

Thanks Mat. Really appreciate it.

Will give it a go and let you know how i get on

Cheers

Rob

On Tue, 30 Jun 2020 at 12:49, Mat  wrote:

> OK, modify this and see if it works:
>
> \define append()
> $(text)$
>
> My added text
>
> *one
> *two
> \end
>
> <$button>
> clicketyclick
> <$list filter="[tag[HelloThere]]">
> <$set name=text value={{{ [{!!title}get[text]] }}}>
> <$action-setfield $tiddler={{!!title}} text=<> />
> 
> 
> 
>
> <:-)
>
> --
> 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/f7bfa35e-8c29-44d3-bce9-7163b15f4161o%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/CAJCYWCtxgBaiYsApqU2wbQr1_zMhHrHRcN_tyETQcvg6aQWp4w%40mail.gmail.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

A view template to support viewing your tiddlers should be all that's needed.

If the data is not private can you share it in a private reply? There are 
plenty of ways to automate this without appending anything.

Regards
Tony

-- 
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/1a27a652-7e96-473b-910e-8aba1c93c810o%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

The dynaview, as I understand it, prevents portion of the page to which you 
have not yet scrolled from rendering. This appeared to work, as you could 
tell because when you paged down there would be a pause before the page 
became visible. But it didn't seem to help performance. The dynaview 
version is still online, btw.

For that matter, I found the epub sample to be fairly slow, and it's only 
an excerpt from the book. It would have been interesting to see what the 
entire book was like, but I was unwilling to sign up for an account to 
purchase a public domain book that I've already read.

As an actual user of ebooks, I'm not sure the epub fulfils users needs. The 
epub is impressive, but probably not worth the overhead. I regularly read a 
huge book on TW without difficulty.  What the world really needs is a 
format with some sort of block-chain registry built in so that you can 
share and exchange commercial ebooks just like you can real books. In any 
event, people don't avoid reading because they need better formatting, 
people avoid reading because they're doing other things. And reading isn't 
even cheaper. A subscription to netflix will costs you less than a 
subscription to Kindle unlimited! You can binge watch the entire HP series 
in a single day, and save weeks of reading! \s

Thanks!

On Tuesday, June 30, 2020 at 1:30:20 AM UTC-7, TiddlyTweeter wrote:
>
>
> Mark S. wrote:
>>
>>  I probably won't be pursuing the dynaview option, since that didn't seem 
>> to improve performance.
>>
>>
>> As a reminder, the NW file can be found at:
>>
>>
>> https://marxsal.github.io/various/notowritey.html
>>
>  
>
> Ciao Mark
>
> Regarding performance and Dynaview---looking at the eBook version of 
> TW---seems to indicate its optimal for fully prepped, pre-ordered Tiddlers.
> I don't fully understand how it works yet, especially its "chunkology". 
> Xavier 
> helpfully commented this though ...
>
>  Xavier wrote:
>>
>> Hi TT,
>>
>> In order to fulfil some of the user interface requirements, like keeping 
>> track of the current reading location or creating annotations anywhere 
>> inside the text, Jeremy introduced Dynaview, then Dynannotate.  In the 
>> context of ePub reading, Dynaview's aim is to reveal on demand the little 
>> chunks that have been produced at ePub parse time, along with their 
>> possible annotations. Once you have this collection of chunks (aka 
>> tiddlers), the performance, while still subject to optimisation, is not 
>> much of a worry: these chunks are not tangled nor even weaved together 
>> through any complex cross-references system. At the time Dynaview comes 
>> into play, the list of chunks is already sorted, waiting to be displayed at 
>> reading pace. That's because ePub is a much poorer and linear format than 
>> TiddlyWiki of course. Fortunately, what can do more, can do less.
>>
>> By the way, being able to split any ePub into chunks is probably the 
>> hardest part of the project. Not only because choosing the chunks limits 
>> can be hard, but also because styles are often used very loosely by 
>> publishers : for instance, you may find paragraphs that are expressed as 
>> > style="font-size: 11pt;display: block;text-indent: 0pt;">The first 
>> paragraph of a section, as you have to guess. because the WYSIWYG 
>> tools that helped producing the ePub are generally misleading. I spare you 
>> the table and images issues :-)
>>
>> Cheers,
>> -- Xavier Cazin
>>
>>
>> On Sat, Jun 27, 2020 at 6:43 PM TiddlyTweeter  
>> wrote:
>>
>>> Xavier
>>>
>>> There is interest in it growing.
>>>
>>> I think the very good PERFORMANCE aspect is particularly interesting 
>>> since eBooks are large documents.
>>>
>>> Over in GG we did some tests with Dynaview but still hitting issues 
>>> which the eBook version does not have. I think better understanding the 
>>> eBook edition of TW will help a lot.
>>>
>>> Fingers crossed x
>>>
>>> Best wishes
>>> TT
>>>
>>> Xavier wrote:


 Not yet ready because of some pressing redesign, but it will eventually 
 be released as a normal 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/646b8812-bacf-4b9b-a4a2-a7075b813eado%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

I imagine the performance hit comes from the way that hiding fold levels 
occurs. The method I used to structure the document was meant to be highly 
portable. So you can port all the tiddlers and the tag tiddler to any 
tiddler, and view them correctly using the <> macro and nothing else. 
And any time you want to change the order of tiddlers, you can do so using 
the tag pill. But, perhaps, I focused too narrowly on an unimportant goal 
;-)

Possibly if there was a mode where fold-levels were turned off performance 
would improve. People could turn off folding in order to performance 
intensive activities and then turn it back on later for viewing.

Thanks!

On Tuesday, June 30, 2020 at 1:37:11 AM UTC-7, Saq Imtiaz wrote:
>
> @TT could you post the document with TiddlyToolmap imported? I have a 
> suspicion about where the performance hit on editing is coming from and 
> comparing side by side to Streams (in which I have Tiddly toolmap imported) 
> will be a quick way to check if I'm on the right track... Without having to 
> dive into code.

-- 
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/429cf417-5bdf-41a1-978c-02d9d340a210o%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

Mark & Saq

FWIW, I put on-line two example wiki. * First version works fine on my 
machine ... * Has 136 items * Half at Level 1 * Half at Level 2 ...

https://tidbits.wiki/noto/notoGIFFORD.html


* Second version was fine at First but once entries (splits) reached about 
300 it got sluggish. * ... And if you make too many items you may get 
browser freeze up.
* Has 498 items * 68 at Level 1 * 430 at Level 2. I stopped splitting 
further on Gifford's list just before MindMapping item. That is about half 
way through the list. Will take time to load ...

https://tidbits.wiki/noto/notoGIFFORD-2.html


Best wishes
TT

On Tuesday, 30 June 2020 15:09:21 UTC+2, Mark S. wrote:
>
> I imagine the performance hit comes from the way that hiding fold levels 
> occurs. The method I used to structure the document was meant to be highly 
> portable. So you can port all the tiddlers and the tag tiddler to any 
> tiddler, and view them correctly using the <> macro and nothing else. 
> And any time you want to change the order of tiddlers, you can do so using 
> the tag pill. But, perhaps, I focused too narrowly on an unimportant goal 
> ;-)
>
> Possibly if there was a mode where fold-levels were turned off performance 
> would improve. People could turn off folding in order to performance 
> intensive activities and then turn it back on later for viewing.
>
> Thanks!
>
> On Tuesday, June 30, 2020 at 1:37:11 AM UTC-7, Saq Imtiaz wrote:
>>
>> @TT could you post the document with TiddlyToolmap imported? I have a 
>> suspicion about where the performance hit on editing is coming from and 
>> comparing side by side to Streams (in which I have Tiddly toolmap imported) 
>> will be a quick way to check if I'm on the right track... Without having to 
>> dive into code.
>
>

-- 
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/31b9dcf8-8faa-48c0-96d7-ea472adeb127o%40googlegroups.com.

[tw5] Show part of field value

2020-06-30 Thread 'Jake' via TiddlyWiki

A little question. I wanted to sort projects by projectsize. But as I found 
out TW sorts them based on "text" logic, not "math" logic. So, if I want 
140.15 Gb be higher then 1.3 Gb, 2 Gb, 3 Gb and not between then I need to 
give them values 001.5 Gb, 002 Gb, 003 Gb. But I don't need those 
additional "zeros" to show in the appropriate part of the table. So, the 
question is how to "remove" those? I thought "removeprefix" should have 
worked, but if I try this:

<$text text={{{[{!!projectsize}removeprefix[00]]}}} />

and the field value has "00" in the beginning - everything is ok, but if it 
doesn't - I get empty result. I think I messed up with syntax somewhere, 
but I don't know where. I tried " +removeprefix", but that also didn't work 
out. Why doesn't it remove "zeroes" where they are and leave the rest as it 
is?

Plus if there is a single "0" before a number, e.g.: 015.43 Gb, i want to 
remove that 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/15c4cad7-db2b-4ac6-bbb1-d68e5526e65bo%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

2020-06-30 Thread David Gifford

That felt really weird to wake up and see something called NotoGifford...I 
expect royalties... :-)

On Tuesday, June 30, 2020 at 8:52:57 AM UTC-5 TiddlyTweeter wrote:

> Mark & Saq
>
> FWIW, I put on-line two example wiki. * First version works fine on my 
> machine ... * Has 136 items * Half at Level 1 * Half at Level 2 ...
>
> https://tidbits.wiki/noto/notoGIFFORD.html
>
>
> * Second version was fine at First but once entries (splits) reached about 
> 300 it got sluggish. * ... And if you make too many items you may get 
> browser freeze up.
> * Has 498 items * 68 at Level 1 * 430 at Level 2. I stopped splitting 
> further on Gifford's list just before MindMapping item. That is about half 
> way through the list. Will take time to load ...
>
> https://tidbits.wiki/noto/notoGIFFORD-2.html
>
>
> Best wishes
> TT
>
> On Tuesday, 30 June 2020 15:09:21 UTC+2, Mark S. wrote:
>>
>> I imagine the performance hit comes from the way that hiding fold levels 
>> occurs. The method I used to structure the document was meant to be highly 
>> portable. So you can port all the tiddlers and the tag tiddler to any 
>> tiddler, and view them correctly using the <> macro and nothing else. 
>> And any time you want to change the order of tiddlers, you can do so using 
>> the tag pill. But, perhaps, I focused too narrowly on an unimportant goal 
>> ;-)
>>
>> Possibly if there was a mode where fold-levels were turned off 
>> performance would improve. People could turn off folding in order to 
>> performance intensive activities and then turn it back on later for viewing.
>>
>> Thanks!
>>
>> On Tuesday, June 30, 2020 at 1:37:11 AM UTC-7, Saq Imtiaz wrote:
>>>
>>> @TT could you post the document with TiddlyToolmap imported? I have a 
>>> suspicion about where the performance hit on editing is coming from and 
>>> comparing side by side to Streams (in which I have Tiddly toolmap imported) 
>>> will be a quick way to check if I'm on the right track... Without having to 
>>> dive into code.
>>
>>

-- 
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/1c52298c-7d39-4fae-864f-b20321d91fe3n%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

2020-06-30 Thread Saq Imtiaz

A few quick observations. Note that I work on a very high end desktop that
makes it difficult to gauge performance accurately. For example, the second
Noto document from TT loads in a few seconds for me. However, comparing the
performance of Streams and Noto might be insightful.

These are averages of 3 runs in Streams and Noto with the tiddly toolmap
imported.

*NOTO*
*All top level items collapsed : *
mainRender 4733ms
mainRefresh 1157ms

*All items expanded: *
mainRender 5497ms
mainRefresh 1220ms

*STREAMS*
*All items collapsed*
mainRender: 222ms
mainRefresh 23ms

*All items expanded:*
mainRender: 2360ms
mainRefresh 184ms

What is interesting here is that Streams is much faster when the items are
collapsed. Note that streams has a lot of complexity added in the way of
filter runs for determining collapse state and drag and drag state, so I
would expect Noto to be as fast if not faster. So are the sub levels in
Noto rendered even if they are not shown?

Also crucially, the editing experience in Streams seems normal, not any
slower than with just one tiddler in the stream. Even if the faster
hardware is masking some of the problem, it shows that Noto is suffering
far more of a performance hit when editing.

I think it is important to distinguish between rendering performance, when
first opening the tiddler, versus refresh performance, when typing etc.

The slow performance in Noto reminds me of what happens when editing forces
a refresh of the containing tiddler or widget. This could be as simple as a
set or vars widget that is being refreshed due to a containing tiddler
being changed, which refreshes all the content inside those widgets. One
way to resolve this is to rework the logic for filters used to avoid such a
situation.

Another workaround is to edit in draft/temp tiddlers, and only save back to
the original tiddler when the user actually saves. This would mean that the
surrounding content would only refresh when you save the tiddler, as
opposed to on every key stroke. An intermediate step that might offer some
help is setting the throttle.refresh field on the tiddler being edited.

Note also that somewhere in tiddlytoolmap in one of the list items is the
code for a filter run, that will end up listing close to all the tiddlers
in the wiki!! I've removed this in my copy. I wouldn't be surprised if that
is exacerbating the problem.

I don't have the opportunity to look at the Noto code at the moment, but
hopefully this might lead you in the right direction with regards to
performance issues.
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/0e0c9350-2bb4-451e-9d70-228b4313c573o%40googlegroups.com.

[tw5] Re: Request for some feedback

Mat, 

These are some really useful points, thanks!

>
>- Am I the only one who doesn't get any scrolling when clicking the 
>links? (win/chrome)
>
>  What exactly do you mean by no scrolling?

>
>- I'm on desktop: It says "Show/hide sidebar" but it not obvious that 
>the whole upper part of the page, which is actually the whole default 
>viewport, is what is referred to.
>
> Yeah that's a good point. I don't really like the way the default theme 
handles the sidebar when it changes to the 'mobile' layout personally. I'd 
rather it cover the content instead of move to the top of the page. To fix 
it I'd have to install a better theme, then override the CSS again, or make 
my own theme entirely, which is something I am thinking of doing.

>
>- The first default tiddler is... unclear; why is the title (if it is 
>the title?) in brackets? Or maybe the big blue is the title? But there 
> seem 
>to be tag pills under both? 
>
> I agree there shouldn't be 2 titles, so I've fixed that. I've changed the 
buttons to be more distinguishable from tags.

>
>- If it is a public site, you should probably remove most of the 
>tiddler tool button showing only the close button (X) and page tools.
>
> Maybe, but then I find when I'm browsing other people's tiddlywiki's I 
like to look at the source of each page. I'll consider removing some of 
those buttons.

>
>- Blue fine links on black... IMO not good for visibility.
>
>  I've made the links brighter, I can go even further if needed.

>
>- Aesthetics: I understand the darkness is intentional but you do ask 
>for feedback so I'll just mention that I don't like these dark themes 
> other 
>than as "night" themes. Just my opinion.
>
> Yeah, some people certainly don't like them. I could add a switch, because 
I do have a light theme ready to go as well, not really sure how I would do 
that though. I chose the dark theme because there will be pictures and 
videos, and I think dark is much less distracting to that kind of content 
than light is, especially in a dark room.

Ash

On Tuesday, 30 June 2020 09:05:47 UTC+1, Mat wrote:
>
> Ash Rubigo wrote:
>>
>> It'd be great to get some feedback on on the aesthetic, layout, and 
>> navigability of my wiki http://www.ashrubigo.com/. 
>>
>
>
>- Am I the only one who doesn't get any scrolling when clicking the 
>links? (win/chrome)
>- I'm on desktop: It says "Show/hide sidebar" but it not obvious that 
>the whole upper part of the page, which is actually the whole default 
>viewport, is what is referred to.
>- The first default tiddler is... unclear; why is the title (if it is 
>the title?) in brackets? Or maybe the big blue is the title? But there 
> seem 
>to be tag pills under both? 
>- If it is a public site, you should probably remove most of the 
>tiddler tool button showing only the close button (X) and page tools.
>- Blue fine links on black... IMO not good for visibility.
>- Aesthetics: I understand the darkness is intentional but you do ask 
>for feedback so I'll just mention that I don't like these dark themes 
> other 
>than as "night" themes. Just my opinion.
>
>
> <:-)
>

-- 
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/2db8457e-c7c0-4ab5-992d-a84f9f4622eao%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

On Tuesday, June 30, 2020 at 7:37:00 AM UTC-7, Saq Imtiaz wrote:
>
> A few quick observations. Note that I work on a very high end desktop that 
> makes it difficult to gauge performance accurately. For example, the second 
> Noto document from TT loads in a few seconds for me. However, comparing the 
> performance of Streams and Noto might be insightful.
>
>
I need to get me one of those ;-)

 What is interesting here is that Streams is much faster when the items are 
> collapsed. Note that streams has a lot of complexity added in the way of 
> filter runs for determining collapse state and drag and drag state, so I 
> would expect Noto to be as fast if not faster. So are the sub levels in 
> Noto rendered even if they are not shown?
>

Hidden sub-sections are hidden by reveal widgets. When I check using 
inspect element, I don't see the hidden text. So I assume there's no 
over-head. Note that the times you got for folded vs non-folded were about 
5x greater.

Also crucially, the editing experience in Streams seems normal, not any 
> slower than with just one tiddler in the stream. Even if the faster 
> hardware is masking some of the problem, it shows that Noto is suffering 
> far more of a performance hit when editing.
>
> I think it is important to distinguish between rendering performance, when 
> first opening the tiddler, versus refresh performance, when typing etc. 
>
>  

> The slow performance in Noto reminds me of what happens when editing 
> forces a refresh of the containing tiddler or widget. This could be as 
> simple as a set or vars widget that is being refreshed due to a containing 
> tiddler being changed, which refreshes all the content inside those 
> widgets. One way to resolve this is to rework the logic for filters used to 
> avoid such a situation. 
>
>
As far as I know, nothing should be changing when typing into a tiddler. If 
TW is refreshing with every key stroke, then that is a problem. On Gifford 
#2, if you open a separate tiddler by itself, it also types slow. So even 
if I changed the logic to work with a temporary tiddler, it doesn't seem 
like there would be an improvement.

My goals when making the outliner were:

  * Use a simple data structure (tag and list) for portability
  * Use only core widgets and wikitext

My technique is:

  * Scan through the tagged list of items
  * Each item is either displayed or not displayed, depending on it's 
"hidden" status, or the "hidden" status of it's superior entries
  * To find the hidden status of each item, "climb" from the existing 
position up one position. 
  * If the prior tiddler is a superior level, and is hidden than hide
  * If the prior tiddler is not a superior level, continuing climbing
  * Repeat until you reach superior level "1".

I'm probably missing a step. But that's the overview. This backwards 
recursive logic is probably too much for large documents. It is possible 
that my two original goals are inconsistent with large-scale performance.

Hmm. Now I'm thinking that I need to restructure the logic so that it runs 
"forward", rather than climbing backwards.

Or buy a better machine.

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/13ebd78f-36c6-4fb8-b1a0-cd208456765ao%40googlegroups.com.

[tw5] Re: Show part of field value

On Tuesday, June 30, 2020 at 7:19:26 AM UTC-7, Jake wrote:
>
> A little question. I wanted to sort projects by projectsize. But as I 
> found out TW sorts them based on "text" logic, not "math" logic. So, if I 
> want 140.15 Gb be higher then 1.3 Gb, 2 Gb, 3 Gb and not between then I 
> need to give them values 001.5 Gb, 002 Gb, 003 Gb. But I don't need those 
> additional "zeros" to show in the appropriate part of the table. So, the 
> question is how to "remove" those? I thought "removeprefix" should have 
> worked, but if I try this:
> <$text text={{{[{!!projectsize}removeprefix[00]]}}} />
> and the field value has "00" in the beginning - everything is ok, but if 
> it doesn't - I get empty result. I think I messed up with syntax somewhere, 
> but I don't know where. I tried " +removeprefix", but that also didn't work 
> out. Why doesn't it remove "zeroes" where they are and leave the rest as it 
> is?
> Plus if there is a single "0" before a number, e.g.: 015.43 Gb, i want to 
> remove that as well.
>

removeprefix[foo] means almost the same thing as prefix[foo]: it matches 
items that actually have a prefix of "foo".
The difference is that removeprefix[] then also removes the "foo" prefix, 
leaving the remaining text behind.

For your stated use, where the !!projectsize  contains numbers that are 
"zero-padded", you can write something like this:
<$text text={{{ [{!!projectsize}removeprefix[00]] 
~[{!!projectsize}removeprefix[0]] ~[{!!projectsize}] }}} />
The leading ~ before each filter expression means "if the filter results so 
far are empty"

Thus, if the project size has leading "00", the first filter expression 
returns a result,
but if it has leading "0", the second filter expression returns a result, 
and
and if neither of those are matches, then it just gives the project size 
"as is".

However, there may be another way to address this.

Let's suppose you *don't* store any leading zeros in the projectsize field 
values.
Then, the problem is, as you originally noted, is that the sort[] filter 
does a *text* sort,
so that "1.3" and "140.15" both come before "2" and "3"

However, the nsort[] filter does a *numeric* sort, so that the results 
(using your example values)
would be ordered as: 1.3, 2, 3, and 140.15, as you intended.

One minor problem arises because your fields also include a suffix of " 
Gb", which makes the
field values "non-numeric" and, as written here: 
https://tiddlywiki.com/#nsort%20Operator

> "Non-numeric values are treated as having a higher value than any number" 

Which automatically defeats the numeric sorting and reverts to text sort 
order.

To address this, you would first have to omit that text from the 
projectsize field of each
project tiddler.  Then, to show a table of project titles and sizes, sorted 
numerically by projectsize,
you could write something like this (assuming you have tiddlers tagged with 
"project"):

  <$list filter="[tag[project]nsort[projectsize]]">
   {{!!title}}{{!!projectsize}}

Let me know how it goes...

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/62da9ab1-4a63-47cb-aa13-f149154572c8o%40googlegroups.com.

[tw5] Re: troublehooting: how to see macro variables

Ok, thank you 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/68a76e9c-51e4-4253-97fe-f531ec93bee6o%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

NotoWritey / Notoriety ha ha! I just got that (better late than never :D)

-- 
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/e564f221-76a9-4d00-95ba-04e955e9b008o%40googlegroups.com.

[tw5] Re: Request for some feedback

Ash Rubigo wrote:
>
>
>>- Am I the only one who doesn't get any scrolling when clicking the 
>>links? (win/chrome)
>>
>>  What exactly do you mean by no scrolling?
>

Literally that. I click a link, and seemingly nothing happens other than 
that my scrollbar handle lengthens or shortens, i.e the tiddler is opened 
but there is no navigation to it. I tried it now also on my android phone 
and same result - no scrolling to display the actual tiddler.

BTW, I assume it is intentional that the page shows as if on 
mobile/smallscreen also for laptop 14" screen.

<:-)

-- 
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/9c9af232-b373-4b7a-bc07-7fbbf323247co%40googlegroups.com.

[tw5] A way to add a timestamp to a tiddler every time it is opened/viewed in the story river?

2020-06-30 Thread si

I wonder if anything like this exists? I couldn't find anything with a 
google search, but you never know.

Reason: I thought it might be cool to generate a list of tiddlers that I 
haven't seen in a while.

-- 
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/0c422c1e-c93d-4fb9-878d-5cf61fd8acf3o%40googlegroups.com.

[tw5] Re: Show part of field value

2020-06-30 Thread 'Jake' via TiddlyWiki


>
> One minor problem arises because your fields also include a suffix of " 
> Gb", which makes the
> field values "non-numeric" and, as written here: 
> https://tiddlywiki.com/#nsort%20Operator
>
>> "Non-numeric values are treated as having a higher value than any number" 
>
> Which automatically defeats the numeric sorting and reverts to text sort 
> order.
>

No-no-no, I'm dumb, but not THAT dumb. :) Of course "Gb" was outside the 
field value. I wouldn't expect it to handle numeric+text field as numeric 
value. 


 However, the nsort[] filter does a *numeric* sort, so that the results 
> (using your example values)

would be ordered as: 1.3, 2, 3, and 140.15, as you intended.
>
>
> To address this, you would first have to omit that text from the 
> projectsize field of each
> project tiddler.  Then, to show a table of project titles and sizes, 
> sorted numerically by projectsize,
> you could write something like this (assuming you have tiddlers tagged 
> with "project"):
> 
>   <$list filter="[tag[project]nsort[projectsize]]">
>{{!!title}}{{!!projectsize}}
>
> 
>
>
Yeah, I had smth like this (though it was "sort" instead of "nsort" - silly 
me, and it worked fine untill I got to difference in digits :) )
<$list filter="[tag[project]has[gamesize]!nsort[gamesize]]">   
<$link/> (<$view field="projectsize" /> Gb) <$transclude 
tiddler={{!!rating-image}} />
 

 Let me know how it goes...


Yay! Both ways worked fine! Both the ~filter and nsort. Of course I'll 
stick with "nsort" as the most obvious choice. :) Though I didn't know 
about that "tilda" thingy and specificity of "removeprefix" operator 
mechanics - might come in handy later for other purpose.

Thanks a lot, Eric!

-- 
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/c7908bc7-62e6-4c0f-9477-360e01114693o%40googlegroups.com.

[tw5] Re: Request for some feedback

Mat,

Literally that. I click a link, and seemingly nothing happens other than 
> that my scrollbar handle lengthens or shortens, i.e the tiddler is opened 
> but there is no navigation to it. I tried it now also on my android phone 
> and same result - no scrolling to display the actual tiddler.
>

So I take it the sidebar is at the top of the screen for you. So if you 
click a link on the sidebar, the sidebar itself won't change, but if you 
scroll down the active tiddler *should *have changed. This is working for 
me on desktop and mobile, Chrome and Firefox.

If that isn't the case for you, then I'd struggle to visualise what 
precisely is happening. A screen capture of the problem would be great in 
finding out what's wrong.

BTW, I assume it is intentional that the page shows as if on 
> mobile/smallscreen also for laptop 14" screen.
>

Yes it is. I want the text to be nice and large for readability, which 
means that even non-mobile screens can be considered 'small', as far as the 
interface is concerned. The only difference is where the sidebar is, and 
like I said earlier, I would prefer it stayed a sidebar and overlapped the 
content. Something for me to work on.

Thanks!

Ash

On Tuesday, 30 June 2020 16:56:30 UTC+1, Mat wrote:
>
> Ash Rubigo wrote:
>>
>>
>>>- Am I the only one who doesn't get any scrolling when clicking the 
>>>links? (win/chrome)
>>>
>>>  What exactly do you mean by no scrolling?
>>
>
> Literally that. I click a link, and seemingly nothing happens other than 
> that my scrollbar handle lengthens or shortens, i.e the tiddler is opened 
> but there is no navigation to it. I tried it now also on my android phone 
> and same result - no scrolling to display the actual tiddler.
>
> BTW, I assume it is intentional that the page shows as if on 
> mobile/smallscreen also for laptop 14" screen.
>
> <:-)
>

-- 
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/c0853936-7574-4596-bf05-7fa0d15ff2bdo%40googlegroups.com.

Re: [tw5] Re: Family History wiki

2020-06-30 Thread Damon Pritchett

In an attempt to show all descendants of a person instead of just the 
children, I've written a macro to do the recursive listing. It works great 
except for one thing; on the very first pass or top level, the spouses 
aren't listed (the code is below the examples). It lists the descendants of 
the top level, but the part that says "with" doesn't happen. When I pick a 
level higher, then it does show. Here's a screenshot of one top level with 
no spouses:

Now here's the next level up:


As you can see, only the top level is missing the "with" and the spouse. 
I'm not exactly sure what I'm doing wrong, but it's so close.


\define each-other-level()
  
<$list filter=
"[titlekin:tags:to:1[]sortan[birth]!title]">

  <$link><$view field='caption'><$view field='title'/> -> born: <$macrocall $name="date-str" date={{!!birth}}/>
  
<$list filter=
"[titletagging[]sortan[birth]tags[]!title]">
  
with: <$link><$view field='caption'><$view field='title'/>
<$list filter=
"[titletagging[]limit[1]has[parents-marriage]]">
  -> married: <$macrocall $name="date-str" date={{!!parents-
marriage}}/>

<>
  

  


  
\end


\define descendants()
  <>
\end


On Monday, June 29, 2020 at 6:09:27 PM UTC-7, TW Tones wrote:
>
> Birthe,
>
> I do not think it racist, to be interested in ones family tree, just that 
> many racists will be interested in theirs, because they seek racial purity, 
> hence more likely to use the term "pedigree" as if their inheritance is 
> superior to another, which is the concept behind breading and animal 
> pedigree's. 
>
> Experience suggests however a truthful family tree often exposes to a 
> racists, that that have the blood of the races that they belittle, 
> somewhere in their tree, at least in a young (in modern terms) country like 
> Australia. 
>
> All racial purity is to some degree inbreeding.
>
> Our Australian indigenous people have being here more than 65,000 years, 
> as time has passed since colonisation, having aboriginal blood is 
> increasingly an honour rather than a curse. The Australian aboriginal 
> represents the longest continuous culture in human history. We even find 
> records of the rising sea levels after the ice age 12,000 years ago, How 
> old is Egypt or the Chinese civilisation?   
>
> Regards
> Tony
>
>
> On Tuesday, June 30, 2020 at 10:54:00 AM UTC+10, Birthe C wrote:
>>
>> TW Tones,
>>
>> It can be of historic interest. It is also a great hobby for many. 
>> I myself inherited at handwritten book, wrote by each generation - very 
>> old and delicate. It was always inherited by the oldest son. I was the 
>> first daughter to inherit it, due to being the one and only left.
>> The book also has the first written words by me. As a small child, not 
>> knowing how to write or spell, I got my grandmother to show me, how to 
>> write the name of the brother I should have had, but that died before i was 
>> born. I thought it wrong he never went into the bookand wrote it very 
>> ugly.
>>
>> It must have been of interest to somebody, because it was stolen shortly 
>> after I inherited it- by one of the guests at the funeralthat tells 
>> more about people that the book did. I do not know why you think racist? 
>> You never know what you will find it your tree! 
>> You should know that from the use you mentioned in dog breading.
>>
>> Birthe
>>
>> tirsdag den 30. juni 2020 kl. 02.28.04 UTC+2 skrev TW Tones:
>>>
>>> Damon,
>>>
>>> Just another name for a genealogical tree really. I am familiar with it 
>>> from dog breeding. It depends on how one values ones genetic tree, I 
>>> suspect racists value it more than others ;)
>>>
>>> Regards
>>> Tony
>>>
>>>

-- 
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/422c7f11-247b-476c-a1d8-0d4dca6958d3o%40googlegroups.com.

[tw5] IDEA: extend [trim[]] filter operator

Hi all,

In a discussion earlier today (
https://groups.google.com/forum/#!topic/tiddlywiki/M8PFeakbp6U), there was 
a "problem" caused by the use of [removeprefix[...]].
The OP had assumed that this just removed the specified leading text from 
the items being filtered when, in fact, it also does the matching action of 
[prefix[...]]

However, it would be helpful if there was a filter actually did *just* 
remove leading (or trailing) text,
without regard to any matching.  One example of a filter that does this 
kind of non-matching action
is "[trim[]]" (introduced in 5.1.20), which removes leading/trailing 
*whitespace* from the input items,
but doesn't have any effect on items that don't have leading/trailing 
whitespace.  Thus, a filter containing this:

[[  foobar ]] [[mumble]] [[gronk snork  ]] [[  frotz]] +[trim[]]
becomes just
[[foobar]] [[mumble]] [[gronk snork]] [[frotz]]

My thought is this... we could extend the current *[trim[]]* syntax to only 
remove leading
OR trailing whitespace by adding a suffix to the operator:

*[trim:prefix[]]* would remove only leading whitespace
*[trim:suffix[]]* would remove only trailing whitespace

and enable removing of other leading/trailing text values, not just 
whitespace, by adding a parameter to the operator:

*[trim[foo]]* would remove leading/trailing text "foo"
*[trim:prefix[foo]]* would remove only leading text "foo"
*[trim:suffix[foo]]* would remove only trailing text "foo"

The parameter would also be able to handle repeating text.  Thus, you could 
trim a list of "zero-padded" numbers, like this:
[[123]] [[0.004]] [[0007.0]] [[89]] [[27.00]] [[05.00]] +[trim[0]trim:
suffix[.]]
would produce this result:
[[123]] [[.004]] [[7]] [[89]] [[27]] [[5]]

and something like:
[[  this is some text...  ]] +[trim[ ]trim[.]]
would produce this result
[[this is some text]]

I can think of several instances where such a filter could have saved me 
untold amount of
effort in handling variations on field values entered by users via an 
$edit-text widget

Your thoughts?

-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/7d1ae8cb-fdf3-4cff-99a2-7c15224a7299o%40googlegroups.com.

[tw5] Re: IDEA: extend [trim[]] filter operator

Good idea but/and I think this request has overlapping use; 
Extend removeprefix op with :suffix to make less greedy #4520 


Do please comment there if you agree 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/a4652ca2-6952-4229-bcf9-ede7c3276831o%40googlegroups.com.

[tw5] Re: Request for some feedback

Ash Rubigo wrote:
>
>
> So I take it the sidebar is at the top of the screen for you. So if you 
> click a link on the sidebar, the sidebar itself won't change, but if you 
> scroll down the active tiddler *should *have changed. This is working for 
> me on desktop and mobile, Chrome and Firefox.
>

Yes, if I *manually *scroll down the tiddler has changed, yes. But is it OK 
to expect the user to have to *manually *scroll down in order to see the 
tiddler whose title link he clicked, rather than having the system 
automatically scroll to 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/7fb55008-0479-4b8c-ad7a-14cb28024be8o%40googlegroups.com.

[tw5] Re: Request for some feedback

Ah okay, that makes things clearer. Yeah, that's just default TiddlyWiki 
behaviour. I completely agree the mobile version of the sidebar needs work, 
and I think I'll make it a priority, it's just confusing and awkward as is. 
Like I said before, changing it so it instead overlaps the content makes 
more sense to me, which averts all the problems. I don't think it's a 
simple fix though, because to my understanding it involves some JavaScript. 
I'll have to look at downloading a theme, then reworking it to my liking.

I think the wiki is looking a bit sharper than it was. I'm definitely still 
open to more feedback, as it can always be better. *Thanks to everyone for 
the responses so far!*

Ash

On Tuesday, 30 June 2020 18:35:41 UTC+1, Mat wrote:
>
> Ash Rubigo wrote:
>>
>>
>> So I take it the sidebar is at the top of the screen for you. So if you 
>> click a link on the sidebar, the sidebar itself won't change, but if you 
>> scroll down the active tiddler *should *have changed. This is working 
>> for me on desktop and mobile, Chrome and Firefox.
>>
>
> Yes, if I *manually *scroll down the tiddler has changed, yes. But is it 
> OK to expect the user to have to *manually *scroll down in order to see 
> the tiddler whose title link he clicked, rather than having the system 
> automatically scroll to 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/981bced7-e890-44e1-8ac0-da35aec9618bo%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

Ciao Mark & Saq

Though  I don't grasp coding complexities  I can comment from observation 
...

> On Tuesday, June 30, 2020 at 7:37:00 AM UTC-7, Saq Imtiaz wrote:
>>
>> The slow performance in Noto reminds me of what happens when editing 
>> forces a refresh of the containing tiddler or widget. This could be as 
>> simple as a set or vars widget that is being refreshed due to a containing 
>> tiddler being changed, which refreshes all the content inside those 
>> widgets. One way to resolve this is to rework the logic for filters used to 
>> avoid such a situation. 
>
>
On Tuesday, 30 June 2020 17:20:13 UTC+2, Mark S. wrote: 

> As far as I know, nothing should be changing when typing into a tiddler. 
> If TW is refreshing with every key stroke, then that is a problem. On 
> Gifford #2, if you open a separate tiddler by itself, it also types slow. 
> So even if I changed the logic to work with a temporary tiddler, it doesn't 
> seem like there would be an improvement.
>

Right. *Everything* is slow. Actual edit, either in Noto instance or to the 
same Tiddler separately whilst Noto is open seem much the same. Actual edit 
is slowed but its when *saving the open instance* in Noto or *changing 
folding* it gets really slowed (the list field update and hiding level 
setting? Yes?) Beyond a certain point the browser freezes for me.

On initial loading, BTW, opening the Same Tiddlers without Noto using just 
the $:/StoryList is much the same as a Noto instance. Load is same. Edit is 
much quicker.

My goals when making the outliner were:
>
>   * Use a simple data structure (tag and list) for portability
>   * Use only core widgets and wikitext
>

Right. From my point of view its a nice approach. Why? Because with careful 
"stem name choice" you can have human readable titling you can use many 
ways.
That matters for many of my cases. For instance its a snap in Noto to sling 
in a chapter of a novel and get correctly numbered paragraphs that directly
correspond to source material ... so ... titling

"GE Chapter IV" is split to ...

"GE Chapter IV 1" thru to "GE Chapter IV 49"

Each number being a paragraph number.

That seems very viable so long as your Noto instances are not holding 
zillions of items.

In a previous example I gave of a 105 page (105 Tiddler) full length 
screenplay the (in non Outliner) very worked well. 
I think the Outliner would manage just as well at that number of items too.

The Gifford-Test-2 was interesting because performance at First was fine. 
But as absolute numbers increased so performance started dropping 
*exponentially*.

To me that means Noto is currently best with projects whose total number of 
"chunks" per Noto instance doesn't get too high.
In practice I'm confident I can use it to deal with books by having an 
instance per chapter and so on. Sensible chunking.

David Gifford's list is challenging as I can't really see a way to chunk it 
down. If you chunked to sections, Noto each, its kinda defeating the 
objective of an umbrella outliner.

FWIW, the eBook edition of TW uses "strategic chunking" I think. I think 
that is one of the reasons it appears performative.

... backwards recursive logic is probably too much for large documents. It 
> is possible that my two original goals are inconsistent with large-scale 
> performance.
>
> Hmm. Now I'm thinking that I need to restructure the logic so that it runs 
> "forward", rather than climbing backwards.
>

IMO, for actual things I make, I think it will often be fine as it is. And 
large stuff needs thinking about anyway according to the specific logic of 
the media concerned.

It would be great if Noto performance could be improved with higher 
numbers, but, for me its basic logic is very neat, useable & human readable 
with a big range of uses.

Best wishes
TT

-- 
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/d52bab1a-a394-4b7b-8162-5c6fca15ed42o%40googlegroups.com.

[tw5] Re: Request for some feedback

Ash Rubigo wrote:
>
> Ah okay, that makes things clearer. Yeah, that's just default TiddlyWiki 
> behaviour. 
>

No, that's not default TW behaviour: If I go to tiddlywiki.com on my 
android phone and click any of the sidebar links, then there's automatic 
scroll to that tiddler.

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/cde93644-497c-41e1-bcf3-d9ed66fb384co%40googlegroups.com.

[tw5] Re: IDEA: extend [trim[]] filter operator

On Tuesday, June 30, 2020 at 10:30:05 AM UTC-7, Mat wrote:
>
> Good idea but/and I think this request has overlapping use; 
> Extend removeprefix op with :suffix to make less greedy #4520 
> 
>

That  issue is very similar to my proposal, but would mean adding ":lazy" 
handling to both removeprefix[] and removesuffix[], and wouldn't address 
the "repeating character" functionality in my proposal.

I think that extending the trim[] operator makes more sense semantically, 
in that it already functions as a "modify but don't remove" operation and 
my proposal merely extends this to allow greater specificity without 
changing the overall purpose.

-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/dcb08682-ab24-4a38-beeb-de6f562a2c9bo%40googlegroups.com.

Re: [tw5] Re: Family History wiki

2020-06-30 Thread Damon Pritchett

Hmm. Possibly. I'll have to think about how to do that.

Is there something fundamentally wrong with my macro the way it is?

Damon

On Tuesday, June 30, 2020 at 12:06:59 PM UTC-7, Mat wrote:
>
> Maybe a workaround; could you introduce a "ghost" that is one level above 
> and that is not shown and whose non-appearing spouse is irrelevant if it 
> shows or not?
>
> <:-)
>

-- 
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/15516b78-a060-4822-b7b0-bf38a3be8a6fo%40googlegroups.com.

[tw5] Re: Request for some feedback

Huh, you're right, I have no idea how I've broken that. That's strange.

I realised making the sidebar always a sidebar was easier than I thought. 
Tell me what you think!

Ash

On Tuesday, 30 June 2020 19:37:24 UTC+1, Mat wrote:
>
> Ash Rubigo wrote:
>>
>> Ah okay, that makes things clearer. Yeah, that's just default TiddlyWiki 
>> behaviour. 
>>
>
> No, that's not default TW behaviour: If I go to tiddlywiki.com on my 
> android phone and click any of the sidebar links, then there's automatic 
> scroll to that tiddler.
>
> <:-)
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/09228b06-e9c9-46f7-852c-8af47c1c01a1o%40googlegroups.com.

[tw5] Re: Request for some feedback

Ash Rubigo wrote:
>
> I realised making the sidebar always a sidebar was easier than I thought. 
> Tell me what you think!
>

I guess it depends on your target audience. You indicated, apropos possibly 
keeping the tiddler tool buttons, that your audience is other TW users in 
which case a sidebar like that is probably OK. The first thing a fellow 
*tiddleur 
*would think is probably "OK, the sidebar is open" and think no further of 
it. But someone not initiated will probably find it confusing, at least on 
desktop. I mean, an intrusive sidebar is probably closed by default 
usually... If there are critical links that the user needs to see directly 
when visiting the site perhaps they should be in the topmost tiddler also? 
Just an idea, possibly a bad one ;-)

In the open sidebar there is, on my desktop screen, a horizontal scrollbar 
at bottom. But the sidebar shows fully and there is no scroll handle. My 
guess is you have something inside the popout that exceeds it by just a 
pixel or so, e.g a border.

<:-)

-- 
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/198f4923-182e-4d78-b45e-62ba75d5a6b6o%40googlegroups.com.

Re: [tw5] Re: Family History wiki

Maybe a workaround; could you introduce a "ghost" that is one level above 
and that is not shown and whose non-appearing spouse is irrelevant if it 
shows or not?

<:-)

-- 
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/a4d771bb-e6e6-45b3-b722-bc2406dc5a11o%40googlegroups.com.

[tw5] Re: Notowritey - Outliner/editor for TW

Ciao Mark

P.S. to last, is the populating of the "*reset*" field also a factor in 
performance?
Just wondering?

Best wishes
TT

-- 
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/2a420dd7-adeb-4f93-8096-fe8a0a29e534o%40googlegroups.com.

[tw5] Stroll - Position of backlink text


Hi there

I have just downloaded an empty version of Stroll and have been trying it 
out. Its functionality is right for recording questions and their answers.

What I have found is that the back link text in the child tiddler is above 
the horizintal line, whereas the forward link text in the parent tiddler is 
below the horizontal line.

Can anyone explain why this?

Rob

-- 
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/a41ede1c-3ca3-4599-ada1-07d0fc5495c1o%40googlegroups.com.

[tw5] Re: Presenting: GRAPHS - pies, bars, scatter and whatever turns you on

Is there a way to get a line graph with super simple input like this:

<>


I tried that on your site, but it doesn't render anything

Ultimately I want to input a string of values generated by a list widget 
like this:
<$list 
filter="[addsuffix[.VAShi]fields[]regexp[\d\d\d\d-\d\d-\d\d]]" 
variable="field">
<$text text={{{ =[addsuffix[.VAShi]get] 
=[addsuffix[.VASlo]get] 
=[addsuffix[.disAbil]get] +[sum[]] }}}/>



so ultimately this to produce a graph:
<>


But obviously I'm not grasping something about how the plugin works.


-- 
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/918e70de-a676-4c72-abac-8d4f6f6c258bo%40googlegroups.com.

[tw5] Re: Family History wiki

2020-06-30 Thread Damon Pritchett

As I was thinking about what Mat had suggested, I had a thought. I realized 
that I had to reverse the order of the list filters and all is well. Here's 
the new code.

\define each-other-level()
  
<$list filter=
"[titletagging[]sortan[birth]tags[]!title]">
  
with: <$link><$view field='caption'><$view field='title'/>
<$list filter=
"[titletagging[]limit[1]has[parents-marriage]]">
  -> married: <$macrocall $name="date-str" date={{!!parents-marriage
}}/>
 

  <$list 
filter="[titlekin:tags:to:1[]sortan[birth]!title]">

  <$link><$view field='caption'><$view field='title'/> -> born: <$macrocall $name="date-str" date={{!!birth}}/>
  <>

  

  

  
\end


\define descendants()
  <>
\end




On Saturday, June 27, 2020 at 4:27:54 PM UTC-7, Damon Pritchett wrote:
>
> All,
>
> I've spent the last few days working on a new wiki for use with my family 
> history. I'm going to use it, not as a substitute for my genealogy program, 
> but as a supplement to keep track of documentation and such. In so doing, 
> I've managed to figure out a nice way of using tidgraph to generate my 
> pedigree chart and I've written a "children of" using nested list widgets. 
> I have tiddlers for each person with that person's parents as tags. With 
> tidgraph, I was able to get the desired behavior by using mode="tags[]" 
> instead of tagging which is the default. Tidgraph is a wonderful plugin and 
> it's too bad that it doesn't seem to be supported any longer. I'm still 
> learning Javascript, so am a long way from making any changes to it myself.
>
> I've created a ViewTemplate that I've included here:
> \import [title]
>
> <$list filter="[all[current]search:description[People]]">
>
> 
>
>
> <$tidgraph start=<> mode="tags[]sort[sex]reverse[]" 
> maxdepth="2" nocollapse />
>
> <$list filter="[all[current]has:field[birth]] 
> [all[current]has:field[death]]">
> 
>   Birth / Death:
>   
> Birth
> <$macrocall $name="date-str" date={{!!birth}}/>
> <>
>   
>   
> Death
> <$macrocall $name="date-str" date={{!!death}}/>
> <>
>   
> 
> 
>
> <$list filter="[all[current]]" variable="Parent">
>
> <$list filter="[all[current]tagging[]search:description[People]limit[1]]" 
> variable=null>
>
> 
>   Children of <>:
>   
> <$list 
> filter="[titletagging[]sortan[birth]tags[]!title]">
>   with: <$link><$view field='caption'><$view 
> field='title'/>
> <$list 
> filter="[titletagging[]limit[1]has[parents-marriage]]">
>   -> married: <$macrocall $name="date-str" 
> date={{!!parents-marriage}}/>
> 
> 
>   <$list filter="[titletagging[]sortan[birth]]">
> <$link><$view field='caption'><$view 
> field='title'/> -> born: <$macrocall $name="date-str" 
> date={{!!birth}}/>
>   
> 
>   
> 
>   
> 
>
> 
>
> 
>
> <$list 
> filter="[all[current]backlinks[]!search:description[People]!is[missing]limit[1]]"
>  
> variable=null>
>
> < filter:"[titlebacklinks[]!search:description[People]]" 
> fields:"tbl-expand record-date description title" sortOp:sortan 
> stateTiddler:"recordsearch" class:"highlight1" editButton:no 
> caption:"''Mentioned or connected with the following records:''">>
>
> 
>
>
> 
>
> 
>
>
> The result is this:
>
>
>
> I'm suing the class "list-tree" which has been around for quite a while 
> and created by Mat. There's also a dynamic table called out from the Shiraz 
> plugin that I use to show any documents that the person is listed in.
>
> This all works just how I want it to work, but being that my skills at 
> Tiddlywiki are still forming, I'm wondering if there might be a more 
> efficient or effective way of doing the same thing. I am definitely open to 
> any better ways of doing things.
>
> I'm also thinking of expanding the "children of" code to a recursive macro 
> to get multiple generations, but I don't know exactly how to proceed down 
> that path. Any suggestions would be highly appreciated.
>
> Feel free to use this code if you think you'd find it useful. I only ask 
> that, if you make any improvements or additions, that you let me know so I 
> might incorporate those.
>
> Thanks,
>
> Damon
>
>
>
>
>
>

-- 
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/ab951224-baa1-4468-8b17-805fdffde87fo%40googlegroups.com.

[tw5] Re: Request for some feedback

>
> You indicated that your audience is other TW users
>

Actually I aim to have a large amount of traffic from all over the 
Internet, primarily Reddit. This wiki is the hub for the projects I work 
on, which is why I'm trying refine the style before promoting it to the 
general public. Reddit in particular can be *brutal *with their feedback, 
they are going to absolutely tear it apart. It is a wiki, a format that 
isn't necessarily the most appealing, but I'm not under the illusion it 
will be the place everyone goes. Unlike independent posts, the great thing 
about a wiki is that all the content can reference each other using links, 
which is great for fans wanting to delve deeper. I suspect only images and 
videos can be truly mainstream, which is what I aim to share directly, and 
that is what the wiki needs *a lot* of, pictures pictures pictures.

I mean, an intrusive sidebar is probably closed by default usually... If 
> there are critical links that the user needs to see directly when visiting 
> the site perhaps they should be in the topmost tiddler also? Just an idea, 
> possibly a bad one ;-)
>

Yeah, I agree that it should probably be closed by default. Just a matter 
of remembering to save with the sidebar closed. Fixed.

My philosophy is already that all pages should be reachable by following 
links from the index, plus there is a persistent button with text for the 
sidebar, so I think people shouldn't have much of a problem finding the 
sidebar.

In the open sidebar there is, on my desktop screen, a horizontal scrollbar 
> at bottom. But the sidebar shows fully and there is no scroll handle. My 
> guess is you have something inside the popout that exceeds it by just a 
> pixel or so, e.g a border.
>

Oh, I didn't notice that before, fixed, thanks!

Ash

On Tuesday, 30 June 2020 20:56:35 UTC+1, Mat wrote:
>
> Ash Rubigo wrote:
>>
>> I realised making the sidebar always a sidebar was easier than I thought. 
>> Tell me what you think!
>>
>
> I guess it depends on your target audience. You indicated, apropos 
> possibly keeping the tiddler tool buttons, that your audience is other TW 
> users in which case a sidebar like that is probably OK. The first thing a 
> fellow *tiddleur *would think is probably "OK, the sidebar is open" and 
> think no further of it. But someone not initiated will probably find it 
> confusing, at least on desktop. I mean, an intrusive sidebar is probably 
> closed by default usually... If there are critical links that the user 
> needs to see directly when visiting the site perhaps they should be in the 
> topmost tiddler also? Just an idea, possibly a bad one ;-)
>
> In the open sidebar there is, on my desktop screen, a horizontal scrollbar 
> at bottom. But the sidebar shows fully and there is no scroll handle. My 
> guess is you have something inside the popout that exceeds it by just a 
> pixel or so, e.g a border.
>
> <:-)
>

-- 
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/eec6d8d6-1b67-4f31-afc7-65bb2cb934edo%40googlegroups.com.

Re: [tw5] Re: Adding text to newly imported tiddlers

Hi Mat

That worked a treat. Thank you so much.

Rob

On Tue, 30 Jun 2020 at 12:49, Mat  wrote:

> OK, modify this and see if it works:
>
> \define append()
> $(text)$
>
> My added text
>
> *one
> *two
> \end
>
> <$button>
> clicketyclick
> <$list filter="[tag[HelloThere]]">
> <$set name=text value={{{ [{!!title}get[text]] }}}>
> <$action-setfield $tiddler={{!!title}} text=<> />
> 
> 
> 
>
> <:-)
>
> --
> 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/f7bfa35e-8c29-44d3-bce9-7163b15f4161o%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/CAJCYWCtwyergm1%3DdWdtXO11pPgAChkMac4zkWPoNMh5sCsVfdA%40mail.gmail.com.

[tw5] Re: Request for some feedback

Mat,

I found out why clicking a link does not move the screen to the top of the 
tiddler. The problem is it does not work with the 'Zoomin' story view, 
because in $:/core/modules/storyviews/zoomin.js, line 115 is commented out:

//$tw.pageScroller.scrollIntoView(targetElement);

Uncommenting it brings back the behavious, but of course it requires 
overwriting a shadow tiddler, which is not so bad. I will note though, that 
this is a bit buggy. I don't know why yet, but this doesn't work when 
revisiting some pages that are already open. 

Fixed?

Ash

On Tuesday, 30 June 2020 22:32:19 UTC+1, Ash Rubigo wrote:
>
> You indicated that your audience is other TW users
>>
>  
> Actually I aim to have a large amount of traffic from all over the 
> Internet, primarily Reddit. This wiki is the hub for the projects I work 
> on, which is why I'm trying refine the style before promoting it to the 
> general public. Reddit in particular can be *brutal *with their feedback, 
> they are going to absolutely tear it apart. It is a wiki, a format that 
> isn't necessarily the most appealing, but I'm not under the illusion it 
> will be the place everyone goes. Unlike independent posts, the great thing 
> about a wiki is that all the content can reference each other using links, 
> which is great for fans wanting to delve deeper. I suspect only images and 
> videos can be truly mainstream, which is what I aim to share directly, and 
> that is what the wiki needs *a lot* of, pictures pictures pictures.
>
> I mean, an intrusive sidebar is probably closed by default usually... If 
>> there are critical links that the user needs to see directly when visiting 
>> the site perhaps they should be in the topmost tiddler also? Just an idea, 
>> possibly a bad one ;-)
>>
>  
> Yeah, I agree that it should probably be closed by default. Just a matter 
> of remembering to save with the sidebar closed. Fixed.
>
> My philosophy is already that all pages should be reachable by following 
> links from the index, plus there is a persistent button with text for the 
> sidebar, so I think people shouldn't have much of a problem finding the 
> sidebar.
>
> In the open sidebar there is, on my desktop screen, a horizontal scrollbar 
>> at bottom. But the sidebar shows fully and there is no scroll handle. My 
>> guess is you have something inside the popout that exceeds it by just a 
>> pixel or so, e.g a border.
>>
>
> Oh, I didn't notice that before, fixed, thanks!
>
> Ash
>
> On Tuesday, 30 June 2020 20:56:35 UTC+1, Mat wrote:
>>
>> Ash Rubigo wrote:
>>>
>>> I realised making the sidebar always a sidebar was easier than I 
>>> thought. Tell me what you think!
>>>
>>
>> I guess it depends on your target audience. You indicated, apropos 
>> possibly keeping the tiddler tool buttons, that your audience is other TW 
>> users in which case a sidebar like that is probably OK. The first thing a 
>> fellow *tiddleur *would think is probably "OK, the sidebar is open" and 
>> think no further of it. But someone not initiated will probably find it 
>> confusing, at least on desktop. I mean, an intrusive sidebar is probably 
>> closed by default usually... If there are critical links that the user 
>> needs to see directly when visiting the site perhaps they should be in the 
>> topmost tiddler also? Just an idea, possibly a bad one ;-)
>>
>> In the open sidebar there is, on my desktop screen, a horizontal 
>> scrollbar at bottom. But the sidebar shows fully and there is no scroll 
>> handle. My guess is you have something inside the popout that exceeds it by 
>> just a pixel or so, e.g a border.
>>
>> <:-)
>>
>

-- 
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/e6e0f22a-a379-4254-b809-057fbdf08749o%40googlegroups.com.

[tw5] Re: IDEA: extend [trim[]] filter operator

Eric,

I support your suggestion, in effect the trim default is "leading/trailing 
whitespace" but you can trim other values with this suggestion.

It is true more often that not removeprefix and removesuffix work for me, 
but they are long operators. If trim was the equivalent of remove prefix I 
would like it.

With the increasing use by many, of the tipple curly braces to construct 
parameters from filters (Variables and References) a "trim/simple" trim 
operator would make them much shorter and more readable.

>From memory unless remove prefix removes the prefix the title will not 
appear in the result. Trim on the other-hand trims if so, but passes all 
titles on. I understand that is what Mats "less Greedy" reference is about.

The existing split and join are related functions and I wonder if what you 
are suggesting is just a subset of some other operators that would be 
useful.

What you propose can sometimes be achieved with the split operator, but 
without a way to use white space rules. This is because the split text is 
removed from the output.

I have always felt it would be nice to have a replace operator replace 
"string with string" which also understood whitespace so you could say 
replace whitespace with / to generate a tiddler title, or replace "/" with 
white-space to extract subtitles. The Question is would this be the way to 
gain the functions you suggest?

Ideally you trim proposal AND others would be implemented. It feels we have 
almost all we need but not everything. Workarounds are not helpful if you 
need a TiddlyWiki degree to design them.

Regards
Tony

On Wednesday, July 1, 2020 at 4:42:58 AM UTC+10, Eric Shulman wrote:
>
> On Tuesday, June 30, 2020 at 10:30:05 AM UTC-7, Mat wrote:
>>
>> Good idea but/and I think this request has overlapping use; 
>> Extend removeprefix op with :suffix to make less greedy #4520 
>> 
>>
>
> That  issue is very similar to my proposal, but would mean adding ":lazy" 
> handling to both removeprefix[] and removesuffix[], and wouldn't address 
> the "repeating character" functionality in my proposal.
>
> I think that extending the trim[] operator makes more sense semantically, 
> in that it already functions as a "modify but don't remove" operation and 
> my proposal merely extends this to allow greater specificity without 
> changing the overall purpose.
>
> -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/65ce3f0c-9069-419b-8ad1-f99989a5d181o%40googlegroups.com.

[tw5] Re: Presenting: GRAPHS - pies, bars, scatter and whatever turns you on

Dave,

Can I suggest in future posting a new topic even if you provide the link to 
the old thread. 

There is a danger the old thread you raised from the dead has being 
superseded, and your reactivating the old one will cause problems.

Thanks
Tony

On Wednesday, July 1, 2020 at 6:54:52 AM UTC+10, Dave Parker wrote:
>
> Is there a way to get a line graph with super simple input like this:
>
> <>
>
>
> I tried that on your site, but it doesn't render anything
>
> Ultimately I want to input a string of values generated by a list widget 
> like this:
> <$list 
> filter="[addsuffix[.VAShi]fields[]regexp[\d\d\d\d-\d\d-\d\d]]"
>  
> variable="field">
> <$text text={{{ =[addsuffix[.VAShi]get] 
> =[addsuffix[.VASlo]get] 
> =[addsuffix[.disAbil]get] +[sum[]] }}}/>
> 
>
>
> so ultimately this to produce a graph:
> <>
>
>
> But obviously I'm not grasping something about how the plugin works.
>
>
>

-- 
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/cbfc8518-ea64-4c0b-95c6-32bbcbdb8693o%40googlegroups.com.

[tw5] Re: A way to add a timestamp to a tiddler every time it is opened/viewed in the story river?

Si,

If you provide the method by which when a tiddler is opened in the story 
river you could include an action that sets the clock by setting a 
date/time field to now.

By default there are multiple ways to open something in the story view, via 
contents, the result of a search, following an "in tiddler link", from the 
sidebar or a button using "to=".

I have prepared a way to execute additional actions on any standard button, 
but the navigation to open a tiddler does not have an easy way to trigger 
an action on every open, that I am aware of. Hackability of default 
triggers - "Buttons" #4272 

Jeremy was discussing a related hack-ability improvement  Implement more of 
TiddlyWiki's black box logic as customisable action strings #3967 

This could provide a method to add an action to all the navigation methods.

In the mean time, I recently discovered I could identify the last opened 
tiddler, in the story, what I call the "focused tiddler". Macro and sidebar 
attached.
The thing I like about this little macro is if you have a lot of tiddlers 
open, it is easy to return to the one with focus. I intend to add a button 
that focuses the current tiddler with a click if not.

I did see somewhere the ability to invoke an action when a tiddler changed. 
Perhaps you could find that and use this focus tiddlername.field to trigger 
what you want on the focus tiddler? I would however consider not allowing 
this for shadow/system tiddler or saving the time stamp for last read 
independently of the tiddler so it could operate on shadow tiddlers without 
editing them.

I also recently shared a read-date autonomous field which you have to stamp 
the tiddler with, that does not interfeat with the created/modified 
datestamps. 
https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/RP3RYc6Opxc

Regards
Tony

On Wednesday, July 1, 2020 at 2:02:30 AM UTC+10, si wrote:
>
> Does anyone know if anything like this exists? I couldn't find anything 
> with a google search, but you never know.
>
> Reason: I thought it might be cool to generate a list of tiddlers that I 
> haven't seen in a while.
>

-- 
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/273096f6-729a-4853-a090-23ba9dc0a343o%40googlegroups.com.

focus-tiddler.json
Description: application/json

[tw5] Re: Presenting: GRAPHS - pies, bars, scatter and whatever turns you on

Will do, thanks Tony

On Tuesday, June 30, 2020 at 7:19:10 PM UTC-6, TW Tones wrote:
>
> Dave,
>
> Can I suggest in future posting a new topic even if you provide the link 
> to the old thread. 
>
> There is a danger the old thread you raised from the dead has being 
> superseded, and your reactivating the old one will cause problems.
>
> Thanks
> Tony
>
> On Wednesday, July 1, 2020 at 6:54:52 AM UTC+10, Dave Parker wrote:
>>
>> Is there a way to get a line graph with super simple input like this:
>>
>> <>
>>
>>
>> I tried that on your site, but it doesn't render anything
>>
>> Ultimately I want to input a string of values generated by a list widget 
>> like this:
>> <$list 
>> filter="[addsuffix[.VAShi]fields[]regexp[\d\d\d\d-\d\d-\d\d]]"
>>  
>> variable="field">
>> <$text text={{{ =[addsuffix[.VAShi]get] 
>> =[addsuffix[.VASlo]get] 
>> =[addsuffix[.disAbil]get] +[sum[]] }}}/>
>> 
>>
>>
>> so ultimately this to produce a graph:
>> <>
>>
>>
>> But obviously I'm not grasping something about how the plugin works.
>>
>>
>>

-- 
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/bfb44ca7-38f8-4ae8-ade6-82b968ce4b5do%40googlegroups.com.

[tw5] Graphs.tiddlyspot.com question

Hi, this is a repeat question (Tony suggested it would be better to do a 
new thread rather than resurrect the old one)

The Graphs plugin is from here: http://graphs.tiddlyspot.com/

Here is the original thread: 
https://groups.google.com/forum/#!searchin/tiddlywiki/line$20graph%7Csort:date/tiddlywiki/LcjsToqhqmE/bmUaMeplBgAJ

And the question:
Is there a way to get a line graph with super simple input like this:

<>


I tried that on your site, but it doesn't render anything

Ultimately I want to input a string of values generated by a list widget 
like this:
<$list 
filter="[addsuffix[.VAShi]fields[]regexp[\d\d\d\d-\d\d-\d\d]]" 
variable="field">
<$text text={{{ =[addsuffix[.VAShi]get] 
=[addsuffix[.VASlo]get] 
=[addsuffix[.disAbil]get] +[sum[]] }}}/>



so ultimately this to produce a graph:
<>


But obviously I'm not grasping something about how the plugin works.


-- 
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/47a5ef39-413b-49a6-a13d-cabc5e2b2c08o%40googlegroups.com.

[tw5] Re: IDEA: extend [trim[]] filter operator

If we had a regular expression splitter (e.g. PR2963), then you could trim 
out prefix, suffix, or even create multiple splits from one input string. 
This would save having to create multiple filters for manipulating strings, 
especially since any new string operators would have names very similar to 
existing operators.

On Tuesday, June 30, 2020 at 10:21:37 AM UTC-7, Eric Shulman wrote:
>
> Hi all,
>
> In a discussion earlier today (
> https://groups.google.com/forum/#!topic/tiddlywiki/M8PFeakbp6U), there 
> was a "problem" caused by the use of [removeprefix[...]].
> The OP had assumed that this just removed the specified leading text from 
> the items being filtered when, in fact, it also does the matching action of 
> [prefix[...]]
>
> However, it would be helpful if there was a filter actually did *just* 
> remove leading (or trailing) text,
> without regard to any matching.  One example of a filter that does this 
> kind of non-matching action
> is "[trim[]]" (introduced in 5.1.20), which removes leading/trailing 
> *whitespace* from the input items,
> but doesn't have any effect on items that don't have leading/trailing 
> whitespace.  Thus, a filter containing this:
>
> [[  foobar ]] [[mumble]] [[gronk snork  ]] [[  frotz]] +[trim[]]
> becomes just
> [[foobar]] [[mumble]] [[gronk snork]] [[frotz]]
>
> My thought is this... we could extend the current *[trim[]]* syntax to 
> only remove leading
> OR trailing whitespace by adding a suffix to the operator:
>
> *[trim:prefix[]]* would remove only leading whitespace
> *[trim:suffix[]]* would remove only trailing whitespace
>
> and enable removing of other leading/trailing text values, not just 
> whitespace, by adding a parameter to the operator:
>
> *[trim[foo]]* would remove leading/trailing text "foo"
> *[trim:prefix[foo]]* would remove only leading text "foo"
> *[trim:suffix[foo]]* would remove only trailing text "foo"
>
> The parameter would also be able to handle repeating text.  Thus, you 
> could trim a list of "zero-padded" numbers, like this:
> [[123]] [[0.004]] [[0007.0]] [[89]] [[27.00]] [[05.00]] +[trim[0]trim:
> suffix[.]]
> would produce this result:
> [[123]] [[.004]] [[7]] [[89]] [[27]] [[5]]
>
> and something like:
> [[  this is some text...  ]] +[trim[ ]trim[.]]
> would produce this result
> [[this is some text]]
>
> I can think of several instances where such a filter could have saved me 
> untold amount of
> effort in handling variations on field values entered by users via an 
> $edit-text widget
>
> Your thoughts?
>
> -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/3e808675-aea8-46a1-97bd-2255be879f86o%40googlegroups.com.

[tw5] Re: IDEA: extend [trim[]] filter operator

Mark,

On Wednesday, July 1, 2020 at 1:07:06 PM UTC+10, Mark S. wrote:
>
> If we had a regular expression splitter (e.g. PR2963), then you could trim 
> out prefix, suffix, or even create multiple splits from one input string. 
> This would save having to create 
>

I agree that would be desirable but maintaining the simpler ones make sense 
as well, match, split, join, *trim* etc...

Regards
Tony

multiple filters for manipulating strings, especially since any new string 
> operators would have names very similar to existing operators.
>

-- 
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/4fc1ed57-b6d8-415a-9dbf-721b8b75b03bo%40googlegroups.com.

[tw5] Re: IDEA: extend [trim[]] filter operator