Re: [tw5] Re: Tip and Question - Inline edit of the text field

2021-05-29 Thread Mohammad Rahmani
Hi Tones

Okay, go with this and style as you like or split and add a toolbar button

For now

1. create a new tiddler tag it with *$:/tags/ViewTemplate*
2. put the below code inside it (text body)

\whitespace trim<$list
filter="[all[current]has:field[inline-edit]]"><$button
class="tc-btn-invisible">
{{$:/core/images/edit-button}}<$action-listops $field="inline-edit"
$subfilter="+[toggle[yes],[no]]" /><$list
filter="[all[current]inline-edit[yes]]">
   {{||$:/core/ui/EditTemplate/body}}



Test
1. Create a new tiddler
2. Add an inline-edit field
3. Save and see the button


I just changed the checkbox with a button! so you colorize it



Best wishes
Mohammad


On Sun, May 30, 2021 at 3:28 AM TW Tones  wrote:

> Mohammad,
>
> I would be happy to do so, however I want to solve the size and coloring
> of the checkbox in the view toolbar before doing so. To me the solution
> should be easy and simple so people can duplicate it for other. Of course I
> can do it via a button, and a display filter and do more.
>
> That is if I can get coloured checkboxes in the view toolbar I would be
> very happy.
>
> Tones
>
> On Saturday, 29 May 2021 at 23:11:55 UTC+10 Mohammad wrote:
>
>> On Sat, May 29, 2021 at 3:47 AM TW Tones  wrote:
>>
>>> Folks,
>>>
>>> Thanks for the feedback. I would like to emphasise a desire to provide a
>>> "very simple" solution for this commonly asked question.
>>>
>>> I concur with your comments and understand buttons vs checkbox, state
>>> tiddlers vs a flag inside the current tiddler. In this case however the
>>> tool is for editing the tiddler so I felt it can be kept simple by saving
>>> in the tiddler.
>>>
>>> The cancel button (delete the field) or do you mean "undo" mario? is
>>> that essential? I can see in a fuller solution it may be simple to store
>>> the text field before edit in a variable, and if undo is pressed restore it.
>>>
>>> I can see your various points captured in a plugin rather than this code
>>> solution, and I have done this for myself already. I want to refine the
>>> simple solution if possible.
>>>
>>> Mohammad,
>>>
>>> In other versions of this I have also had internal and external
>>> multiline text fields with notes working the same way. Some arising from
>>> discussions with you (perhaps if I have the right Mohammad perhaps you
>>> could sign off Mohammad Shiraz?)
>>>
>>
>> Why not distribute this as your first plugin? Put it on GitHub!
>> I think this can be used for live nores, sticky notes, ...
>>
>>
>>> All,
>>> The fact is if a simple css or html can help me add a tooltip to the
>>> checkbox and make it look more like a button, while in the toolbar this
>>> simple solution would be more complete.
>>>
>>> Tones
>>> On Saturday, 29 May 2021 at 02:10:18 UTC+10 Mohammad wrote:
>>>
 Interesting!

 This can be used to add comments at the end of tiddler!




 Best wishes
 Mohammad


 On Fri, May 28, 2021 at 12:21 PM TW Tones  wrote:

> OOps
>
> Also add a tiddler tagged $:/tags/ViewTemplate containing
> <$list filter="[all[current]inline-edit[yes]]">
>{{||$:/core/ui/EditTemplate/body}}
> 
>
> Regards
> Tones
> On Friday, 28 May 2021 at 17:48:02 UTC+10 TW Tones wrote:
>
>> Folks,
>>
>> Having worked with TiddlyWiki for some time, I have managed to get a
>> way to edit the text field without going into edit mode. I just went to
>> revisit this with a minimal case, and was surprised it worked, in part
>> because its easy to share.
>>
>> Place the following in a tiddler tagged $:/tags/ViewToolbar
>> \whitespace trim
>> <$list filter="[all[current]has:field[inline-edit]]">
>> <$checkbox field="inline-edit" checked="yes" unchecked="no"
>> default="no">
>> 
>>
>> Now any tiddler to which you add the field inline-edit will gain a
>> checkbox in the toolbar, allowing you to toggle editing the text in view
>> mode, without loosing focus in edit mode.
>>
>> Question
>> This button need a little more work, to comply with the tiddlywiki
>> standard, I will do that shortly. However my Question is since this is 
>> easy
>> to achieve does anyone know how to restyle the checkbox better for use in
>> the toolbar?
>>
>>- Make it larger and similar in size to existing buttons
>>- Provide a tooltip
>>- Perhaps alter the color
>>
>> I will then refine and republish here.
>>
>> Tones
>>
> --
> You received this message because you are subscribed to the Google
> Groups "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to tiddlywiki+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/19612ae1-c72d-43ac-9169-3e8bee22b2bbn%40googlegroups.com
> 

[tw5] Re: Tiddler Outline Viewer

2021-05-29 Thread Charlie Veniot
Arg, I hit post message instead of the attachment button.  The PDF:

