date:20200719

Si, and Folks,

Interesting thread with some very interesting information and techniques.

Si Asked

> I wonder if anyone has done something similar, or has a different approach 
> worth sharing?

I understand the issues with alternative triggers and Eric was wise to keep 
the dirty method hidden, however I believe we need to extend functionality 
where possible, it can be done with with guidance and caution.

Because this is all so dependant on triggers I want to restate an Idea, I 
had some time a go and still intend to demonstrate, but the simple idea is 
to allow additional actions to be set for any existing trigger in 
tiddlywiki. The most common triggers are of course buttons. Buttons are 
triggered to save, close and edit, they can be used to save the wiki and 
reload, and many more functions. Often when trying to solve a problem with 
a trigger one (or more) of the existing buttons may actually fulfil this 
role. 

So given these various timers and triggers it may be quite easy to leverage 
existing buttons or the action navigate to trigger a timer action 
(conditionally).

One thought was to try and identify the missing triggers, for example a 
logout button that saves and resets the user would also be a suitable time 
to do "on exit" triggers, other on exit actions can be loaded on top of it, 
perhaps like backing up the content of local storage to file. Or my 
interest is check in on single file wikis.

An on exit trigger is the complement to the existing startup actions as 
they are for "on wiki load" trigger. Building a set of available buttons 
that by definition are used in the user interface at the practical 
occasions where we often need a trigger.

If we introduced a set of timer buttons, or a timer utility where you could 
set on off or reoccurring timers then enabled custom actions to be 
triggered 90% of all the timer trigger needs would be met. This tool can be 
designed to stop infinite loops as much as possible so the tools given to 
the user are not fragile.

As has being illustrated in this thread, date or period elapsed triggers 
are another desirable feature, This is a kind or raw functionality we 
should provide if not in the core in a key plugin. A generic non specific 
solution. One reason it should be provided upfront is it can be made 
efficient by cascading the test, on change in month we can test for a 
change in year, and at no other time except load.

The most tricky is change in day (midnight when wiki is still open)

Regards
Tony

On Sunday, June 21, 2020 at 10:08:10 PM UTC+10, si wrote:
>
> I use TiddlyWiki as a task manager, among other things, and I thought it 
> would be cool to know how long I spent working on a completed task.
>
> Off the top of my head I imagine having a "start/stop" button that will 
> alternately add a timestamp to the fields "start" and "stop". Then I could 
> (hopefully) create a macro that calculates the total time spent on the task.
>
> I wonder if anyone has done something similar, or has a different approach 
> worth sharing?
>

-- 
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/e4da9a6e-770e-4200-9992-b594c378a913o%40googlegroups.com.

[tw5] Re: Side Preview?

Amerus,

If you are using a multi-screen laptop/desktop the open in new window 
button does display the content of a tiddler, but only the body part. I 
have made two new open in new window buttons, just in a beta state now that 
I have attached that may be another approach to the functionality you are 
after, drop these on tiddlywiki.com to see how it works.

Regards
Tony


On Monday, July 20, 2020 at 2:53:30 AM UTC+10, amreus wrote:
>
> Oh geez I just realized I need to have the built-in Preview (eye) 
> enabled..  lol.  
>
>
> On Sunday, July 19, 2020 at 10:58:22 AM UTC-4, _Phi / hpx1 wrote:
>>
>> yes, that looks correct. Its working for me on an empty.html tiddlywiki, 
>> so I can only suggest some troubleshooting steps :
>>
>>- maybe double check the tag $:/tags/Stylesheet  (no trailing space) ?
>>- make sure the tiddler type is default (click the trash con near the 
>>`type`) and save your tiddler first. The, open/edit a tiddler to check if 
>>it works.
>>- try to save the wiki then refresh (although it shouldn't be 
>>necessary).
>>- maybe run it under TiddlyDesktop to confirm that it's not related 
>>to your browser settings.
>>
>> good luck
>>
>> On Sunday, July 19, 2020 at 11:31:47 AM UTC+2, amreus wrote:
>>>
>>> Thank you for taking your time to create this.
>>>
>>> I have not been able to get it to work.  
>>>
>>> Is this the correct way to use?
>>>
>>>
>>>1. Create a new tiddler, and paste in the css text.
>>>2. Add a tag to the new tiddler of  $:/tags/Stylesheet
>>>
>>>
>>> Is there some step I am missing? I start with a new (5.1.22) empty.html 
>>> to avoid possible interference and still see nothing.  Also there is a 
>>> recent topic of floating toolbar buttons which also does not appear to do 
>>> anything for me. 
>>>
>>>
>>>
>>> Thanks again.
>>> On Saturday, July 18, 2020 at 12:12:40 AM UTC-4, _Phi / hpx1 wrote:

 So it's definitely possible with css, see images and code below. I 
 didn't try to calc the sizes, so you'll need to tinker with the values a 
 bit (adjust top/left/width/height according to the zoom scale you choose). 
 the "side preview" with small zoom :

 and the variant that I use : bigger preview & shadows to fit my theme :

 the CSS code

 /* == the text editor (on the left) ===*/
 .tc-tiddler-preview {
 overflow: visible; /* block preview will overlap the sidebar */ 
 }
 .tc-editor-toolbar {
 margin-top: 2px;
 width: 80%; /* reduced toolbar width for the preview block */
 }
 .tc-edit-texteditor {
 max-height: 55vh; 
 overflow-y: auto;
 }
 .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor {
 width: 620px;  /* width of the editor block on the left*/
 border: 1px solid <>;
 }
 .tc-edit-texteditor tc-edit-texteditor-body {
 height: 275px;
 }
 .tc-tiddler-frame .tc-edit-texteditor {
 margin: 1px 0 1px 0;
 }
 /*== the preview block on the right ===*/
 .tc-tiddler-preview-preview {
 transform: scale(0.62);/* defines the zoom scale */
 float: right; 
 position: absolute; 
 top : 9em;  /* sets where the preview appears */
 left : 550px; /* setswhere the preview appears */
 overflow-x: auto;
 overflow-y:auto;
 width: 100%; 
 height:100%;
 max-width : 500px;  
 max-height: 560px; 
 margin: 4px 0px 3px 3px;
 padding: 3px 16px 3px 16px;
 z-index: 1000;  
  border: 1px solid <>;
 background : <>;
 } 


 On Tuesday, July 14, 2020 at 11:28:38 PM UTC+2, amreus wrote:
>
> This is related to Mat's SideEditor, but I thought not on-topic so I 
> started a new topic. 
>
> So would it be possible to make a "Side Preview" plugin? So instead of 
> floating a side editor, the normal editor is used but a small (tiny?), 
> live 
> preview window is floated over the sidebar when the tiddler is being 
> edited? Sort of like the preview when you hover over the Windows taskbar.
>
>
>
>
>

-- 
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/58d41a5f-0f0c-455a-a477-42154960aba6o%40googlegroups.com.


new-windows.json
Description: application/json

[tw5] Re: tm-open-window - how use paramObject?

Mat,

Somewhere recently a chat about open in new window, and discussions about 
the side editor, which impresses me, but some how I find it hard to use, 
something personal thing about edit in sidebar, I went on to make open in 
new window more robust for my needs that allows us to edit tiddlers to view 
with the view template

The key for me was being able to open in new window, in view or edit modes 
on tiddlers, that incorporate the view and edit templates that impact 
tiddlers in the story but also in the new window. The Open in window is 
only really a "display body in new window".


   - Try this on Tiddlywiki.com new-windows (attached)
   - I also included prior work which moves the tiddler to the new window, 
   ie closes the one in the story first, but this only displays the body.

I am keen to see where you go, perhaps with refining the chrome around new 
windows.

So I share this in the spirit of collaboration. I will eventually publish 
it if people are keen.

Regards
Tony

On Monday, July 20, 2020 at 1:00:47 AM UTC+10, Mat wrote:
>
> Eric Shulman wrote:
>>
>> You can get *some* control over the width/height of the opened window by 
>> calculating it based on $:/info/browser/screen/width and 
>> $:/info/browser/screen/height.
>>
>
> Yes, that's a good idea and I think it would even give me *full* control 
> because I can do something like:
> [{$:/info/browser/screen/width}multiply[my-value-in-vh-or-vw]]
>
> <:-)
>

-- 
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/db59b686-2769-43c3-9585-e04e8afefab0o%40googlegroups.com.


new-windows.json
Description: application/json


Move to new window.tid
Description: Binary data

[tw5] Re: BOA - Catalog of selected and sorted tiddlers


[image: Snag_419a8585.png] 
oleghbond,

This looks elegant but personally I find a second language, I do not know, 
difficult to work with. But once I had a tiddler open with the 
<>
Macro I started to see it working.

I need to explore further but is it fair to say "This is a catalogue for 
browsing and listing a selected set of tags"?

Since you make use of tag pills, have a look at this attached informal set 
of macros that add functionality to the tag pill drop down, it may work 
well with your solution.

Once installed it looks like above.

Thanks for sharing.


Regards
Tony









On Monday, July 20, 2020 at 6:44:00 AM UTC+10, oleghbond wrote:
>
> Plugin is:
>
>- titled *BOA - Catalog of selected and sorted tiddlers*,
>- placed locally at $:/plugins/boa/catalog 
>,
>- placed globally at https://protw.github.io/templ,
>- dependent on plugin *Shiraz *and widget *Checklist*.
>
> The plugin displays a set of tiddlers selected by tags and sorted by the 
> creation date as a tiled grid. For the tag selection and the creation date 
> filtering the control panel is used:
>
> [image: catalog-control.png]
>
> The list of tags at the catalog control panel is defined by 
> index full-tag-list of the data tiddler $:/plugins/boa/catalog/vars 
> . 
> So, for defining own list of tags one has to edit the 
> index full-tag-list of the data tiddler $:/plugins/boa/catalog/vars 
> . 
> In case a certain tag from the list contains a space this tag has to be 
> embraced into square brackets [[certain tag]].
>
> Immediately below the control panel the tiled grid of the selected and 
> sorted tiddlers is placed. Each tiddler in the grid is displayed under 
> control of the template $:/plugins/boa/catalog/template/catalog-element 
> .
>  
> Thus the template can be customized by a user.
>
> The complete catalog including the control panel and the tiled tiddler 
> grid can be revealed by inserting macros <>.
>
> An example can be seen at https://protw.github.io/treemap
>

-- 
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/0f74742b-47d2-4520-9031-71fdcf109f04o%40googlegroups.com.


reimagin-tags.json
Description: application/json

[tw5] Re: First release of

2020-07-19 Thread Joshua Fontany

Followed! Very very cool, Lin. 
Is this for single wiki at a time? Single repo?
Can you use Bob with it seamlessly?

Looking forward to digging in here, and I noticed a shout out for my *VSCode 
TW5 Syntax* extension in your readme. Mahalo (thank you)!

Best,
Joshua Fontany

On Sunday, July 19, 2020 at 12:12:38 PM UTC-7 Lin Onetwo wrote:

>
> Hi, I've been recently working on a new Desktop App for TiddlyWiki, which 
> focuses on syncing data to Github and providing extra nodejs API to 
> TiddlyWiki plugins.
>
> https://github.com/tiddly-gittly/TiddlyGit-Desktop
>
> Most of the code is based on my experience using 
> Tiddlywiki-NodeJS-Github-Template 
>  this 
> year, but I've implement git-sync 
>  in 
> TiddlyGit-Desktop, so sync experience will be much better.
>
> This is still the first alpha release, to show the possibility, if you 
> like it, you can click "watch -> Release Only" to get updates on the future 
> versions.
>
> I will implement a TiddlyGit-Mobile in the future, after TiddlyGit-Desktop 
> is stable, if I have time...
>
> This App is totally free, but it is based on my friend's App's code, there 
> may be a prompt asking for license code, just ignore it, I will remove this 
> in the next release.
>
> Lin Onetwo
>

-- 
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/bf0758e9-618d-4695-8a5c-0a1a4429d229n%40googlegroups.com.

[tw5] Re: Chatbot Plugin

TT,

I think I understand the point you are making, but being aware of the 
further shore is important, to ensure we do not compromise the future. Some 
one can set off for that shore when they please, but to know its there 
permits us to choose if we wish to learn to build a boat.

I am yet to understand the scripts on which it is driven but I would like 
to see it respond to content. Even just simply "how are you today?" "I am 
good and in edit mode", or "who are you", "I am wikititle".



On Sunday, July 19, 2020 at 10:59:25 PM UTC+10, TiddlyTweeter wrote:
>
> TW Tones
>
> As ever you reach for the further shore. In this case it is maybe 
> premature.
>
> The *.rive* scripting is well mature. The documentation is excellent. The 
> plugin simply instantiates it.
>
> The issue you getting at is whether we need "more".
>
> SO let us pragmatically see!
>
> My one practical comment to CB was to add a macro so we could do *< "$:/inter-act.rive">>.*
>
> I think, already, its a neat interface with a lot of intelligence. Deeper 
> integration with TW *will require understanding .rive scripts*, I think.
>
> Best wishes
> TT
>
> On Sunday, 19 July 2020 04:16:22 UTC+2, TW Tones wrote:
>>
>> Folks,
>>
>> On the chatbot, my thinking is how can we make the chatbot rely on 
>> content in a tiddlywiki, such as a knowledge base built with tiddlers 
>> fields and tags, perhaps TOC's or for example a genealogical tree such that 
>> the chat bot can be asked questions who's answers are sourced from the 
>> content of the wiki. eg; Does tony have an uncle, who are tony's aunts and 
>> uncles? Does fred have any living siblings? A bit like a Structured Query 
>> language in a chatbot.
>>
>> It would allow for another level of abstraction, that is given a 
>> knowledge base provide the user with a way to ask questions of it. I could 
>> imagine later even using this code, to code solutions at the higher 
>> abstraction level so rather than a list widget you use a query or question 
>> to list a set.
>>
>> To do this we need to find away to get the content to map to a data model 
>> that the bot can make use of and visa versa. The expert systems of old and 
>> the decision trees of big data and machine learning of today can easily be 
>> represented on top of tiddlywiki. It would be dreamy to allow these to be 
>> developed freely on tiddlywiki but then have a chatbot able to interpret 
>> plain language and respond with the knowledge. The 4th generation 
>> programming languages of the past which tiddlywiki, especially the list and 
>> set handling features is more than adequate for emulating, could be 
>> personified through a chat bot.
>>
>> Perhaps we first start with allowing the chat bot to respond to questions 
>> in tiddlywiki terms eg; have you any tasks due today, where "tasks" and 
>> "today" are defined, tasks defined by the wiki by the wiki designer, today 
>> as part of the tool set. So ideally we need to give the chatbot a way to 
>> look into the content, rather than put the content into the chatbot.
>>
>> Food for thought
>> TW Tones
>>
>>
>> On Thursday, July 16, 2020 at 3:19:55 PM UTC+10, ChristianB wrote:
>>>
>>> Hi All,
>>>
>>> I've created a chatbot plugin that would like to share with this group.  
>>>
>>> Its available here:  
>>> http://ceebeetree.tiddlyspot.com/#:%24%3A%2Fplugins%2Fceebee%2Fchatbot%2Fui%2Fchat
>>>  
>>>
>>> I'm interested to see what uses people can apply this to in their own 
>>> wiki's... at the moment the chatbot is using a very simplistic set of 
>>> responses that were available as a sample for the underlying AI library 
>>> (RiveScript) so it would be interesting what useful responses people can 
>>> program their own bot to provide...
>>>
>>> Also any review on the code is welcome - this is my first plugin I've 
>>> loaded to GitHub so happy to take on some push suggestions etc 
>>>
>>> Cheers
>>> CB
>>>
>>

-- 
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/bafd2e59-8499-4c0e-88fc-9daf2f5333d4o%40googlegroups.com.

[tw5] Re: Converting a tiddler name to a field name to display relevant fields

 

> \define ModifierBlock(for)
> Hello
> <$set name="mfield" filter="[[$for$]lowercase[]addprefix[mod-]]">
> <>
> 
> <$list filter="[all[tiddlers]has]">
> <><$view field=<> />
> 
> 
> 
> \end
>
> <>
>

So, IMO this slightly modified code should say Hello, list the 
dumpvariables and then show a table with tiddlers that have a mod-test 
field and their content of that field.
As Felicia says, either you have the macro and the call in the same tiddler 
or, if separate, then the macro must have the tag $:/tags/Macro