On Sunday, May 30, 2021 at 12:11:24 AM UTC-3 Charlie Veniot wrote:

> G'day all,
>
> Following up on TiddlyWiki and "Code Folding" 
> :
>
> I'm sharing this unpolished code in case anybody else wants to play around 
> with it, or just study it for the fun of it.
>
> Please find attached a JSON file with related tiddlers (the "Tiddler 
> Outline Viewer" tiddler and a quick and dirty sample for testing purposes), 
> and a print-to-PDF to see what the "Tiddler Outline Viewer" looks like.
>
> As I play around with this thing, I'll eventually add some code inspection 
> (?) to help pinpoint missing widget/macro end tags and/or tag mismatches.
>
> At which point I may call this "Tiddler Outline Inspector" ?  Who knows...
>
> Cheers !
>
>
>
>

-- 
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/60df8062-6bfa-49ee-9d97-d4804630bba7n%40googlegroups.com.


Tiddler Outline Viewer.pdf
Description: Adobe PDF document


[tw5] Tiddler Outline Viewer

2021-05-29 Thread Charlie Veniot
G'day all,

Following up on TiddlyWiki and "Code Folding" 
:

I'm sharing this unpolished code in case anybody else wants to play around 
with it, or just study it for the fun of it.

Please find attached a JSON file with related tiddlers (the "Tiddler 
Outline Viewer" tiddler and a quick and dirty sample for testing purposes), 
and a print-to-PDF to see what the "Tiddler Outline Viewer" looks like.

As I play around with this thing, I'll eventually add some code inspection 
(?) to help pinpoint missing widget/macro end tags and/or tag mismatches.

At which point I may call this "Tiddler Outline Inspector" ?  Who knows...

Cheers !



-- 
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/300dbfbe-d11c-4c1c-bf47-51906716e374n%40googlegroups.com.


TiddlerOutlineViewer.json
Description: application/json


Re: [tw5] Re: Tip and Question - Inline edit of the text field

2021-05-29 Thread TW Tones
Mohammad,

I would be happy to do so, however I want to solve the size and coloring of 
the checkbox in the view toolbar before doing so. To me the solution should 
be easy and simple so people can duplicate it for other. Of course I can do 
it via a button, and a display filter and do more.

That is if I can get coloured checkboxes in the view toolbar I would be 
very happy.

Tones

On Saturday, 29 May 2021 at 23:11:55 UTC+10 Mohammad wrote:

> On Sat, May 29, 2021 at 3:47 AM TW Tones  wrote:
>
>> Folks,
>>
>> Thanks for the feedback. I would like to emphasise a desire to provide a 
>> "very simple" solution for this commonly asked question. 
>>
>> I concur with your comments and understand buttons vs checkbox, state 
>> tiddlers vs a flag inside the current tiddler. In this case however the 
>> tool is for editing the tiddler so I felt it can be kept simple by saving 
>> in the tiddler. 
>>
>> The cancel button (delete the field) or do you mean "undo" mario? is that 
>> essential? I can see in a fuller solution it may be simple to store the 
>> text field before edit in a variable, and if undo is pressed restore it.
>>
>> I can see your various points captured in a plugin rather than this code 
>> solution, and I have done this for myself already. I want to refine the 
>> simple solution if possible.
>>
>> Mohammad,
>>
>> In other versions of this I have also had internal and external multiline 
>> text fields with notes working the same way. Some arising from discussions 
>> with you (perhaps if I have the right Mohammad perhaps you could sign off 
>> Mohammad Shiraz?)
>>
>
> Why not distribute this as your first plugin? Put it on GitHub!
> I think this can be used for live nores, sticky notes, ...
>
>
>> All,
>> The fact is if a simple css or html can help me add a tooltip to the 
>> checkbox and make it look more like a button, while in the toolbar this 
>> simple solution would be more complete.
>>
>> Tones
>> On Saturday, 29 May 2021 at 02:10:18 UTC+10 Mohammad wrote:
>>
>>> Interesting!
>>>
>>> This can be used to add comments at the end of tiddler!
>>>
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Fri, May 28, 2021 at 12:21 PM TW Tones  wrote:
>>>
 OOps

 Also add a tiddler tagged $:/tags/ViewTemplate containing
 <$list filter="[all[current]inline-edit[yes]]">
{{||$:/core/ui/EditTemplate/body}}
 

 Regards
 Tones
 On Friday, 28 May 2021 at 17:48:02 UTC+10 TW Tones wrote:

> Folks,
>
> Having worked with TiddlyWiki for some time, I have managed to get a 
> way to edit the text field without going into edit mode. I just went to 
> revisit this with a minimal case, and was surprised it worked, in part 
> because its easy to share.
>
> Place the following in a tiddler tagged $:/tags/ViewToolbar
> \whitespace trim
> <$list filter="[all[current]has:field[inline-edit]]">
> <$checkbox field="inline-edit" checked="yes" unchecked="no" 
> default="no">
> 
>
> Now any tiddler to which you add the field inline-edit will gain a 
> checkbox in the toolbar, allowing you to toggle editing the text in view 
> mode, without loosing focus in edit mode.
>
> Question
> This button need a little more work, to comply with the tiddlywiki 
> standard, I will do that shortly. However my Question is since this is 
> easy 
> to achieve does anyone know how to restyle the checkbox better for use in 
> the toolbar?
>
>- Make it larger and similar in size to existing buttons
>- Provide a tooltip
>- Perhaps alter the color
>
> I will then refine and republish here.
>
> Tones
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "TiddlyWiki" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to tiddlywiki+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/19612ae1-c72d-43ac-9169-3e8bee22b2bbn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/6952ed06-6e5c-4d56-a919-d21e7130b7dcn%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 

[tw5] Re: Understanding Templates, Macros, Etc.

2021-05-29 Thread Eric Shulman
On Saturday, May 29, 2021 at 2:36:29 PM UTC-7 rj...@blackperl.com wrote:

> Please forgive the somewhat newbie-ish post. 
>
You don't need to ask for "forgiveness"... this group welcomes "newbies" 
with open arms. 

> I want to be able to click a button and create a new "Project" tiddler, in 
> which a few basic tags are set but which also has the skeleton content of:
>
> !!Materials
>
> !!!Kits/Aftermarket
>
> !!!Accessories
>
> !!References
>
> !!Web References
>
> !!Notes
>
>
1) First, create a tiddler (e.g., "ProjectStarter"), containing the desired 
"skeleton content" and tags.
2) Next add the following $button wherever you like:
<$button message="tm-new-tiddler" param="ProjectStarter">New 
Project