<:-)

-- 
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/b104b764-c2a7-40a3-b9a4-bf576bf983a5o%40googlegroups.com.

[tw5] BOA - Catalog of selected and sorted tiddlers

2020-07-19 Thread oleghbond

Plugin is:

- titled *BOA - Catalog of selected and sorted tiddlers*,
- placed locally at $:/plugins/boa/catalog
,
- placed globally at https://protw.github.io/templ,
- dependent on plugin *Shiraz *and widget *Checklist*.

The plugin displays a set of tiddlers selected by tags and sorted by the
creation date as a tiled grid. For the tag selection and the creation date
filtering the control panel is used:

[image: catalog-control.png]

The list of tags at the catalog control panel is defined by
index full-tag-list of the data tiddler $:/plugins/boa/catalog/vars
.
So, for defining own list of tags one has to edit the
index full-tag-list of the data tiddler $:/plugins/boa/catalog/vars
.
In case a certain tag from the list contains a space this tag has to be
embraced into square brackets [[certain tag]].

Immediately below the control panel the tiled grid of the selected and
sorted tiddlers is placed. Each tiddler in the grid is displayed under
control of the template $:/plugins/boa/catalog/template/catalog-element
.

Thus the template can be customized by a user.

The complete catalog including the control panel and the tiled tiddler grid
can be revealed by inserting macros <>.

An example can be seen at https://protw.github.io/treemap

--
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/2d134be3-1ddf-4217-b495-c26aa61e930dn%40googlegroups.com.

[tw5] Re: Autoscroll in TW

On Sunday, July 19, 2020 at 12:49:20 PM UTC-7, Felicia Crow wrote:
>
> so took finally another look and while I can't say which update did it, I 
> can say that it now also works in firefox without problems.
>

That is good news!  I also can't say which update did it, but my *guess* is 
it was a side effect of switching from
using a  to a <$button> for the "scrollFrame" in AutoScroll/Template.

The $button enables the use of keyboard to pause and resume (enter or 
space) and to stop (escape).  But it also means
that a different type of container is now being used to surround the 
scrollContent, and that would mean different
browser-internal code as well (for handling overflow on buttons vs divs).

Some things are just luck... or magic.   Whichever it is, I'm glad it's now 
working as intended.

-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/c0321af2-d8d9-400b-b2ab-632a07d070f6o%40googlegroups.com.

[tw5] Re: First release of

Thanks for sharing stuff - I'm afraid I have to ask some totally basic 
questions:

This is an app I download to my desktop - yes?
It is used do open/run tiddlywikis that are not stored on my computer but 
on github - yes?
I'm supposed to install the app on all devices from which I want to access 
the wikis - yes?
The wikis on github are stored as files, like the tiddlywiki5 respository - 
yes?

Thank you.

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c132160c-56d7-448e-9c7f-ebb3ee7bb5a3o%40googlegroups.com.

[tw5] Re: Presenting: SideEditor 2.0 - A live editor floating by the river side...

amreus wrote:
>
> I somewhat accidentally found http://j.d.fullscreen.tiddlyspot.com/ 
> which, when preview is turned on, is about what I pictured making.  
>

Oh, I have not seen that! 

On a side note, there appears to be many, many existing solutions for TW. 
> How on earth are we supposed to find them?
>

Hopefully someone like, for example, you will come up with a good solution 
for it... it is a HUGE problem for the community. Various attempts have 
been made but it is IMO not solved in a satisfactory way yet.

<:-) 

-- 
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/3f63a031-e77a-4763-a8fb-684485223453o%40googlegroups.com.

[tw5] Re: Autoscroll in TW

2020-07-19 Thread Felicia Crow

Hi Eric,

so took finally another look and while I can't say which update did it, I 
can say that it now also works in firefox without problems.

Regards,
Felicia

On Friday, 17 July 2020 at 12:55:23 UTC+2 Eric Shulman wrote:

> another update:
>
> * changed TiddlyTools/AutoTag/Setup "autotag" field to "autotags" (plural)
>- field now allows multiple tag values to be listed, e.g., "autoscroll 
> song", will enable autoscroll handling for tiddlers tagged with "song" as 
> well as those tagged "autoscroll"
>
> * changed "max scroll" calculation
>- scrolling now ends when last line becomes visible at the *bottom* of 
> the scrolling area.  Previously scrolling would end when last line reached 
> the *top* of the scrolling area.
>
> * changed symbols for "start/pause/resume" button.  Shows "chevron-down" 
> when not scrolling (either at start, or when paused).  Shows 
> "timestamp-off" when scrolling.
>
> -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/446ddd8b-9ffb-4881-b674-018a7b579ba4n%40googlegroups.com.

[tw5] Re: Converting a tiddler name to a field name to display relevant fields

2020-07-19 Thread Felicia Crow

Hi,
I am sorry, I have missed something that is by now obvious to me, but not 
necessarily to everyone.

When you wrote that your macro did not produce any output I tested the 
macro and since my tests where in the same tiddler due to it being easier 
it of course worked.
>From what you are describing now it sounds more like not the macro itself 
being the problem, but that you are missing the tag $:/tags/Macro on the 
macro containing the tiddler.
Without this tag your macro only exists within the context of the tiddler 
it was defined in and can only be used there. 

For the sake of completeness: There is also the ImportVariableWidget/Import 
Pragma , but judging by your 
description in this case it is probably easier to just mark your macro as 
global.

Regards,
Felicia
 
On Sunday, 19 July 2020 at 19:49:54 UTC+2 drmo...@gmail.com wrote:

>
> I don't suppose anyone has any further enlightenment on this, do they?
>
> I'm still completely stuck. Even changing the macro to:
>
> \define ModifierBlock(for:"")
> Hello
>
> <$set name="x" value=<<__for__>> >
> <$set name="mfield" filter="[titlelowercase[]addprefix[mod-]]">
> <>
> 
>
> <$list filter="[all[tiddlers]has]">
> <><$view field=<> />
> 
> 
> 
> 
> 
> \end
>
> Invoking
>
> <>
>
> In another tiddler produces nothing at all (not even "Hello" or the output 
> from dumpvariables) and no indication why not, which is not really a good 
> development environment! Is there any way to get a clue what's happening?
>
>

-- 
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/dc84814e-634c-4f29-ad0b-d841ccc3e7afn%40googlegroups.com.

[tw5] Macro only loading when viewing.

2020-07-19 Thread Jeff W

Hey folks,

I've incorporated, into my Noteself usage, the ximg macro located here->  
[External Image Path 
Macro](http://www.richshumaker.com/tw5/tw-photo.html#External%20Image%20Path)

It works great and works when I view a tiddler using the markup.

I have since modified the approach (created new tiddlers) to create 
essentially an External Link Path Macro (xpdf). My modified macro xpdf is 
intended to allow external links to open pdfs. The macro seems to work, but 
only when I perform the following:

   1. advance search for the macro
   2. select the xpdf macro
   3. when the tiddler appears (I don't have to open the edit window) the 
   tiddlers that are using the macro work.

Here's what I've got in the tiddler:

A tiddler named "$:/macros/xpdf" and tagged "$:/tags/Macro" with the 
following content


\define pdfAtPath(t, y, d, p)
[ext[$t$|$p$$y$ JBW/$d$]]
\end

\define xpdf(title, year, doc, path:"$:/macros/xpdf/path")
<$macrocall $name="pdfAtPath" p={{$path$}} t="$title$" y="$year$" d="$doc$"
/>
\end

Another tiddler named "$:/macros/xpdf/path" and tagged "$:/tags/Macro" with 
the following content

./JBW Notes Chrono/

In the tiddler calling the macro, the following notation is used:

<>


Some other data (if needed).

   - Mac OS 10.15.5
   - Latest Noteself install 5.1.21
   - I have a local CouchDB (3.1.0) instance running
   - I have a remote CouchDB (2.3.1) instance running
   - This DB is replicating to and from each CouchDB instance

The Questions...

   - Does anyone see any reason why the xpdf macro would need the extra 
   step?
   - Would the ximg and xpdf conflict with each other? (They both appear to 
   work once the xpdf macro is viewed)
   - Are there certain variables that I need to change because they are 
   unique (I wouldn't think this to be true)
   - Anyone have any ideas on how to fix it?

Thanks in advance,

-- 
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/0cfc9ab0-dca8-4709-b2ca-5730ebe6ef26o%40googlegroups.com.

[tw5] First release of

2020-07-19 Thread Lin Onetwo


Hi, I've been recently working on a new Desktop App for TiddlyWiki, which 
focuses on syncing data to Github and providing extra nodejs API to 
TiddlyWiki plugins.

https://github.com/tiddly-gittly/TiddlyGit-Desktop

Most of the code is based on my experience using 
Tiddlywiki-NodeJS-Github-Template 
 this year, 
but I've implement git-sync 
 in 
TiddlyGit-Desktop, so sync experience will be much better.

This is still the first alpha release, to show the possibility, if you like 
it, you can click "watch -> Release Only" to get updates on the future 
versions.

I will implement a TiddlyGit-Mobile in the future, after TiddlyGit-Desktop 
is stable, if I have time...

This App is totally free, but it is based on my friend's App's code, there 
may be a prompt asking for license code, just ignore it, I will remove this 
in the next release.

Lin Onetwo

-- 
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/5809f790-d688-4d70-90f8-7a76bb22848dn%40googlegroups.com.

[tw5] Re: Converting a tiddler name to a field name to display relevant fields

2020-07-19 Thread Mark Green


I don't suppose anyone has any further enlightenment on this, do they?

I'm still completely stuck. Even changing the macro to:

\define ModifierBlock(for:"")
Hello
<$set name="x" value=<<__for__>> >
<$set name="mfield" filter="[titlelowercase[]addprefix[mod-]]">
<>

<$list filter="[all[tiddlers]has]">
<><$view field=<> />





\end

Invoking

<>

In another tiddler produces nothing at all (not even "Hello" or the output 
from dumpvariables) and no indication why not, which is not really a good 
development environment! Is there any way to get a clue what's happening?

-- 
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/abeaecf5-d0d0-499a-bd28-755f916deb89o%40googlegroups.com.

[tw5] Re: Side Preview?

Oh geez I just realized I need to have the built-in Preview (eye) 
enabled..  lol.  


On Sunday, July 19, 2020 at 10:58:22 AM UTC-4, _Phi / hpx1 wrote:
>
> yes, that looks correct. Its working for me on an empty.html tiddlywiki, 
> so I can only suggest some troubleshooting steps :
>
>- maybe double check the tag $:/tags/Stylesheet  (no trailing space) ?
>- make sure the tiddler type is default (click the trash con near the 
>`type`) and save your tiddler first. The, open/edit a tiddler to check if 
>it works.
>- try to save the wiki then refresh (although it shouldn't be 
>necessary).
>- maybe run it under TiddlyDesktop to confirm that it's not related to 
>your browser settings.
>
> good luck
>
> On Sunday, July 19, 2020 at 11:31:47 AM UTC+2, amreus wrote:
>>
>> Thank you for taking your time to create this.
>>
>> I have not been able to get it to work.  
>>
>> Is this the correct way to use?
>>
>>
>>1. Create a new tiddler, and paste in the css text.
>>2. Add a tag to the new tiddler of  $:/tags/Stylesheet
>>
>>
>> Is there some step I am missing? I start with a new (5.1.22) empty.html 
>> to avoid possible interference and still see nothing.  Also there is a 
>> recent topic of floating toolbar buttons which also does not appear to do 
>> anything for me. 
>>
>>
>>
>> Thanks again.
>> On Saturday, July 18, 2020 at 12:12:40 AM UTC-4, _Phi / hpx1 wrote:
>>>
>>> So it's definitely possible with css, see images and code below. I 
>>> didn't try to calc the sizes, so you'll need to tinker with the values a 
>>> bit (adjust top/left/width/height according to the zoom scale you choose). 
>>> the "side preview" with small zoom :
>>>
>>> and the variant that I use : bigger preview & shadows to fit my theme :
>>>
>>> the CSS code
>>>
>>> /* == the text editor (on the left) ===*/
>>> .tc-tiddler-preview {
>>> overflow: visible; /* block preview will overlap the sidebar */ 
>>> }
>>> .tc-editor-toolbar {
>>> margin-top: 2px;
>>> width: 80%; /* reduced toolbar width for the preview block */
>>> }
>>> .tc-edit-texteditor {
>>> max-height: 55vh; 
>>> overflow-y: auto;
>>> }
>>> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor {
>>> width: 620px;  /* width of the editor block on the left*/
>>> border: 1px solid <>;
>>> }
>>> .tc-edit-texteditor tc-edit-texteditor-body {
>>> height: 275px;
>>> }
>>> .tc-tiddler-frame .tc-edit-texteditor {
>>> margin: 1px 0 1px 0;
>>> }
>>> /*== the preview block on the right ===*/
>>> .tc-tiddler-preview-preview {
>>> transform: scale(0.62);/* defines the zoom scale */
>>> float: right; 
>>> position: absolute; 
>>> top : 9em;  /* sets where the preview appears */
>>> left : 550px; /* setswhere the preview appears */
>>> overflow-x: auto;
>>> overflow-y:auto;
>>> width: 100%; 
>>> height:100%;
>>> max-width : 500px;  
>>> max-height: 560px; 
>>> margin: 4px 0px 3px 3px;
>>> padding: 3px 16px 3px 16px;
>>> z-index: 1000;  
>>>  border: 1px solid <>;
>>> background : <>;
>>> } 
>>>
>>>
>>> On Tuesday, July 14, 2020 at 11:28:38 PM UTC+2, amreus wrote:

 This is related to Mat's SideEditor, but I thought not on-topic so I 
 started a new topic. 

 So would it be possible to make a "Side Preview" plugin? So instead of 
 floating a side editor, the normal editor is used but a small (tiny?), 
 live 
 preview window is floated over the sidebar when the tiddler is being 
 edited? Sort of like the preview when you hover over the Windows taskbar.






-- 
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/b86f1e0d-925d-4bac-bc0a-8ff909780f5fo%40googlegroups.com.

[tw5] Re: Presenting: SideEditor 2.0 - A live editor floating by the river side...

Thanks for reply and eplaination.

I somewhat accidentally found http://j.d.fullscreen.tiddlyspot.com/ which, 
when preview is turned on, is about what I pictured making.  

On a side note, there appears to be many, many existing solutions for TW. 
How on earth are we supposed to find them?



On Tuesday, July 14, 2020 at 4:48:51 PM UTC-4, Mat wrote:

> @amreus
> Thanks for feedback, I appreciate it even if what you request would be a 
> very different plugin as I'll explain. So, just maybe you should fiddle 
> with a separate version after all! :-)
>
> I don't like the hover feature.  
>
>
> The very hovering is a main thing because I wanted it to be super easy to 
> flip between the things. One could imagine some kind of clickable area that 
> brings things into view but that would require a very different mechanism. 
> The hovering is purely CSS based whereas clicking likely would be in 
> wikitext (or JS).
>  
> Wit that said, I can mention that I am considering an "open in new window" 
> feature for the editor, i.e a button that splits out the editor, somewhat 
> like rQuickTid . (I also have very 
> vague ideas about merging the two, to make it possible to create new 
> tiddlers via the SideEditor).
>
> It's too difficult  not to trigger the sidebar when going for the Check 
>> button, which is too small. 
>
>
> I can agree with this. I should probably make the check button bigger. 
> Possibly add some transparent margin around also to prevent mis-hovering.
>
>
> I would just prefer to have the editor cover the sidebar stuff. 
>
>
> One downside then, at least on a 14" screen like mine or smaller, is that 
> you can't(?) have an editor that is wider than the sidebar. Maybe you have 
> a bigger screen. But I recall someone putting an editor in one of the 
> sidebar tabs. Can't remember who or the name of the plugin if there ever 
> was one. Possibly it was Mohammad... not sure.
>  
>
>> Then clicking anywhere off the editor textarea would close it, or perhaps 
>> the Escape key could close it also. Other than that, it's a very nice 
>> enhancement. 
>
>
>  I didn't experiment with key commands yet but again, it's not really for 
> CSS which is the key "mechanism" in SideEditor. 
>
> Since you did consider building your own thing, please feel free to mess 
> around with the SideEditor. Or any other thing I've made for that matter. 
>
> <:-)
>

-- 
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/f563a538-d473-4e03-8a15-64893718o%40googlegroups.com.

[tw5] Re: Side Preview?

Yeah I double-checked everything you mentioned.  I can't get it to work in 
Firefox & timimi, nor in TiddlyDesktop. Both using empty.html v 5.1.22. 
It's odd.  I'll keep digging although I don't know exactly where to look at 
the moment.

Thanks.


On Sunday, July 19, 2020 at 10:58:22 AM UTC-4, _Phi / hpx1 wrote:
>
> yes, that looks correct. Its working for me on an empty.html tiddlywiki, 
> so I can only suggest some troubleshooting steps :
>
>- maybe double check the tag $:/tags/Stylesheet  (no trailing space) ?
>- make sure the tiddler type is default (click the trash con near the 
>`type`) and save your tiddler first. The, open/edit a tiddler to check if 
>it works.
>- try to save the wiki then refresh (although it shouldn't be 
>necessary).
>- maybe run it under TiddlyDesktop to confirm that it's not related to 
>your browser settings.
>
> good luck
>
> On Sunday, July 19, 2020 at 11:31:47 AM UTC+2, amreus wrote:
>>
>> Thank you for taking your time to create this.
>>
>> I have not been able to get it to work.  
>>
>> Is this the correct way to use?
>>
>>
>>1. Create a new tiddler, and paste in the css text.
>>2. Add a tag to the new tiddler of  $:/tags/Stylesheet
>>
>>
>> Is there some step I am missing? I start with a new (5.1.22) empty.html 
>> to avoid possible interference and still see nothing.  Also there is a 
>> recent topic of floating toolbar buttons which also does not appear to do 
>> anything for me. 
>>
>>
>>
>> Thanks again.
>> On Saturday, July 18, 2020 at 12:12:40 AM UTC-4, _Phi / hpx1 wrote:
>>>
>>> So it's definitely possible with css, see images and code below. I 
>>> didn't try to calc the sizes, so you'll need to tinker with the values a 
>>> bit (adjust top/left/width/height according to the zoom scale you choose). 
>>> the "side preview" with small zoom :
>>>
>>> and the variant that I use : bigger preview & shadows to fit my theme :
>>>
>>> the CSS code
>>>
>>> /* == the text editor (on the left) ===*/
>>> .tc-tiddler-preview {
>>> overflow: visible; /* block preview will overlap the sidebar */ 
>>> }
>>> .tc-editor-toolbar {
>>> margin-top: 2px;
>>> width: 80%; /* reduced toolbar width for the preview block */
>>> }
>>> .tc-edit-texteditor {
>>> max-height: 55vh; 
>>> overflow-y: auto;
>>> }
>>> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor {
>>> width: 620px;  /* width of the editor block on the left*/
>>> border: 1px solid <>;
>>> }
>>> .tc-edit-texteditor tc-edit-texteditor-body {
>>> height: 275px;
>>> }
>>> .tc-tiddler-frame .tc-edit-texteditor {
>>> margin: 1px 0 1px 0;
>>> }
>>> /*== the preview block on the right ===*/
>>> .tc-tiddler-preview-preview {
>>> transform: scale(0.62);/* defines the zoom scale */
>>> float: right; 
>>> position: absolute; 
>>> top : 9em;  /* sets where the preview appears */
>>> left : 550px; /* setswhere the preview appears */
>>> overflow-x: auto;
>>> overflow-y:auto;
>>> width: 100%; 
>>> height:100%;
>>> max-width : 500px;  
>>> max-height: 560px; 
>>> margin: 4px 0px 3px 3px;
>>> padding: 3px 16px 3px 16px;
>>> z-index: 1000;  
>>>  border: 1px solid <>;
>>> background : <>;
>>> } 
>>>
>>>
>>> On Tuesday, July 14, 2020 at 11:28:38 PM UTC+2, amreus wrote:

 This is related to Mat's SideEditor, but I thought not on-topic so I 
 started a new topic. 

 So would it be possible to make a "Side Preview" plugin? So instead of 
 floating a side editor, the normal editor is used but a small (tiny?), 
 live 
 preview window is floated over the sidebar when the tiddler is being 
 edited? Sort of like the preview when you hover over the Windows taskbar.






-- 
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/dfd701ae-84b6-4890-b654-27a7e3332f72o%40googlegroups.com.

[tw5] Re: How to save multiple lines into a field ?

2020-07-19 Thread clutterstack

Whoop, just ran into this yesterday (and understood it this morning). 

-- 
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/7977e839-050c-4a7d-8f4b-3477b2dadbc1o%40googlegroups.com.

[tw5] Re: tm-open-window - how use paramObject?

Eric Shulman wrote:
>
> You can get *some* control over the width/height of the opened window by 
> calculating it based on $:/info/browser/screen/width and 
> $:/info/browser/screen/height.
>

Yes, that's a good idea and I think it would even give me *full* control 
because I can do something like:
[{$:/info/browser/screen/width}multiply[my-value-in-vh-or-vw]]

<:-)