That's it.  When you press the "New Project" button, it will open a new 
tiddler for editing with the indicated default starting content.

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/dfb7829e-31c8-468b-9777-e407e9b5f588n%40googlegroups.com.


[tw5] Understanding Templates, Macros, Etc.

2021-05-29 Thread Randy J. Ray
Please forgive the somewhat newbie-ish post. What I am trying to do is 
similar to something another list member posted about recently, but I 
was still new to the list and getting my mail app to properly file 
list-mail. As such, I lost some of the threads.


I use TiddlyWiki a fair amount, with different wikis for different 
purposes: one for coding projects, one for master's thesis research, one 
for my scale modeling hobby projects, etc. But for each of these I have 
a similar need: I want to be able to create a new tiddler with some 
amount of text already present (generally just a collection of headings 
at different levels).


Using the scale modeling wiki as an example: I want to be able to click 
a button and create a new "Project" tiddler, in which a few basic tags 
are set but which also has the skeleton content of:


   !!Materials

   !!!Kits/Aftermarket

   !!!Accessories

   !!References

   !!Web References

   !!Notes

I have similar needs for the other wikis, but different basic structure.

I would normally think of this sort of thing as a template, but I think 
that TW uses template to mean something different? I found a very close 
sample of this on the Grok TiddlyWiki site, using "$action-sendmessage" 
and "tm-new-tiddler", but it wasn't clear how to include body content.


Thanks in advance,

Randy