-- 
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/692c172b-5f5e-4e3d-a8fd-107154864fa7o%40googlegroups.com.

[tw5] Re: Side Preview?

2020-07-19 Thread _Phi / hpx1

yes, that looks correct. Its working for me on an empty.html tiddlywiki, so 
I can only suggest some troubleshooting steps :

   - maybe double check the tag $:/tags/Stylesheet  (no trailing space) ?
   - make sure the tiddler type is default (click the trash con near the 
   `type`) and save your tiddler first. The, open/edit a tiddler to check if 
   it works.
   - try to save the wiki then refresh (although it shouldn't be necessary).
   - maybe run it under TiddlyDesktop to confirm that it's not related to 
   your browser settings.

good luck

On Sunday, July 19, 2020 at 11:31:47 AM UTC+2, amreus wrote:
>
> Thank you for taking your time to create this.
>
> I have not been able to get it to work.  
>
> Is this the correct way to use?
>
>
>1. Create a new tiddler, and paste in the css text.
>2. Add a tag to the new tiddler of  $:/tags/Stylesheet
>
>
> Is there some step I am missing? I start with a new (5.1.22) empty.html to 
> avoid possible interference and still see nothing.  Also there is a recent 
> topic of floating toolbar buttons which also does not appear to do anything 
> for me. 
>
>
>
> Thanks again.
> On Saturday, July 18, 2020 at 12:12:40 AM UTC-4, _Phi / hpx1 wrote:
>>
>> So it's definitely possible with css, see images and code below. I didn't 
>> try to calc the sizes, so you'll need to tinker with the values a bit 
>> (adjust top/left/width/height according to the zoom scale you choose). 
>> the "side preview" with small zoom :
>>
>> and the variant that I use : bigger preview & shadows to fit my theme :
>>
>> the CSS code
>>
>> /* == the text editor (on the left) ===*/
>> .tc-tiddler-preview {
>> overflow: visible; /* block preview will overlap the sidebar */ 
>> }
>> .tc-editor-toolbar {
>> margin-top: 2px;
>> width: 80%; /* reduced toolbar width for the preview block */
>> }
>> .tc-edit-texteditor {
>> max-height: 55vh; 
>> overflow-y: auto;
>> }
>> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor {
>> width: 620px;  /* width of the editor block on the left*/
>> border: 1px solid <>;
>> }
>> .tc-edit-texteditor tc-edit-texteditor-body {
>> height: 275px;
>> }
>> .tc-tiddler-frame .tc-edit-texteditor {
>> margin: 1px 0 1px 0;
>> }
>> /*== the preview block on the right ===*/
>> .tc-tiddler-preview-preview {
>> transform: scale(0.62);/* defines the zoom scale */
>> float: right; 
>> position: absolute; 
>> top : 9em;  /* sets where the preview appears */
>> left : 550px; /* setswhere the preview appears */
>> overflow-x: auto;
>> overflow-y:auto;
>> width: 100%; 
>> height:100%;
>> max-width : 500px;  
>> max-height: 560px; 
>> margin: 4px 0px 3px 3px;
>> padding: 3px 16px 3px 16px;
>> z-index: 1000;  
>>  border: 1px solid <>;
>> background : <>;
>> } 
>>
>>
>> On Tuesday, July 14, 2020 at 11:28:38 PM UTC+2, amreus wrote:
>>>
>>> This is related to Mat's SideEditor, but I thought not on-topic so I 
>>> started a new topic. 
>>>
>>> So would it be possible to make a "Side Preview" plugin? So instead of 
>>> floating a side editor, the normal editor is used but a small (tiny?), live 
>>> preview window is floated over the sidebar when the tiddler is being 
>>> edited? Sort of like the preview when you hover over the Windows taskbar.
>>>
>>>
>>>
>>>
>>>

-- 
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/31eace9f-b9ef-43b7-bf17-84f679e24a09o%40googlegroups.com.

[tw5] Re: tm-open-window - how use paramObject?

On Sunday, July 19, 2020 at 6:22:40 AM UTC-7, Mat wrote:
>
>
>1. width and height are, according to the docs, separate parameters in 
>the tw-open-window call BUT I'm not happy with how they can only be set in 
>pixels because the context I'm using it in does things in vh, vw. 
>
> You can get *some* control over the width/height of the opened window by 
calculating it based on $:/info/browser/screen/width and 
$:/info/browser/screen/height.

For example, if you want the window to be 2/3 of the screen width, you 
could write:

<$action-sendmessage $message="tm-open-window"
   windowTitle=<>
   width={{{ [{$:/info/browser/screen/width}divide[3]multiply[2]] }}} />

-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/97076867-0345-4b1b-a815-233e9242c800o%40googlegroups.com.

[tw5] Re: tm-open-window - how use paramObject?

PMario wrote:
>
> IMO just create them. eg:
>

Hahaaa! That does work! This was the most critical of my questions.

>>1. width and height... pixels VS vh, vw. 
>>
>> That's a restriction coming from the browser API. 
> https://developer.mozilla.org/en-US/docs/Web/API/Window/open#Window_features 
> 
>  
> ... [...] imo can't be changed, even if we want to.
>

Yeah... looks like you're right. 

>
>>1. I wish to control the position of the window.
>>
>> IMO would need to update the function -> GitHub feature request! 

Gotcha. Thanks.

Additionally, the API docs, under the section with headling "Toolbar and UI 
parts features" seem to indicate is should be possible to get rid of UP 
parts. Specifically I want to remove these two "rows", at least the 
"about:blank" row:

...and/but if I do succeed in removing that upper row, then I'll also need 
a "close window" button from within the window. 

For these things to be doable, i.e remove the two "rows" and create a close 
window button, would these also be new features implemented in TW - or is 
it anything that can already now be accessed via tm-open-window?

Thank you PMario!

<:-)

-- 
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/df07a07b-41f7-4596-a716-0ef2485019eao%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

On Sunday, July 19, 2020 at 3:24:36 AM UTC-7, Jed Carty wrote:
>
> To join in the fun, I also made a $action-delay widget that delays the 
> execution of any action widgets contained inside it by a set time. It is an 
> action widget so it gets triggered by the normal mechanisms.
> https://ooktech-tw.gitlab.io/plugins/delayactions/
>

Except for the optional autostart="true" param (to invoke the widget 
outside of a $button) and using milliseconds
for the delay value, my code does pretty much the same as your 
$action-delay widget.

Normally, I eschew duplication of efforts, but in this case, I think I will 
stick with my own version of this widget
primarily because of the two differences noted above.  Triggering timeouts 
more often than 1 second is
useful when calculating elapsed times with sufficient accuracy to avoid 
processing overhead effects
as well as getting sub-second accuracy.

...and, I still think that the autostart="true" param has promise, even 
though it *might* cause some
"run-away" triggers if not used carefully.

-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/18fde75b-ff2f-4d1a-8068-0d705972c8c3o%40googlegroups.com.

[tw5] Re: tm-open-window - how use paramObject?

2020-07-19 Thread PMario

On Sunday, July 19, 2020 at 3:22:40 PM UTC+2, Mat wrote:

But how do I formulate the paramObject argument to achieve:
>
>1. I wish to send along a variable value to be used inside the opened 
>window.
>
> IMO just create them. eg:

<$action-sendmessage $message="tm-open-window" width=xxx height=yyy 
myVar1="some text" myVar2="test" .../>


It should do the trick and give those elements are "variables to the new 
window" ... Similar to <$var or <$set ... 
 

>
>1. width and height are, according to the docs, separate parameters in 
>the tw-open-window call BUT I'm not happy with how they can only be set in 
>pixels because the context I'm using it in does things in vh, vw. 
>
> That's a restriction coming from the browser API. 
https://developer.mozilla.org/en-US/docs/Web/API/Window/open#Window_features 
... Scroll down a bit to "SIZE" and have a closer look at the description. 
min = 100px and unit is px. ... So imo can't be changed, even if we want to.
 

>
>1. I wish to control the position of the window.
>
> IMO would need to update the function -> GitHub feature request! 

Should be possible from the API point of view. See former link.

-mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/24eda26d-f99f-4d1e-bfb1-795287054e3eo%40googlegroups.com.

[tw5] tm-open-window - how use paramObject?

I'm working to improve the SideEditor. The new idea is a "separate window" 
feature, i.e to split out the editor into a separate window which you can 
then place in front of any other applications you're working on with your 
computer.

Question: 

The doc for tm-open-window 
 
reads:

paramObject Hashmap of variables that will be provided to the window
but there is no example for how to use this.

Digging in the core, I find $:/core/modules/startup/windows.js 

 
which has

 paramObject = event.paramObject || {},
 windowTitle = paramObject.windowTitle || title,
 template = paramObject.template || 
"$:/core/templates/single.tiddler.window",
 width = paramObject.width || "700",
 height = paramObject.height || "600",
 variables = $tw.utils.extend({},paramObject,{currentTiddler: title});

(I'm assuming this is a definition of it, as opposed to merely some 
invocation)

But how do I formulate the paramObject argument to achieve:

   1. I wish to send along a variable value to be used inside the opened 
   window.
   2. width and height are, according to the docs, separate parameters in 
   the tw-open-window call BUT I'm not happy with how they can only be set in 
   pixels because the context I'm using it in does things in vh, vw. 
   3. I wish to control the position of the window.

Thank you!

<:-)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/14e4f03c-b316-4d26-97be-8d0f9297c3f7o%40googlegroups.com.

[tw5] Re: Chatbot Plugin

TiddlyTweeter wrote:
>
> Have you tested how smart it is ??? :-)
>

I did test with 

"What is your nmae?" and similar, yes, and it did not give the same reply 
as if correctly spelled.

<:-)

-- 
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/909cdd1d-5fea-49f9-82ba-2e9b174d3165o%40googlegroups.com.

[tw5] Re: Chatbot Plugin

TW Tones

As ever you reach for the further shore. In this case it is maybe premature.

The *.rive* scripting is well mature. The documentation is excellent. The 
plugin simply instantiates it.

The issue you getting at is whether we need "more".

SO let us pragmatically see!

My one practical comment to CB was to add a macro so we could do *<>.*

I think, already, its a neat interface with a lot of intelligence. Deeper 
integration with TW *will require understanding .rive scripts*, I think.

Best wishes
TT

On Sunday, 19 July 2020 04:16:22 UTC+2, TW Tones wrote:
>
> Folks,
>
> On the chatbot, my thinking is how can we make the chatbot rely on content 
> in a tiddlywiki, such as a knowledge base built with tiddlers fields and 
> tags, perhaps TOC's or for example a genealogical tree such that the chat 
> bot can be asked questions who's answers are sourced from the content of 
> the wiki. eg; Does tony have an uncle, who are tony's aunts and uncles? 
> Does fred have any living siblings? A bit like a Structured Query language 
> in a chatbot.
>
> It would allow for another level of abstraction, that is given a knowledge 
> base provide the user with a way to ask questions of it. I could imagine 
> later even using this code, to code solutions at the higher abstraction 
> level so rather than a list widget you use a query or question to list a 
> set.
>
> To do this we need to find away to get the content to map to a data model 
> that the bot can make use of and visa versa. The expert systems of old and 
> the decision trees of big data and machine learning of today can easily be 
> represented on top of tiddlywiki. It would be dreamy to allow these to be 
> developed freely on tiddlywiki but then have a chatbot able to interpret 
> plain language and respond with the knowledge. The 4th generation 
> programming languages of the past which tiddlywiki, especially the list and 
> set handling features is more than adequate for emulating, could be 
> personified through a chat bot.
>
> Perhaps we first start with allowing the chat bot to respond to questions 
> in tiddlywiki terms eg; have you any tasks due today, where "tasks" and 
> "today" are defined, tasks defined by the wiki by the wiki designer, today 
> as part of the tool set. So ideally we need to give the chatbot a way to 
> look into the content, rather than put the content into the chatbot.
>
> Food for thought
> TW Tones
>
>
> On Thursday, July 16, 2020 at 3:19:55 PM UTC+10, ChristianB wrote:
>>
>> Hi All,
>>
>> I've created a chatbot plugin that would like to share with this group.  
>>
>> Its available here:  
>> http://ceebeetree.tiddlyspot.com/#:%24%3A%2Fplugins%2Fceebee%2Fchatbot%2Fui%2Fchat
>>  
>>
>> I'm interested to see what uses people can apply this to in their own 
>> wiki's... at the moment the chatbot is using a very simplistic set of 
>> responses that were available as a sample for the underlying AI library 
>> (RiveScript) so it would be interesting what useful responses people can 
>> program their own bot to provide...
>>
>> Also any review on the code is welcome - this is my first plugin I've 
>> loaded to GitHub so happy to take on some push suggestions etc 
>>
>> Cheers
>> CB
>>
>