--
"""
Randy J. Ray  San Jose, CA
rj...@blackperl.com
twitter.com/rjray
Silicon Valley Scale Modelers: http://www.svsm.org

--
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/dc884ca6-2815-aefb-5f9a-9d6223a081b6%40blackperl.com.


[tw5] Re: Question for long time TiddlyWiki users

2021-05-29 Thread Jon
Hi, 

as you are only asked to enter the password once, I always type the 
password first in a text editor to make sure I've typed it correctly and 
then copy & paste it into the box. Otherwise, if you encrypt the tiddler 
with misspelled password, you won't know what the typo was and there's a 
chance you won't be able to retrieve the file. Could this have happened in 
your case?

Regards
Jon

On Saturday, 29 May 2021 at 01:22:22 UTC+1 Em Heppler wrote:

>
> Using it daily for a few months with no issue. Then something happened a 
> few days ago, not sure what happened, but it suddenly wouldn't accept my 
> password.
>
> Issue found at: https://groups.google.com/g/tiddlywiki/c/-50bBlRdcks
>
> Because I'm not sure what caused this, its entirely possible that 
> encryption with TW works perfectly and it was just a matter of something 
> else going on with my installation.
>
> Regardless of how you encrypt, I would highly recommend you come up with 
> regular backup system.
>
> On Friday, May 28, 2021 at 5:19:14 PM UTC-4 springer wrote:
>
>> Reet, I never had any problem, even though I regularly used encryption on 
>> pretty large projects hosted at tiddlyspot.
>> -Springer
>>
>> On Sunday, May 17, 2020 at 10:09:26 PM UTC-4 Reet Pandher wrote:
>>
>>> Have you tried the encryption feature of the tiddlywiki?
>>> If yes then has it been reliable for you? Reliable as in Has it caused 
>>> any sort of corruption or loss of data even when you know your password? 
>>> Does it work properly even when you have large amounts of data stored in 
>>> it? 
>>>
>>> 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/618e79ab-49a1-4479-9108-57ec6a473f80n%40googlegroups.com.


Re: [tw5] Re: TW-Scripts A Community Resource For All Users

2021-05-29 Thread Mohammad Rahmani
Best wishes
Mohammad


On Sat, May 29, 2021 at 6:16 PM TiddlyTweeter 
wrote:

> Ciao  Mohammad,
>
> Mohammad wrote:
>
>> ... glad to see TW-Script is helpful!
>>
>
> TW-Scripts  IS ace! It has a LOT of
> useful common coding solutions.
> I personally learned a lot from it about Data Dictionaries, for which it
> has many very good, clear, examples.
>
>
Hi TT,

Thanks, it needs to be organized and have more sections like a Data
dictionary!
There is a plan to add a section on templates! In my opinion transclusion,
especially through templates is a real magic. Many do not use it as they
should! one reason is that there are not enough examples showing the power
of transclusion through templates. Dynamic Table (both Alan Aldrich and
Shiraz version) are nothing just efficient use of templates!




> 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/f497d133-1bc5-4433-b39e-5b9415e23a23n%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/CAAV1gMBURXcMGHU1M%3D69Tn1GN0iJHgjNjNnDDcUB7tJ-Qo4djA%40mail.gmail.com.


[tw5] Re: Improve Search in Tiddlywiki

2021-05-29 Thread bimlas
This can be useful if you use a lot of fields or tags to indicate different 
properties:

Locator provides a universal interface for navigating between your tiddlers 
and searching, filtering them without the need to write filter expressions. 
The plugin contains a table of contents macro and an enhanced search engine 
that contains a visual filter builder to filter results by tags and field 
values. You can organize the tiddlers to any number of trees, even by 
custom fields or links in text. Unlike classic Table of Contents, standard 
search, filter search and list of tags, this plugin handles these functions 
organically.

https://bimlas.gitlab.io/tw5-locator/

-- 
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/eb2df6f3-73f4-4d1d-bffe-95db43189acbn%40googlegroups.com.


Re: [tw5] TiddlyWiki Documentation - Syntax

2021-05-29 Thread Mohammad Rahmani
I love this bold/italic format! Now at a short glance one understand how to
call the widget!


If readability does matter, then V3 is the most readable but may take more
space and look lengthy!
My experience says having a standard form for all widgets makes learning
them easier!

I also recommend to keep the table! as it has a column of explanation to
all attributes! in other words the table is a descriptive tool
clarify everything while the syntax is only an abstract form!

Lets see what other says!


Best wishes
Mohammad


On Sat, May 29, 2021 at 8:40 PM Stobot  wrote:

> Progress and feedback gathering:
>
>- The main suggestion I wanted to take a look at first was adding
>"metasyntactic variables", which was suggested by many of you. I had
>expressed my concern with length, so want to show that below and at the
>link to get feedback.
>- Added these attribute strings in a dictionary so they can be shared
>/consistent between widgets
>- Added parenthesis around defaults that are not variable names
>
>
> Review here:
> Documentation — Syntax for Widgets (tiddlyhost.com)
> 
>
> So on the site now I show a V1 (original), V2 (adding the metasyntactic
> variables), and V3 with them, but splitting each attribute into a new line.
> It's not clear to me which is best because I change my mind depending on
> how many attributes there are. While V3 I think makes it easier to read for
> widgets with MANY attributes, I wonder then if it's worth just combining
> the syntax and attribute table altogether since it'd probably fit all side
> by side (think syntax as col1 of a table with the description, defaults as
> other columns...
>
> Examples - fairly simple = Image
> [image: image-widget.PNG]
>
> Examples - more complex = Edit-text
> [image: edit-text-widget.PNG]
>
>
> On Thursday, May 27, 2021 at 6:19:11 PM UTC-4 TW Tones wrote:
>
>> Folks,
>>
>> When documenting code perhaps mouse over and alt text could be used along
>> with highlighting so an optional items being bold nd green could support
>> screen readers and the color blind with mouse over text? We do have  rich
>> environment available after all. I am sure there are standards we can
>> follow.
>>
>> Tones
>>
>> On Friday, 28 May 2021 at 03:47:37 UTC+10 Mohammad wrote:
>>
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Thu, May 27, 2021 at 4:28 PM Stobot  wrote:
>>>
 Thanks everyone for the feedback!

 @Soren

- Good point about the formatting on the values in the Default
section, I'll try parentheses.
- I ''strongly'' agree that every attribute should have an example.
I might have to put that as a secondary effort though to make sure I 
 finish
this.
- Good reminder again on color-blindness. I did end up going with
the bold / italic setup so I think I'll stick with that unless I hear of
something better
- I like the note about doing source="MyImageTiddler" rather than
just source as I have it. I actually did that originally, but after
realizing how many attributes some of these things have, I 
 counter-balanced
against the length of the syntax mockup. I think you're probably right
anyways, and I think your point about a maintained table of example 
 values
per type makes sense - good idea. But take a look at something like
<$edit-text/> which has 20 attributes. At a certain length, I worry we
would lose people, or you then get into a kind of stepped layout where 
 each
attribute gets a newline?
- I agree on the order, I did put all the required ones first, and
then took some liberty on ones I thought were most common, but 
 alphabetical
probably makes more sense. Counter to that might be to bundle (sort
together) the ones that go together.
- Your last point on multiple required attributes is similar to
where I was thinking about too. For reference, using your example -
<$action-setfield>
   - Your suggestion: <$action-setfield $tiddler="tid"
   ($field="field" | $index = "index" | *text* field)
   $value="value" />  - what does the *text* field part mean?
   - I was thinking about the combinations that were valid could
   all be spelled out. For example either tiddler or field are fine, 
 and if
   you use index you need tiddler too.
   - So maybe: <$action-setfield ( $tiddler | $field | $tiddler +
   $field | $tiddler + $index ) $value /> - though again that gets long 
 if
   there are lots of options like this.

 @Tones

- I commented on your other thread on CSS - I agree that's an
opportunity for a little more to be added to the documentation also
- I also like the "copy to clipboard" piece. I saw that in many of
the examples and will try 

Re: [tw5] TiddlyWiki Documentation - Syntax

2021-05-29 Thread Ste
I have no idea if this would be more hassle than it's worth or would be a 
workable work flow but could text stretch or stretch text be used to 
present a condensed version which could be expanded? 
https://links.tiddlywiki.com/urls/7f9e7e60ed40b5098996
https://links.tiddlywiki.com/urls/618ef8913574d547c412

On Saturday, 29 May 2021 at 17:10:32 UTC+1 Stobot wrote:

> Progress and feedback gathering:
>
>- The main suggestion I wanted to take a look at first was adding 
>"metasyntactic variables", which was suggested by many of you. I had 
>expressed my concern with length, so want to show that below and at the 
>link to get feedback. 
>- Added these attribute strings in a dictionary so they can be shared 
>/consistent between widgets
>- Added parenthesis around defaults that are not variable names
>
>
> Review here:
> Documentation — Syntax for Widgets (tiddlyhost.com) 
> 
>
> So on the site now I show a V1 (original), V2 (adding the metasyntactic 
> variables), and V3 with them, but splitting each attribute into a new line. 
> It's not clear to me which is best because I change my mind depending on 
> how many attributes there are. While V3 I think makes it easier to read for 
> widgets with MANY attributes, I wonder then if it's worth just combining 
> the syntax and attribute table altogether since it'd probably fit all side 
> by side (think syntax as col1 of a table with the description, defaults as 
> other columns... 
>
> Examples - fairly simple = Image
> [image: image-widget.PNG]
>
> Examples - more complex = Edit-text
> [image: edit-text-widget.PNG]
>
>
> On Thursday, May 27, 2021 at 6:19:11 PM UTC-4 TW Tones wrote:
>
>> Folks,
>>
>> When documenting code perhaps mouse over and alt text could be used along 
>> with highlighting so an optional items being bold nd green could support 
>> screen readers and the color blind with mouse over text? We do have  rich 
>> environment available after all. I am sure there are standards we can 
>> follow.
>>
>> Tones 
>>
>> On Friday, 28 May 2021 at 03:47:37 UTC+10 Mohammad wrote:
>>
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>>
>>> On Thu, May 27, 2021 at 4:28 PM Stobot  wrote:
>>>
 Thanks everyone for the feedback!

 @Soren

- Good point about the formatting on the values in the Default 
section, I'll try parentheses. 
- I ''strongly'' agree that every attribute should have an example. 
I might have to put that as a secondary effort though to make sure I 
 finish 
this. 
- Good reminder again on color-blindness. I did end up going with 
the bold / italic setup so I think I'll stick with that unless I hear 
 of 
something better
- I like the note about doing source="MyImageTiddler" rather than 
just source as I have it. I actually did that originally, but after 
realizing how many attributes some of these things have, I 
 counter-balanced 
against the length of the syntax mockup. I think you're probably right 
anyways, and I think your point about a maintained table of example 
 values 
per type makes sense - good idea. But take a look at something like 
<$edit-text/> which has 20 attributes. At a certain length, I worry we 
would lose people, or you then get into a kind of stepped layout where 
 each 
attribute gets a newline?
- I agree on the order, I did put all the required ones first, and 
then took some liberty on ones I thought were most common, but 
 alphabetical 
probably makes more sense. Counter to that might be to bundle (sort 
together) the ones that go together. 
- Your last point on multiple required attributes is similar to 
where I was thinking about too. For reference, using your example - 
<$action-setfield> 
   - Your suggestion: <$action-setfield $tiddler="tid" 
   ($field="field" | $index = "index" | *text* field) 
   $value="value" />  - what does the *text* field part mean?
   - I was thinking about the combinations that were valid could 
   all be spelled out. For example either tiddler or field are fine, 
 and if 
   you use index you need tiddler too.
   - So maybe: <$action-setfield ( $tiddler | $field | $tiddler + 
   $field | $tiddler + $index ) $value /> - though again that gets long 
 if 
   there are lots of options like this.

 @Tones

- I commented on your other thread on CSS - I agree that's an 
opportunity for a little more to be added to the documentation also
- I also like the "copy to clipboard" piece. I saw that in many of 
the examples and will try to implement it by reverse-engineering the 
 core 
macro that does it. 
- You bring up a lot of other things that while valid, 

Re: [tw5] TiddlyWiki Documentation - Syntax

2021-05-29 Thread Stobot
Progress and feedback gathering:

   - The main suggestion I wanted to take a look at first was adding 
   "metasyntactic variables", which was suggested by many of you. I had 
   expressed my concern with length, so want to show that below and at the 
   link to get feedback. 
   - Added these attribute strings in a dictionary so they can be shared 
   /consistent between widgets
   - Added parenthesis around defaults that are not variable names


Review here:
Documentation — Syntax for Widgets (tiddlyhost.com) 


So on the site now I show a V1 (original), V2 (adding the metasyntactic 
variables), and V3 with them, but splitting each attribute into a new line. 
It's not clear to me which is best because I change my mind depending on 
how many attributes there are. While V3 I think makes it easier to read for 
widgets with MANY attributes, I wonder then if it's worth just combining 
the syntax and attribute table altogether since it'd probably fit all side 
by side (think syntax as col1 of a table with the description, defaults as 
other columns... 

Examples - fairly simple = Image
[image: image-widget.PNG]

Examples - more complex = Edit-text
[image: edit-text-widget.PNG]


On Thursday, May 27, 2021 at 6:19:11 PM UTC-4 TW Tones wrote:

> Folks,
>
> When documenting code perhaps mouse over and alt text could be used along 
> with highlighting so an optional items being bold nd green could support 
> screen readers and the color blind with mouse over text? We do have  rich 
> environment available after all. I am sure there are standards we can 
> follow.
>
> Tones 
>
> On Friday, 28 May 2021 at 03:47:37 UTC+10 Mohammad wrote:
>
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Thu, May 27, 2021 at 4:28 PM Stobot  wrote:
>>
>>> Thanks everyone for the feedback!
>>>
>>> @Soren
>>>
>>>- Good point about the formatting on the values in the Default 
>>>section, I'll try parentheses. 
>>>- I ''strongly'' agree that every attribute should have an example. 
>>>I might have to put that as a secondary effort though to make sure I 
>>> finish 
>>>this. 
>>>- Good reminder again on color-blindness. I did end up going with 
>>>the bold / italic setup so I think I'll stick with that unless I hear of 
>>>something better
>>>- I like the note about doing source="MyImageTiddler" rather than 
>>>just source as I have it. I actually did that originally, but after 
>>>realizing how many attributes some of these things have, I 
>>> counter-balanced 
>>>against the length of the syntax mockup. I think you're probably right 
>>>anyways, and I think your point about a maintained table of example 
>>> values 
>>>per type makes sense - good idea. But take a look at something like 
>>><$edit-text/> which has 20 attributes. At a certain length, I worry we 
>>>would lose people, or you then get into a kind of stepped layout where 
>>> each 
>>>attribute gets a newline?
>>>- I agree on the order, I did put all the required ones first, and 
>>>then took some liberty on ones I thought were most common, but 
>>> alphabetical 
>>>probably makes more sense. Counter to that might be to bundle (sort 
>>>together) the ones that go together. 
>>>- Your last point on multiple required attributes is similar to 
>>>where I was thinking about too. For reference, using your example - 
>>><$action-setfield> 
>>>   - Your suggestion: <$action-setfield $tiddler="tid" 
>>>   ($field="field" | $index = "index" | *text* field) $value="value" 
>>>   />  - what does the *text* field part mean?
>>>   - I was thinking about the combinations that were valid could all 
>>>   be spelled out. For example either tiddler or field are fine, and if 
>>> you 
>>>   use index you need tiddler too.
>>>   - So maybe: <$action-setfield ( $tiddler | $field | $tiddler + 
>>>   $field | $tiddler + $index ) $value /> - though again that gets long 
>>> if 
>>>   there are lots of options like this.
>>>
>>> @Tones
>>>
>>>- I commented on your other thread on CSS - I agree that's an 
>>>opportunity for a little more to be added to the documentation also
>>>- I also like the "copy to clipboard" piece. I saw that in many of 
>>>the examples and will try to implement it by reverse-engineering the 
>>> core 
>>>macro that does it. 
>>>- You bring up a lot of other things that while valid, would be 
>>>massive scope creep on an already large effort, but I'm happy to pencil 
>>> in 
>>>for future "phases"
>>>   - Multiple versions of common widgets, like the filtered 
>>>   transclusion example, good point. 
>>>   - Documentation of macros & <$macrocall/> syntax
>>>   - Examples should all work on TiddlyWiki.com - totally agree. I 
>>>   think the whole "recipe book" idea as base data (as is used for some 
>>> of the 
>>>   filter stuff is a good starting 

[tw5] RenderCommand: internal links incorrect

2021-05-29 Thread Louis Davout

I have TW 5.1.23 running on node. I'm exporting to static html using the 
RenderCommand:

tiddlywiki --render [!is[system]] "[encodeuricomponent[]addsuffix[.html]]"

The internal links generated still have the # like an achor tag. Ex:

In topicA I have a link to topicB ([[topicB]] the html generated for topicA 
has 

topicB

How can I get the links to point to the files?

topicB

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/d94cedda-9672-4db5-b523-2547ad2b5872n%40googlegroups.com.


Re: [tw5] Re: TW-Scripts A Community Resource For All Users

2021-05-29 Thread TiddlyTweeter
Ciao  Mohammad,

Mohammad wrote:

> ... glad to see TW-Script is helpful!
>

TW-Scripts  IS ace! It has a LOT of 
useful common coding solutions.
I personally learned a lot from it about Data Dictionaries, for which it 
has many very good, clear, examples.

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/f497d133-1bc5-4433-b39e-5b9415e23a23n%40googlegroups.com.


[tw5] Re: TW-Scripts A Community Resource For All Users

2021-05-29 Thread TiddlyTweeter
Ciao Barro ...

REFERENCES COLLECTIVE  remains, even 
now, later, a very interesting and useful resource.
I stolen bits of code from it and have used it to find TW resources more 
easily.

(FYI, I come from Barrow-Upon-Soar 
 in the UK :-)

Best wishes
TT

On Saturday, 29 May 2021 at 10:34:44 UTC+2 barro...@gmail.com wrote:

> TWScripts picks up the torch and continues the fine reference tradition 
> started by Tobias Beer with his tb5.  TWScripts, along with tb5 and 
> Toolmap, were the first reference wikis I included in the References 
> Collective, 
> https://groups.google.com/g/tiddlywiki/c/NirYvurkEfY/m/IMrRrfHFAAAJ
>
> 5 stars & 2 thumbs up rating : )
>
> On Monday, November 16, 2020 at 12:34:36 AM UTC-5 Mohammad wrote:
>
>> TW-Scripts is one of the most comprehensive collection of solutions 
>> including codes, macros, stylesheets, tips and tricks for Tiddlywiki 5.
>>
>> While it has not been updated for a while, but it is there with a lot of 
>> answers to your questions specially for those who have recently started 
>> Tiddlywiki.
>>
>>
>> Page: https://kookma.github.io/TW-Scripts/
>> Github code: https://github.com/kookma/TW-Scripts
>>
>>
>> I hopefully update it as I get some free time!
>> If you like it star it at https://github.com/kookma/TW-Scripts
>>
>> Best wishes
>> Mohammad
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e1064c3b-208e-4cb6-bbcb-bc5423b900b3n%40googlegroups.com.


Re: [tw5] Re: TW-Scripts A Community Resource For All Users

2021-05-29 Thread Mohammad Rahmani
On Sat, May 29, 2021 at 1:04 PM A Gloom  wrote:

> TWScripts picks up the torch and continues the fine reference tradition
> started by Tobias Beer with his tb5.  TWScripts, along with tb5 and
> Toolmap, were the first reference wikis I included in the References
> Collective,
> https://groups.google.com/g/tiddlywiki/c/NirYvurkEfY/m/IMrRrfHFAAAJ
>
> 5 stars & 2 thumbs up rating : )
>

Thank you! I am glad to see TW-Script is helpful!

>
> On Monday, November 16, 2020 at 12:34:36 AM UTC-5 Mohammad wrote:
>
>> TW-Scripts is one of the most comprehensive collection of solutions
>> including codes, macros, stylesheets, tips and tricks for Tiddlywiki 5.
>>
>> While it has not been updated for a while, but it is there with a lot of
>> answers to your questions specially for those who have recently started
>> Tiddlywiki.
>>
>>
>> Page: https://kookma.github.io/TW-Scripts/
>> Github code: https://github.com/kookma/TW-Scripts
>>
>>
>> I hopefully update it as I get some free time!
>> If you like it star it at https://github.com/kookma/TW-Scripts
>>
>> Best wishes
>> Mohammad
>>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/cda98de1-a8ea-4122-a107-d910bd9d2569n%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/CAAV1gMDZJZ0p%3DU6OuiG%2BFXAGnJjjYCu%3DkD_XrHZ%3DPaUNQP3h5w%40mail.gmail.com.


Re: [tw5] Re: Tip and Question - Inline edit of the text field

2021-05-29 Thread Mohammad Rahmani
On Sat, May 29, 2021 at 3:47 AM TW Tones  wrote:

> Folks,
>
> Thanks for the feedback. I would like to emphasise a desire to provide a
> "very simple" solution for this commonly asked question.
>
> I concur with your comments and understand buttons vs checkbox, state
> tiddlers vs a flag inside the current tiddler. In this case however the
> tool is for editing the tiddler so I felt it can be kept simple by saving
> in the tiddler.
>
> The cancel button (delete the field) or do you mean "undo" mario? is that
> essential? I can see in a fuller solution it may be simple to store the
> text field before edit in a variable, and if undo is pressed restore it.
>
> I can see your various points captured in a plugin rather than this code
> solution, and I have done this for myself already. I want to refine the
> simple solution if possible.
>
> Mohammad,
>
> In other versions of this I have also had internal and external multiline
> text fields with notes working the same way. Some arising from discussions
> with you (perhaps if I have the right Mohammad perhaps you could sign off
> Mohammad Shiraz?)
>

Why not distribute this as your first plugin? Put it on GitHub!
I think this can be used for live nores, sticky notes, ...


> All,
> The fact is if a simple css or html can help me add a tooltip to the
> checkbox and make it look more like a button, while in the toolbar this
> simple solution would be more complete.
>
> Tones
> On Saturday, 29 May 2021 at 02:10:18 UTC+10 Mohammad wrote:
>
>> Interesting!
>>
>> This can be used to add comments at the end of tiddler!
>>
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>>
>> On Fri, May 28, 2021 at 12:21 PM TW Tones  wrote:
>>
>>> OOps
>>>
>>> Also add a tiddler tagged $:/tags/ViewTemplate containing
>>> <$list filter="[all[current]inline-edit[yes]]">
>>>{{||$:/core/ui/EditTemplate/body}}
>>> 
>>>
>>> Regards
>>> Tones
>>> On Friday, 28 May 2021 at 17:48:02 UTC+10 TW Tones wrote:
>>>
 Folks,

 Having worked with TiddlyWiki for some time, I have managed to get a
 way to edit the text field without going into edit mode. I just went to
 revisit this with a minimal case, and was surprised it worked, in part
 because its easy to share.

 Place the following in a tiddler tagged $:/tags/ViewToolbar
 \whitespace trim
 <$list filter="[all[current]has:field[inline-edit]]">
 <$checkbox field="inline-edit" checked="yes" unchecked="no"
 default="no">
 

 Now any tiddler to which you add the field inline-edit will gain a
 checkbox in the toolbar, allowing you to toggle editing the text in view
 mode, without loosing focus in edit mode.

 Question
 This button need a little more work, to comply with the tiddlywiki
 standard, I will do that shortly. However my Question is since this is easy
 to achieve does anyone know how to restyle the checkbox better for use in
 the toolbar?

- Make it larger and similar in size to existing buttons
- Provide a tooltip
- Perhaps alter the color

 I will then refine and republish here.

 Tones

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to tiddlywiki+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/19612ae1-c72d-43ac-9169-3e8bee22b2bbn%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/6952ed06-6e5c-4d56-a919-d21e7130b7dcn%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/CAAV1gMB_1ty7b7crw5N4cwqKDCqENR8YcyXBFi7tdRv3Toqg8g%40mail.gmail.com.


[tw5] Re: Improve Search in Tiddlywiki

2021-05-29 Thread A Gloom
In trying to leverage what TW already has and to avoid too many home brewed 
mods (my mods are often questionable), here's what I use to modify the main 
search box:

https://tiddlywiki.com/#Customising%20search%20results

It details how to add custom search visualizations to the default search 
bar and set the new visualizaton as default.

I often clone $:/core/ui/DefaultSearchResultList (renaming it so it will go 
into the directory where you may have other custom system/shadow tiddlers) 
to make a new custom search visualization.  Often to split the 
title/tag/text results smaller segments.  Or replace the search filter 
fields filters with custom search filters to meet my needs, like excluding 
tiddlers like added sidebar tab tiddlers (that I don't want to $:/ prefix) 
that don't exclusively hold content.

What would be of use, would be paginated search results.

On Monday, May 17, 2021 at 4:29:12 AM UTC-4 Atronoush wrote:

> Thank you all for your input!
>
> The PowerSearch by Eric is great as I learn alot from that!
> I recommend it for learning filters!
>
> --Atro
>
>
>

-- 
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/dbb06bdf-5d30-4917-8051-8efada73fbe2n%40googlegroups.com.


[tw5] Re: TW-Scripts A Community Resource For All Users

2021-05-29 Thread A Gloom
TWScripts picks up the torch and continues the fine reference tradition 
started by Tobias Beer with his tb5.  TWScripts, along with tb5 and 
Toolmap, were the first reference wikis I included in the References 
Collective, 
https://groups.google.com/g/tiddlywiki/c/NirYvurkEfY/m/IMrRrfHFAAAJ

5 stars & 2 thumbs up rating : )

On Monday, November 16, 2020 at 12:34:36 AM UTC-5 Mohammad wrote:

> TW-Scripts is one of the most comprehensive collection of solutions 
> including codes, macros, stylesheets, tips and tricks for Tiddlywiki 5.
>
> While it has not been updated for a while, but it is there with a lot of 
> answers to your questions specially for those who have recently started 
> Tiddlywiki.
>
>
> Page: https://kookma.github.io/TW-Scripts/
> Github code: https://github.com/kookma/TW-Scripts
>
>
> I hopefully update it as I get some free time!
> If you like it star it at https://github.com/kookma/TW-Scripts
>
> Best wishes
> Mohammad
>

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