-- 
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/cbc570ed-f8d0-492f-8ffb-baa5776fb750o%40googlegroups.com.

[tw5] Re: Chatbot Plugin

Have you tested how smart it is ??? :-)

On Sunday, 19 July 2020 14:55:45 UTC+2, Mat wrote:
>
> TiddlyTweeter wrote:
>>
>> BUT you missing something. First you need look at the .rive format the 
>> plugin supports! It is pretty smart already. The docs are extremely Good 
>> quality.  https://www.rivescript.com/docs/tutorial
>>
>
> I meant the other way around; the fuzzy search could perhaps be used in 
> the chatbot to make the chatbot smarter.
>
> <:-)
>

-- 
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/d29e6e4a-3ada-4b74-bf6e-eed2e573cad5o%40googlegroups.com.

[tw5] Re: Chatbot Plugin

TiddlyTweeter wrote:
>
> BUT you missing something. First you need look at the .rive format the 
> plugin supports! It is pretty smart already. The docs are extremely Good 
> quality.  https://www.rivescript.com/docs/tutorial
>

I meant the other way around; the fuzzy search could perhaps be used in the 
chatbot to make the chatbot smarter.

<:-)

-- 
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/4fb4e819-e03b-4dfc-ae15-ac94a35401ceo%40googlegroups.com.

[tw5] Re: Chatbot Plugin

Mat

I think you thinking of ...

plugin: https://hoelz.ro/files/fts.html

 

discussion: 
> https://groups.google.com/forum/#!searchin/tiddlywiki/Rob$20hoelz%7Csort:date/tiddlywiki/ZvvLTxQz3Ag/jsN4xhzqBgAJ
>  


BUT you missing something. First you need look at the .rive format the 
plugin supports! It is pretty smart already. The docs are extremely Good 
quality.  https://www.rivescript.com/docs/tutorial

TT 

On Sunday, 19 July 2020 14:07:16 UTC+2, Mat wrote:
>
> @Christian
>
> There was someone who created a fuzzy search some time back... (maybe a 
> year ago?) I'm thinking that could be of use?
>
> <:-)
>

-- 
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/95981a2e-0fd9-480e-b398-9581c4b3597ao%40googlegroups.com.

[tw5] Re: Chatbot Plugin

@Christian

There was someone who created a fuzzy search some time back... (maybe a 
year ago?) I'm thinking that could be of use?

<:-)

-- 
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/f7f60dca-dc59-4d12-9197-88285855e99eo%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

On Sunday, July 19, 2020 at 2:25:58 AM UTC-7, PMario wrote:
>
> On Sunday, July 19, 2020 at 7:39:34 AM UTC+2, Eric Shulman wrote:
>>
>> However... I've also added another param, autostart="yes", which will 
>> actually trigger the $action-timeout as soon as it is rendered, even if 
>> it's not inside a $button.
>> I'm not sure when this param will be useful, and it's best to consider it 
>> "experimental" for now.
>>
>  

> @Eric. ... I personally would create 2 plugins. 1 with the "useful" 
> timeout and 1 with the potentially dangerous "experimental" parameter. 
>

As long as you don't specify the autostart="true" param, it just does the 
"useful" timeout when triggered from a user-action (button press).
Note that even without using autostart, you can still create "tail end" 
timer loops that can then be controlled by setting a flag field.

For example, here's how I implemented the timer's "elapsed time" display:

\define ticker_actions()
<$action-timeout delay="1000" id="$(currentTiddler)$" actions="""
   <$list filter="[[$(currentTiddler)$]is[tiddler]]">
  <$action-setfield $timestamp="no" now=<> 
/>
  <$reveal default={{!!stop}} type="match" text="">
 <$importvariables filter="TiddlyTools/Timer"> <> 

""" />
\end

Note how the timeout widget invokes an action that sets the "now" field (to 
track the current time...
used to calculate the elapsed time) and then it checks if the "stop" field 
is blank.  If it is, then it
schedules another timeout to occur in one second.  This function will keep 
invoking itself once
a second until "stop" is set to a non-blank value (i.e., "true"), which is 
triggered by the user 
when they explicitly press the "stop" button in the timer interface.

-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/c8432b4c-2c14-4cd0-9184-9984713f6c22o%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

2020-07-19 Thread Thomas Elmiger

Thank you for the mention, TT, but my Reminders for ToDoNow are triggered by 
(not so obvious) user interaction.

Cool stuff here! 

Cheers, 
Thomas 

-- 
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/324e439f-8d06-473e-94f6-7db79e3f79bao%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

Right.

Just FYI the tools like "ToDoNow" have time based activation of alerts 
already.

Best wishes
TT

On Sunday, 19 July 2020 12:24:36 UTC+2, Jed Carty wrote:
>
> To join in the fun, I also made a $action-delay widget that delays the 
> execution of any action widgets contained inside it by a set time. It is an 
> action widget so it gets triggered by the normal mechanisms.
>
> https://ooktech-tw.gitlab.io/plugins/delayactions/
>
> The trigger actions plugin I made could be used in a similar way, it 
> doesn't have a delay but it can trigger action widgets based on changes to 
> a wiki and could be combined with a delay action widget to execute actions 
> after a set time based on any change in the wiki as a trigger.
>
> https://github.com/inmysocks/TW5-TriggerActions
>
> And I made a timer actions plugin that runs action widgets at specified 
> intervals
>
> https://github.com/OokTech/TW5-TimerActions
>

-- 
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/5ea67644-9af0-4d72-b231-d40ef820ac4fo%40googlegroups.com.

[tw5] Re: Chatbot Plugin

Ed Heil wrote:

> Off topic, but I'm fascinated to hear you worked with Eugene Gendlin! His
> work, and that of his student Ann Weiser Cornell, have been very helpful to
> me, and I even really enjoyed his philosophical work, _Experiencing and the
> Creation of Meaning_, to the degree I understood it!
>

Ciao Ed

I can reply, I think, both acknowledging your interest, which I really
appreciate! :-), and the thread theme.

Gene was an amazing selfless person. He was also a brilliant philosopher.
Experience & The Creation Of Meaning

is still not fully grasped for its significance.
His brilliance as a philosopher clearly comes out when he debates with
other thinkers.
As he does in Language Beyond Postmodernism
.

Both are highly relevant to computer interface design, though the work
needed to show that has not been done yet.

Ann Weiser Cornell is
very important for widely popularising "Focusing", a major practical
application of Gene's philosophy for self-help. She's Good.

In my years with him I grew to be Executive Director of archiving &
preserving his work.
I realised, along with Mary Hendricks, his wife, that giving public access
to most of his published & unpublished (about 140) articles was a v. Good
idea.
Result: after 18 months of good sponsor funded hard graft was the: Gendlin
Online Library

Back to this thread.

Gene actually wrote a formal "Eliza" style script, though not a
programmer, he was interested in exploring the "semantics of response."
It was never made into a program. It only exists on paper.

As a philosopher he was fascinated by the Turing Test
.
His key take-away was

*"... a lot of life is pretending.*

*I know its a robot. *

*It does not matter, *

*IF** it helps me. *

*If it helps I can FEEL it, so will give it credence.*

*What is going on is that humans, programming machines,*

*provide tools that understand some aspects of meaning-making."*

Chritian B's plugin may be a step towards that for TW.

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/b6cb468a-75a4-40e8-a789-05379aa8b92eo%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

2020-07-19 Thread Jed Carty

To join in the fun, I also made a $action-delay widget that delays the 
execution of any action widgets contained inside it by a set time. It is an 
action widget so it gets triggered by the normal mechanisms.

https://ooktech-tw.gitlab.io/plugins/delayactions/

The trigger actions plugin I made could be used in a similar way, it 
doesn't have a delay but it can trigger action widgets based on changes to 
a wiki and could be combined with a delay action widget to execute actions 
after a set time based on any change in the wiki as a trigger.

https://github.com/inmysocks/TW5-TriggerActions

And I made a timer actions plugin that runs action widgets at specified 
intervals

https://github.com/OokTech/TW5-TimerActions

-- 
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/54fe283b-63fd-44fb-9e83-d55107dd36dco%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

2020-07-19 Thread Saq Imtiaz

@Mat

... autostart="yes" ... I'm not sure when this param will be useful
>>
> ... "auto-perform tasks" ... could be the next *big* enhancement
>>
>
> Well, that next big enhancement could - I think - be a partial solution 
> for the current TWederation  
> implementation 
> to function better. 
>

Doesn't Jed already have a plugin that executes actions at timed intervals? 
You could probably use that in combination with startup actions.

-- 
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/89f13d4f-4257-4f31-bce5-ed560c6a4207o%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

2020-07-19 Thread Saq Imtiaz


>
> Automatically triggering actions can be very useful, to create eg: 
> automatic TW UI tests. ... On the other hand, if done wrong it can be very 
> destructive (trust me!). 
>

It's probably useful to point out for end-users that the limitation that 
actions can only be triggered by direct user actions, like clicking a 
button, has never been a technical one as it is exceedingly easy to 
implement. 

Rather it has always been an intentional one based on what are perceived to 
be best practices.

I think at the least some very prominent disclaimers and warning messages 
are a good idea for any plugin that implements such a feature.

-- 
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/e77b0646-c45c-4513-8b38-1bc44709840do%40googlegroups.com.

[tw5] Re: Side Preview?

Thank you for taking your time to create this.

I have not been able to get it to work.  

Is this the correct way to use?


   1. Create a new tiddler, and paste in the css text.
   2. Add a tag to the new tiddler of  $:/tags/Stylesheet


Is there some step I am missing? I start with a new (5.1.22) empty.html to 
avoid possible interference and still see nothing.  Also there is a recent 
topic of floating toolbar buttons which also does not appear to do anything 
for me. 



Thanks again.
On Saturday, July 18, 2020 at 12:12:40 AM UTC-4, _Phi / hpx1 wrote:
>
> So it's definitely possible with css, see images and code below. I didn't 
> try to calc the sizes, so you'll need to tinker with the values a bit 
> (adjust top/left/width/height according to the zoom scale you choose). 
> the "side preview" with small zoom :
>
> and the variant that I use : bigger preview & shadows to fit my theme :
>
> the CSS code
>
> /* == the text editor (on the left) ===*/
> .tc-tiddler-preview {
> overflow: visible; /* block preview will overlap the sidebar */ 
> }
> .tc-editor-toolbar {
> margin-top: 2px;
> width: 80%; /* reduced toolbar width for the preview block */
> }
> .tc-edit-texteditor {
> max-height: 55vh; 
> overflow-y: auto;
> }
> .tc-tiddler-frame .tc-tiddler-preview .tc-edit-texteditor {
> width: 620px;  /* width of the editor block on the left*/
> border: 1px solid <>;
> }
> .tc-edit-texteditor tc-edit-texteditor-body {
> height: 275px;
> }
> .tc-tiddler-frame .tc-edit-texteditor {
> margin: 1px 0 1px 0;
> }
> /*== the preview block on the right ===*/
> .tc-tiddler-preview-preview {
> transform: scale(0.62);/* defines the zoom scale */
> float: right; 
> position: absolute; 
> top : 9em;  /* sets where the preview appears */
> left : 550px; /* setswhere the preview appears */
> overflow-x: auto;
> overflow-y:auto;
> width: 100%; 
> height:100%;
> max-width : 500px;  
> max-height: 560px; 
> margin: 4px 0px 3px 3px;
> padding: 3px 16px 3px 16px;
> z-index: 1000;  
>  border: 1px solid <>;
> background : <>;
> } 
>
>
> On Tuesday, July 14, 2020 at 11:28:38 PM UTC+2, amreus wrote:
>>
>> This is related to Mat's SideEditor, but I thought not on-topic so I 
>> started a new topic. 
>>
>> So would it be possible to make a "Side Preview" plugin? So instead of 
>> floating a side editor, the normal editor is used but a small (tiny?), live 
>> preview window is floated over the sidebar when the tiddler is being 
>> edited? Sort of like the preview when you hover over the Windows taskbar.
>>
>>
>>
>>
>>

-- 
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/49fa6821-07f7-4c12-8187-d5bbe24e8d74o%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?

2020-07-19 Thread PMario

On Sunday, July 19, 2020 at 7:39:34 AM UTC+2, Eric Shulman wrote:
>
> However... I've also added another param, autostart="yes", which will 
> actually trigger the $action-timeout as soon as it is rendered, even if 
> it's not inside a $button.
> I'm not sure when this param will be useful, and it's best to consider it 
> "experimental" for now.
>

Automatically triggering actions can be very useful, to create eg: 
automatic TW UI tests. ... On the other hand, if done wrong it can be very 
destructive (trust me!). Especially during development, if some action 
variables are not initialized in the right way. 

I did create a <$trigger widget  some 
time ago. It activates defined actions if the widget is rendered. I used it 
to create an automatic test-suite 
for TW navigation actions.

Due to the "potential destructive" nature of the widget, I did use 
"buttons" to switch from 1 test-tiddler to the next one. That's the reason, 
why I didn't promote that widget!

There is also a high risk, to create endless loops, if a triggered action 
causes a redraw of the tiddler elements, that contain the <$trigger widget. 

@Eric. ... I personally would create 2 plugins. 1 with the "useful" timeout 
and 1 with the potentially dangerous "experimental" parameter. 

just my thoughts.
mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/64844999-6ac1-46d7-924a-49e4c317c895o%40googlegroups.com.

[tw5] Re: Formatting based on field value


>
>  
> B-but... why it needs a macro inside? 
>

That last solution of mine did *not *have any macro. A macro is a separate 
"codelet" that starts with "\definition". 
 

> why it can't be just: 
>
> <$list filter="[{!!rating}compare:integer:gt[70]then[green]] 
> ~[{!!rating}compare:integer:gt[50]then[grey]] ~[[red]]" variable=color>
> Rating {{!!rating}}
> 
>

OK, first, I agree that it *ought *to be possible to directly insert the 
color into the span thing. Again, my last solution did kind of do this. But 
there are a few issues with the code you write here above:

I'll get to your exact syntax but first, here is a syntax that is "more 
correct but still faulty":

...
Rating {{!!rating}}
...

The <<..>> syntax is the basic way to call a variable. I suspect this 
doesn't work here because the span reads this one: <>  as if it was 
the closing angle bracket of the span tag. So this is why I, in my initial 
solution, split out the whole span out into a macro.

But you ask why $(...)$ doesn't work. This is because $(..)$ is the syntax 
to call a variable when you are in a place where the variable was not 
created. To see the difference, test this:

\define mymacro()
<$vars fruit=banana>
This says banana: <>
This says apple: $(fruit)$

\end

<$vars fruit=apple>
This says apple: <>
<>


If you do this (no macro)

<$vars fruit=apple>
This says apple: $(fruit)$


...you don't get anything because it is simply not the syntax to use when 
calling the variable. It should be <>.

Your examples also imply a question on the difference between $list and 
$vars. For this specific case, the output from the filter is only one value 
so you can use either, as in your examples. $vars sets a variable to be a 
specific value whereas $list sets a variable to be one value at a time from 
a list of values.

Hope this clarifies.

<:-)

-- 
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/f467577e-a551-4773-be6a-dcbbd56d072do%40googlegroups.com.

[tw5] Re: Time Tracking in TiddlyWiki?