[tw] Re: (TW5) Problem with operator on: subfilter:"sort[created]" ?

2017-02-23 Thread Daniel Cunningham 
Sorry It was when I tried to add a comment above the macro that I threw the 
error.  I need to study up on TW5 comment syntax.

On Thursday, February 23, 2017 at 11:15:35 PM UTC-8, Daniel Cunningham 
wrote:
>
> Uhhh, scratch the "leading whitespace fragility" question.  I need to 
> chase my own sloppiness down...  :-)
>
>
> On Thursday, February 23, 2017 at 10:34:03 PM UTC-8, Daniel Cunningham 
> wrote:
>>
>> Hi Mark,
>>
>> Thanks for that follow-up!  I'm beginning to see (thanks to you and 
>> Mario) how this works.
>>
>> OK, so I now get how you can negate the sort order inside the macro (with 
>> a bang).  And then I see from the docs that the way that expression 
>> evaluates is L-to-R via that "railroad" style filter syntax 
>> .
>>
>> And now I see how you can't get to the juicy inner goodness unless you 
>> explicitly flip that bang in the middle...
>>
>> ...which bothered me.  So I extended your initial idea to allow an 
>> additional parameterization from outside:
>>
>> \define timeline2(limit:"100",format:"DDth  MMM 
>> ",subfilter:"",sortaction"sort",dateField:"modified")
>> 
>> <$list 
>> filter="[!is[system]$subfilter$has[$dateField$]$sortaction$[$dateField$]limit[$limit$]eachday[$dateField$]]">
>>
>> [...]
>>
>> <$macrocall $name="timeline2" subfilter="" 
>> format={{$:/language/RecentChanges/DateFormat}} sortaction="sort" 
>> dateField="created"/>
>>
>> And so, I can make a call using a sortaction of "sort" or "!sort", and 
>> control it from outside.  Which works.  And taught me a lot, so thanks to 
>> you & Mario for investing your time explaining that to me.
>>
>> Finally. some observations and questions for you veterans (keeping in 
>> mind that I'm not at all familiar with the code base yet):
>>
>>- Keep in mind I'm not a "macro-ey" kinda guy.  I'm more of 
>>"function-ey" or "object/method-ey" dude, so I'm sure you should take 
>> this 
>>with a bowling ball sized grain of salf... 
>>- It kind of "bothered" me that the declaration "looks" like it has a 
>>"default parameterization", but does not really.  In other words, when 
>> you 
>>call the macro, if you don't explicitly supply all parameters, it will 
>>fail.  That seems a bit fragile, right?
>>- Death by whitespace:  I found out if there's any leading whitespace 
>>(before the macro definition) the tiddler fails.  Also, if there's any 
>>whitespace in the filter list, it will fail.  Again, trying not to seem 
>>harsh, but it feels rather fragile.  Am I being unfair?
>>- Is this "macro-ey" stuff kind of like the STL in C++?
>>- Is this "fragility" due to the macro mechanism itself?  Or is it a 
>>characteristic of JavaScript?  Or CSS?  Or HTML?  Or some intersection of 
>>those elements?
>>
>>
>> And, again, most of all... THANKS for your explanations, which have been 
>> very useful in helping me to spin up on the awesomeness that is TiddlyWiki!
>>
>>
>>
>> On Thursday, February 23, 2017 at 5:42:43 PM UTC-8, Mark S. wrote:
>>>
>>> Hi Daniel,
>>>
>>> Mario's syntax uses the macrocall widget, which is a somewhat more 
>>> formal way of calling a macro that works better in some situations.
>>>
>>> The problem with the timeline macro is that it doesn't give you access 
>>> to the sorting order (A/D), as you can see in this filter:
>>>
>>> [!is[system]$subfilter$has[$dateField$]*!**sort*[$dateField$]limit[
>>> $limit$]eachday[$dateField$]]
>>>
>>> You can't reach the *!sort* in the macro invocation. You can try 
>>> putting the following into a tiddler, which is modified from the original 
>>> timeline code:
>>>
>>> \define timeline2(limit:"100",format:"DDth MMM ",subfilter:"",
>>> dateField:"modified")
>>> 
>>> <$list filter=
>>> "[!is[system]$subfilter$has[$dateField$]sort[$dateField$]limit[$limit$]eachday[$dateField$]]"
>>> >
>>> 
>>> <$view field="$dateField$" format="date" template="$format$"/>
>>> <$list filter=
>>> "[sameday:$dateField${!!$dateField$}!is[system]$subfilter$sort[$dateField$]]"
>>> >
>>> 
>>> <$link to={{!!title}}>
>>> <>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> \end
>>> <$macrocall $name="timeline2" subfilter="" format={{$:/language/
>>> RecentChanges/DateFormat}} dateField="created"/>
>>>
>>> It seemed to work in my quick test, though I didn't look at dates too 
>>> closely. 
>>>
>>> Good luck!
>>> Mark
>>>
>>>
>>> On Thursday, February 23, 2017 at 4:12:26 PM UTC-8, Daniel Cunningham 
>>> wrote:

 Many thanks, Mario!  I tried that, and it works.  

 But rather than change a shadow tiddler, I elected to put in into a 
 "end-user" tiddler, that I can then place in the sidebar with a 
 "$:tags/SideBar" tag.  That gives me the functionality I was looking for.  
 Also, I won't shoot myself in the foot if core changes during my "learning 
 curve".  :-)

 As a follow-up, the results are still in descending order (same as the 
 original Recent tab functionality).  So,

[tw] Re: (TW5) Problem with operator on: subfilter:"sort[created]" ?

2017-02-23 Thread Daniel Cunningham 
Uhhh, scratch the "leading whitespace fragility" question.  I need to chase 
my own sloppiness down...  :-)


On Thursday, February 23, 2017 at 10:34:03 PM UTC-8, Daniel Cunningham 
wrote:
>
> Hi Mark,
>
> Thanks for that follow-up!  I'm beginning to see (thanks to you and Mario) 
> how this works.
>
> OK, so I now get how you can negate the sort order inside the macro (with 
> a bang).  And then I see from the docs that the way that expression 
> evaluates is L-to-R via that "railroad" style filter syntax 
> .
>
> And now I see how you can't get to the juicy inner goodness unless you 
> explicitly flip that bang in the middle...
>
> ...which bothered me.  So I extended your initial idea to allow an 
> additional parameterization from outside:
>
> \define timeline2(limit:"100",format:"DDth  MMM 
> ",subfilter:"",sortaction"sort",dateField:"modified")
> 
> <$list 
> filter="[!is[system]$subfilter$has[$dateField$]$sortaction$[$dateField$]limit[$limit$]eachday[$dateField$]]">
>
> [...]
>
> <$macrocall $name="timeline2" subfilter="" 
> format={{$:/language/RecentChanges/DateFormat}} sortaction="sort" 
> dateField="created"/>
>
> And so, I can make a call using a sortaction of "sort" or "!sort", and 
> control it from outside.  Which works.  And taught me a lot, so thanks to 
> you & Mario for investing your time explaining that to me.
>
> Finally. some observations and questions for you veterans (keeping in mind 
> that I'm not at all familiar with the code base yet):
>
>- Keep in mind I'm not a "macro-ey" kinda guy.  I'm more of 
>"function-ey" or "object/method-ey" dude, so I'm sure you should take this 
>with a bowling ball sized grain of salf... 
>- It kind of "bothered" me that the declaration "looks" like it has a 
>"default parameterization", but does not really.  In other words, when you 
>call the macro, if you don't explicitly supply all parameters, it will 
>fail.  That seems a bit fragile, right?
>- Death by whitespace:  I found out if there's any leading whitespace 
>(before the macro definition) the tiddler fails.  Also, if there's any 
>whitespace in the filter list, it will fail.  Again, trying not to seem 
>harsh, but it feels rather fragile.  Am I being unfair?
>- Is this "macro-ey" stuff kind of like the STL in C++?
>- Is this "fragility" due to the macro mechanism itself?  Or is it a 
>characteristic of JavaScript?  Or CSS?  Or HTML?  Or some intersection of 
>those elements?
>
>
> And, again, most of all... THANKS for your explanations, which have been 
> very useful in helping me to spin up on the awesomeness that is TiddlyWiki!
>
>
>
> On Thursday, February 23, 2017 at 5:42:43 PM UTC-8, Mark S. wrote:
>>
>> Hi Daniel,
>>
>> Mario's syntax uses the macrocall widget, which is a somewhat more formal 
>> way of calling a macro that works better in some situations.
>>
>> The problem with the timeline macro is that it doesn't give you access to 
>> the sorting order (A/D), as you can see in this filter:
>>
>> [!is[system]$subfilter$has[$dateField$]*!**sort*[$dateField$]limit[
>> $limit$]eachday[$dateField$]]
>>
>> You can't reach the *!sort* in the macro invocation. You can try putting 
>> the following into a tiddler, which is modified from the original timeline 
>> code:
>>
>> \define timeline2(limit:"100",format:"DDth MMM ",subfilter:"",
>> dateField:"modified")
>> 
>> <$list filter=
>> "[!is[system]$subfilter$has[$dateField$]sort[$dateField$]limit[$limit$]eachday[$dateField$]]"
>> >
>> 
>> <$view field="$dateField$" format="date" template="$format$"/>
>> <$list filter=
>> "[sameday:$dateField${!!$dateField$}!is[system]$subfilter$sort[$dateField$]]"
>> >
>> 
>> <$link to={{!!title}}>
>> <>
>> 
>> 
>> 
>> 
>> 
>> 
>> \end
>> <$macrocall $name="timeline2" subfilter="" format={{$:/language/
>> RecentChanges/DateFormat}} dateField="created"/>
>>
>> It seemed to work in my quick test, though I didn't look at dates too 
>> closely. 
>>
>> Good luck!
>> Mark
>>
>>
>> On Thursday, February 23, 2017 at 4:12:26 PM UTC-8, Daniel Cunningham 
>> wrote:
>>>
>>> Many thanks, Mario!  I tried that, and it works.  
>>>
>>> But rather than change a shadow tiddler, I elected to put in into a 
>>> "end-user" tiddler, that I can then place in the sidebar with a 
>>> "$:tags/SideBar" tag.  That gives me the functionality I was looking for.  
>>> Also, I won't shoot myself in the foot if core changes during my "learning 
>>> curve".  :-)
>>>
>>> As a follow-up, the results are still in descending order (same as the 
>>> original Recent tab functionality).  So, to get ascending order, I recon I 
>>> should apply a sort operator to the results of your code segment.  But the 
>>> syntax of your code is very different than that shown in the docs -- can 
>>> you give guidance on this?
>>>
>>> Best,
>>>
>>> -- Daniel
>>>
>>>
>>> On Wednesday, February 22, 2017 at 4:22:50 PM UTC-8, PMario wrote:

[tw] Re: [TW5] plugins "FontAwesome" und "ThirdFlow" updated

2017-02-23 Thread Mat 
On Friday, February 24, 2017 at 7:16:14 AM UTC+1, TheDiveO wrote:
>
> Looks like the embedded font isn't properly used. I tested with FF on 
> Win8.1. Do you have a recent FF version installed? 
>

FF latest version. Same non-result when testing on Chrome latest and Edge 
(probably latest).  Also tried downloading and looking at local, but same 
non-result.

Win10 latest and guess the laptop is maybe 1 year old.

Nobody else experiencing problems to see the special fonts on 
http://thediveo.github.io/TW5FontAwesome/output/fontawesome.html ?

Again, thank you TheDiveO

<:-)

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0201a37f-7acf-46e1-bca7-e64bdf702c51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: (TW5) Problem with operator on: subfilter:"sort[created]" ?

2017-02-23 Thread Daniel Cunningham 
Hi Mark,

Thanks for that follow-up!  I'm beginning to see (thanks to you and Mario) 
how this works.

OK, so I now get how you can negate the sort order inside the macro (with a 
bang).  And then I see from the docs that the way that expression evaluates 
is L-to-R via that "railroad" style filter syntax 
.

And now I see how you can't get to the juicy inner goodness unless you 
explicitly flip that bang in the middle...

...which bothered me.  So I extended your initial idea to allow an 
additional parameterization from outside:

\define timeline2(limit:"100",format:"DDth  MMM 
",subfilter:"",sortaction"sort",dateField:"modified")

<$list 
filter="[!is[system]$subfilter$has[$dateField$]$sortaction$[$dateField$]limit[$limit$]eachday[$dateField$]]">

[...]

<$macrocall $name="timeline2" subfilter="" 
format={{$:/language/RecentChanges/DateFormat}} sortaction="sort" 
dateField="created"/>

And so, I can make a call using a sortaction of "sort" or "!sort", and 
control it from outside.  Which works.  And taught me a lot, so thanks to 
you & Mario for investing your time explaining that to me.

Finally. some observations and questions for you veterans (keeping in mind 
that I'm not at all familiar with the code base yet):

   - Keep in mind I'm not a "macro-ey" kinda guy.  I'm more of 
   "function-ey" or "object/method-ey" dude, so I'm sure you should take this 
   with a bowling ball sized grain of salf... 
   - It kind of "bothered" me that the declaration "looks" like it has a 
   "default parameterization", but does not really.  In other words, when you 
   call the macro, if you don't explicitly supply all parameters, it will 
   fail.  That seems a bit fragile, right?
   - Death by whitespace:  I found out if there's any leading whitespace 
   (before the macro definition) the tiddler fails.  Also, if there's any 
   whitespace in the filter list, it will fail.  Again, trying not to seem 
   harsh, but it feels rather fragile.  Am I being unfair?
   - Is this "macro-ey" stuff kind of like the STL in C++?
   - Is this "fragility" due to the macro mechanism itself?  Or is it a 
   characteristic of JavaScript?  Or CSS?  Or HTML?  Or some intersection of 
   those elements?
   

And, again, most of all... THANKS for your explanations, which have been 
very useful in helping me to spin up on the awesomeness that is TiddlyWiki!



On Thursday, February 23, 2017 at 5:42:43 PM UTC-8, Mark S. wrote:
>
> Hi Daniel,
>
> Mario's syntax uses the macrocall widget, which is a somewhat more formal 
> way of calling a macro that works better in some situations.
>
> The problem with the timeline macro is that it doesn't give you access to 
> the sorting order (A/D), as you can see in this filter:
>
> [!is[system]$subfilter$has[$dateField$]*!**sort*[$dateField$]limit[$limit$
> ]eachday[$dateField$]]
>
> You can't reach the *!sort* in the macro invocation. You can try putting 
> the following into a tiddler, which is modified from the original timeline 
> code:
>
> \define timeline2(limit:"100",format:"DDth MMM ",subfilter:"",
> dateField:"modified")
> 
> <$list filter=
> "[!is[system]$subfilter$has[$dateField$]sort[$dateField$]limit[$limit$]eachday[$dateField$]]"
> >
> 
> <$view field="$dateField$" format="date" template="$format$"/>
> <$list filter=
> "[sameday:$dateField${!!$dateField$}!is[system]$subfilter$sort[$dateField$]]"
> >
> 
> <$link to={{!!title}}>
> <>
> 
> 
> 
> 
> 
> 
> \end
> <$macrocall $name="timeline2" subfilter="" format={{$:/language/
> RecentChanges/DateFormat}} dateField="created"/>
>
> It seemed to work in my quick test, though I didn't look at dates too 
> closely. 
>
> Good luck!
> Mark
>
>
> On Thursday, February 23, 2017 at 4:12:26 PM UTC-8, Daniel Cunningham 
> wrote:
>>
>> Many thanks, Mario!  I tried that, and it works.  
>>
>> But rather than change a shadow tiddler, I elected to put in into a 
>> "end-user" tiddler, that I can then place in the sidebar with a 
>> "$:tags/SideBar" tag.  That gives me the functionality I was looking for.  
>> Also, I won't shoot myself in the foot if core changes during my "learning 
>> curve".  :-)
>>
>> As a follow-up, the results are still in descending order (same as the 
>> original Recent tab functionality).  So, to get ascending order, I recon I 
>> should apply a sort operator to the results of your code segment.  But the 
>> syntax of your code is very different than that shown in the docs -- can 
>> you give guidance on this?
>>
>> Best,
>>
>> -- Daniel
>>
>>
>> On Wednesday, February 22, 2017 at 4:22:50 PM UTC-8, PMario wrote:
>>>
>>> On Wednesday, February 22, 2017 at 11:48:49 PM UTC+1, Daniel Cunningham 
>>> wrote:

 And then what you are saying is that since this is embedded in the 
 timeline macro, any sort criteria I try to apply to "created" will be to 
 no 
 avail?

>>>
>>> Have a look at the docs: http://tiddlywiki.com/#timeline%20Macro
>>>  
>>>

[tw] Re: [TW5] plugins "FontAwesome" und "ThirdFlow" updated

2017-02-23 Thread TheDiveO 
Looks like the embedded font isn't properly used. I tested with FF on 
Win8.1. Do you have a recent FF version installed? 

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f8d6bf6d-37d9-4d32-95bc-90dafaf606bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: The look of tables TW5

2017-02-23 Thread David Szego 
Try putting a non-breaking space between cards:

 

or setting CSS word-break and word-spacing properties:

https://www.w3schools.com/cssref/css3_pr_word-break.asp
https://www.w3schools.com/cssref/pr_text_word-spacing.asp

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5a7b1f00-2260-4193-b9c4-6c5ce420a515%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: red screen of death TW5

2017-02-23 Thread David Szego 
try loading yourfilename.html#: and immediately deleting the Tiddler that's 
crashing you, or at the very least opening it, editing it, and removing the 
$:/tags/Macro tag, or removing the <> call in the text of any 
Tiddler using it so it doesn't get called until you fix it.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9492ad42-34d7-4095-aa13-e825adfad747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] The look of tables TW5

2017-02-23 Thread tejjyid 
I have a table produced by a macro that looks slightly wonky under TW5.






You can see the odd spacing in the North cards; most clearly perhaps in the 
contrast between the erratic spacing of N's diamonds and the tight, even 
spacing of East's clubs. This is actually an improved version thanks to 
"text-align:center". The TWC version - from a string which *should be in 
all material respects identical - looks much more even, withouth any CSS 
intervantion from me.


* I know these words mean little; I had to change the string because TW5 
doesn't easily support cell-level CSS, but all that involved was removing 
some inline CSS wrapping from the red suit symbols and repacing it with an 
"!" so I could switch the colour via tableheader. There are *no* gratuitous 
spaces in the underlying string.

** I wouldn't necessarily believe me either, but I have checked.

I can certainly live with the problem, but I'd like to eliminate it if 
possible.

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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5b1391bc-986b-413d-9e26-ccddf7eb5c3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] red screen of death TW5

2017-02-23 Thread tejjyid 
I'm working on the conversion of my TW's from TWC -> TW5.

I was fiddling with one of my new macros (converted & functional, but 
improveable) and I introduced a syntax error. Bingo, RSOD and I can no 
longer access the tiddler to repair the damage. In fact, I can't access the 
wiki. Fortunately it was small enough to fix by editing the html file with 
a text editor, but I'm pretty sure that's not recommended procedure.

I searched on this in the group and found a discussion suggesting that the 
RSOD won't happen if developer tools are switched on. Not so - developer 
tools were switched on at the time of this RSOD. I also found a suggestion 
that there is an option in the developer tools that needs to be on for this 
to be true, but that appeared to be for Chrome. I'm using, and plan to 
continue using, Firefox. 

Can anybody assist?  

Thanks in anticipation

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7da96617-7e5b-47bb-a1d1-1195025ffc0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: (TW5) Problem with operator on: subfilter:"sort[created]" ?

2017-02-23 Thread 'Mark S.' via TiddlyWiki 
Hi Daniel,

Mario's syntax uses the macrocall widget, which is a somewhat more formal 
way of calling a macro that works better in some situations.

The problem with the timeline macro is that it doesn't give you access to 
the sorting order (A/D), as you can see in this filter:

[!is[system]$subfilter$has[$dateField$]*!**sort*[$dateField$]limit[$limit$]
eachday[$dateField$]]

You can't reach the *!sort* in the macro invocation. You can try putting 
the following into a tiddler, which is modified from the original timeline 
code:

\define timeline2(limit:"100",format:"DDth MMM ",subfilter:"",dateField:
"modified")

<$list filter=
"[!is[system]$subfilter$has[$dateField$]sort[$dateField$]limit[$limit$]eachday[$dateField$]]"
>

<$view field="$dateField$" format="date" template="$format$"/>
<$list filter=
"[sameday:$dateField${!!$dateField$}!is[system]$subfilter$sort[$dateField$]]"
>

<$link to={{!!title}}>
<>






\end
<$macrocall $name="timeline2" subfilter="" format={{$:/language/
RecentChanges/DateFormat}} dateField="created"/>

It seemed to work in my quick test, though I didn't look at dates too 
closely. 

Good luck!
Mark


On Thursday, February 23, 2017 at 4:12:26 PM UTC-8, Daniel Cunningham wrote:
>
> Many thanks, Mario!  I tried that, and it works.  
>
> But rather than change a shadow tiddler, I elected to put in into a 
> "end-user" tiddler, that I can then place in the sidebar with a 
> "$:tags/SideBar" tag.  That gives me the functionality I was looking for.  
> Also, I won't shoot myself in the foot if core changes during my "learning 
> curve".  :-)
>
> As a follow-up, the results are still in descending order (same as the 
> original Recent tab functionality).  So, to get ascending order, I recon I 
> should apply a sort operator to the results of your code segment.  But the 
> syntax of your code is very different than that shown in the docs -- can 
> you give guidance on this?
>
> Best,
>
> -- Daniel
>
>
> On Wednesday, February 22, 2017 at 4:22:50 PM UTC-8, PMario wrote:
>>
>> On Wednesday, February 22, 2017 at 11:48:49 PM UTC+1, Daniel Cunningham 
>> wrote:
>>>
>>> And then what you are saying is that since this is embedded in the 
>>> timeline macro, any sort criteria I try to apply to "created" will be to no 
>>> avail?
>>>
>>
>> Have a look at the docs: http://tiddlywiki.com/#timeline%20Macro
>>  
>>
>>>
>>> Unless... I clone the macro & modfify it to use the "created" field?
>>>
>>
>> Edit: $:/core/ui/SideBar/Recent 
>> 
>>
>> like so: <$macrocall $name="timeline" 
>> format={{$:/language/RecentChanges/DateFormat}} dateField="created"/>
>>
>> and you should be good to go. 
>>
>> have fun!
>> 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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7e045124-c89f-476b-9d3e-6992563bb9c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: (TW5) Problem with operator on: subfilter:"sort[created]" ?

2017-02-23 Thread Daniel Cunningham 
Many thanks, Mario!  I tried that, and it works.  

But rather than change a shadow tiddler, I elected to put in into a 
"end-user" tiddler, that I can then place in the sidebar with a 
"$:tags/SideBar" tag.  That gives me the functionality I was looking for.  
Also, I won't shoot myself in the foot if core changes during my "learning 
curve".  :-)

As a follow-up, the results are still in descending order (same as the 
original Recent tab functionality).  So, to get ascending order, I recon I 
should apply a sort operator to the results of your code segment.  But the 
syntax of your code is very different than that shown in the docs -- can 
you give guidance on this?

Best,

-- Daniel


On Wednesday, February 22, 2017 at 4:22:50 PM UTC-8, PMario wrote:
>
> On Wednesday, February 22, 2017 at 11:48:49 PM UTC+1, Daniel Cunningham 
> wrote:
>>
>> And then what you are saying is that since this is embedded in the 
>> timeline macro, any sort criteria I try to apply to "created" will be to no 
>> avail?
>>
>
> Have a look at the docs: http://tiddlywiki.com/#timeline%20Macro
>  
>
>>
>> Unless... I clone the macro & modfify it to use the "created" field?
>>
>
> Edit: $:/core/ui/SideBar/Recent 
> 
>
> like so: <$macrocall $name="timeline" 
> format={{$:/language/RecentChanges/DateFormat}} dateField="created"/>
>
> and you should be good to go. 
>
> have fun!
> 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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/41c0cc43-6424-4751-829c-161c912420ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] TiddlyWiki plugin: Call WebService.

2017-02-23 Thread Stéphane Delaye 
Hello. The web services are hosted on the same domain as the tiddlywiki HTML 
file. I should not have cordialement cors issues. 

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dd84bc26-0445-4cbc-8dcd-1057f06d2d4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] plugins "FontAwesome" und "ThirdFlow" updated

2017-02-23 Thread Mat 


>
>- the *ThirdFlow* plugin now works with TW 5.1.13 again, after I've 
>added a missing sync adaptor method. Plugin download: 
>http://thediveo.github.io/ThirdFlow/ --
>
>
Even the illustrations are cool!

<:-)
 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/72ee2ca0-723a-4ee0-b712-0a66fc103eec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] plugins "FontAwesome" und "ThirdFlow" updated

2017-02-23 Thread Mat 
Thanks for sharing!  It is probably great stuff but this is how the 
fontawesome demo looks for me on FF win10







On Thursday, February 23, 2017 at 6:33:48 PM UTC+1, TheDiveO wrote:
>
> After a long time away from TW5 I've finally managed to update my two 
> plugins so they work with the recent TW5 version 5.1.13:
>
>- the *FontAwesome* plugin now embedds font version 4.7.0 of the 
>incredibly useful "Font Awesome". Plugin download: 
>http://thediveo.github.io/TW5FontAwesome/ -- if you know FontAwesome 
>then you'll probably know what to do with this plugin.
>- the *ThirdFlow* plugin now works with TW 5.1.13 again, after I've 
>added a missing sync adaptor method. Plugin download: 
>http://thediveo.github.io/ThirdFlow/ -- this plugin helps with 
>developing TW5 plugins mainly from inside a TiddlyWiki itself.
>   - a local nodejs-based TW5 server neatly arranges your plugin 
>   tiddlers in folders, so you don't end up with a flat mess of source 
>   tiddlers you need to put into your source control system.
>   - a release script creates either just your plugin as a single .tid 
>   file for simple import, or a demo TW5 including your shiny plugin.
>   - a sidebar view offers a concise view on just your plugins as well 
>   as their contents.
>   
> Admittedly, I can't promise to have much time to work on and maintain 
> these plugins in the future, I've upgraded them, so I can use them for my 
> own work. Of course, pull requests are always appreciated.
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5793c661-4e13-4300-b9ad-4fac9b689088%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] plugins "FontAwesome" und "ThirdFlow" updated

2017-02-23 Thread Josiah 
Stuff like this deserves UPvotes :-).

Josiah, x

On Thursday, 23 February 2017 18:33:48 UTC+1, TheDiveO wrote:
>
> After a long time away from TW5 I've finally managed to update my two 
> plugins so they work with the recent TW5 version 5.1.13:
>
>- the *FontAwesome* plugin now embedds font version 4.7.0 of the 
>incredibly useful "Font Awesome". Plugin download: 
>http://thediveo.github.io/TW5FontAwesome/ -- if you know FontAwesome 
>then you'll probably know what to do with this plugin.
>- the *ThirdFlow* plugin now works with TW 5.1.13 again, after I've 
>added a missing sync adaptor method. Plugin download: 
>http://thediveo.github.io/ThirdFlow/ -- this plugin helps with 
>developing TW5 plugins mainly from inside a TiddlyWiki itself.
>   - a local nodejs-based TW5 server neatly arranges your plugin 
>   tiddlers in folders, so you don't end up with a flat mess of source 
>   tiddlers you need to put into your source control system.
>   - a release script creates either just your plugin as a single .tid 
>   file for simple import, or a demo TW5 including your shiny plugin.
>   - a sidebar view offers a concise view on just your plugins as well 
>   as their contents.
>   
> Admittedly, I can't promise to have much time to work on and maintain 
> these plugins in the future, I've upgraded them, so I can use them for my 
> own work. Of course, pull requests are always appreciated.
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/cd63-d3f7-4bc1-9f66-cb62b900182b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: How to access my TW from iPhone?

2017-02-23 Thread 'Mark S.' via TiddlyWiki 
>From http://tiddlywiki.com/#ServerCommand , you need to give a command that 
will let other devices see your app, like

--server 8080 $:/core/save/all text/plain text/html "" "" 192.168.0.245


That means you will need to look up the serving machine's local ip number 
(I'm assuming you're on a local wifi or other router).

You can add a username and password, but per the text this is passed in 
plain text, so it's not heavy duty security. 

I'm not a security expert, but I believe you might be able to tell your 
local router to block activities on certain ports, so you have some 
security from the outside world. Of course, this would not prevent other 
users inside your local network from viewing your "site".

Possibly you could encrypt your TW -- I've never tried this on node.js. You 
could then examine your individual tid's and verify that they're encrypted.

Good luck,
Mark


On Wednesday, February 22, 2017 at 3:12:31 PM UTC-8, Matt Groth wrote:
>
> I'm running tiddlywiki on Node.js on my Mac and accessing it by going to 
> http://127.0.0.1:8080/. How can I access this address from my iPhone? 
>
> I'm guessing this will require creating an internet server. How would I do 
> this, and how can I keep it private?
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d744af11-315f-4b96-810d-05e0af668d24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] Re: [TW5-node] How to trigger a rebuild of $__StoryList.tid

2017-02-23 Thread Xavier Cazin 
Captain Packers is right to say that one can insert tiddlers in a running
wiki server. For instance, consider this command:

curl -v  -H "Content-Type: application/json"  -X PUT \
   --data-binary '{ "text": "Some content above the line", "tags":
"[[incoming content]] $:/tags/AboveStory"}' \
 "http://127.0.0.1:8080/recipes/default/tiddlers/MyTiddler;

If a wiki server is running at http://127.0.0.1:8080, issuing this command
in a shell will surely create (or replace) a tiddler which title is
MyTiddler and which content will appear above the Story List.

More interesting things can be done as soon as you add fields to be
processed by a template :

curl -v  -H "Content-Type: application/json"  -X PUT \
   --data-binary '{ "text": "{{||A template to handle data}}", "tags":
"[[incoming data]] $:/tags/AboveStory", "data1":"whatever" }' \
 "http://127.0.0.1:8080/recipes/default/tiddlers/MyDataTiddler1;

Now, I'm not sure that placing such tiddlers in the Story List is a good
idea. If we want them to be visible as soon as they are loaded, we may be
better off giving them a tag that make them appear at a known place (like
on the side bar).

X.

-- Xavier Cazin

On Thu, Feb 23, 2017 at 4:15 AM, Riz  wrote:

> You got to restart the server. That does not mean you have to do it
> manually. Try using something like nodemon to watch
> the folder and restart when there are changes.
>
> On Thursday, 23 February 2017 01:47:39 UTC+5:30, Captain Packers wrote:
>>
>> the actual contents of $__StoryList.tid on the server
>
> --
> 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 post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywiki/a607cabd-cabe-4457-91cc-4ca325684cb0%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CADeSwYM0YWPMgSFmZZY_2LDw21QZszji%3DCH2Y%2BTNkO3baMqd6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[tw] [TW5] plugins "FontAwesome" und "ThirdFlow" updated

2017-02-23 Thread TheDiveO 
After a long time away from TW5 I've finally managed to update my two 
plugins so they work with the recent TW5 version 5.1.13:

   - the *FontAwesome* plugin now embedds font version 4.7.0 of the 
   incredibly useful "Font Awesome". Plugin download: 
   http://thediveo.github.io/TW5FontAwesome/ -- if you know FontAwesome 
   then you'll probably know what to do with this plugin.
   - the *ThirdFlow* plugin now works with TW 5.1.13 again, after I've 
   added a missing sync adaptor method. Plugin download: 
   http://thediveo.github.io/ThirdFlow/ -- this plugin helps with 
   developing TW5 plugins mainly from inside a TiddlyWiki itself.
  - a local nodejs-based TW5 server neatly arranges your plugin 
  tiddlers in folders, so you don't end up with a flat mess of source 
  tiddlers you need to put into your source control system.
  - a release script creates either just your plugin as a single .tid 
  file for simple import, or a demo TW5 including your shiny plugin.
  - a sidebar view offers a concise view on just your plugins as well 
  as their contents.
  
Admittedly, I can't promise to have much time to work on and maintain these 
plugins in the future, I've upgraded them, so I can use them for my own 
work. Of course, pull requests are always appreciated.

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/39a9f1c6-8255-4aa9-a340-5340c7b8d525%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [BETA] Noteself android app

2017-02-23 Thread Danielo Rodríguez 


El lunes, 20 de febrero de 2017, 16:43:53 (UTC+1), The Bo escribió:
>
> It works like a charm. I will continue testing and give you a more 
> detailed feedback.
>
> I already love it! :)
>

Thank you very much The Bo. Glad you are enjoying it. Are you using the 
share-with capabilities?

Regards 

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/719a0edd-ca4d-4aaa-a73f-abcc384d45a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Kinship, Genealogy & Family Trees ... Observations & Request

2017-02-23 Thread Josiah 
Ciao David

Thanks!

I'll work-up a decent brief on this over the next few days. 

Best wishes
Josiah

On Wednesday, 22 February 2017 02:54:33 UTC+1, David Szego wrote:
>
> Being an amateur geneaologist, I'd be very interested in seeing your 
> formal procedure. FWIW, I currently use TW to index all of the LDS 
> microfilm scans with my ancestral records ... it would be great to be able 
> to import a GEDCOM, display it, and cross-reference the record to the 
> person, all in TW. 
>
> Maybe I'll tackle that after I'm finished Cardo 1.0! ;->
>
> Cheers,
> David.
>
>
> On Monday, 20 February 2017 11:10:49 UTC-5, Josiah wrote:
>>
>> It seems to me that genealogical trees should be doable in TW.
>>
>> I should emphasise I don't have the programming skill to actually do it.
>>
>> *But I thought others might find it an interesting delimited challenge.*
>>
>> WHY am I interested? Because I am an anthropologist. And anthropologists 
>> know lots about kinship systems. And TW could serve as an elegant, 
>> minimalist way to record and document kinship relationships, I believe.
>>
>> Kinship diagrams are in one way very easy. They are simply branching 
>> hierarchies of "DESCENT". BUT also central to them is the role of 
>> "AFFINITY" (marriage). 
>>
>> So what you have is a FUSION of DESCENT lines through MARRIAGE. So its 
>> never ONE descent line.
>>
>> This is why Mat's interesting recent experiment using forking lists 
>> () and smart CSS hits a limit. It can't cope with the  arbitrary 
>> crossing in of affines (relatives by marriage) who create ADDITIONAL 
>> HIERARCHIES.
>>
>> I'm sure there could be a way to do this in TW without having to resort 
>> to overly complex solutions. The logic in genealogical trees is not 
>> infinitely complex.
>>
>> If anyone is interested I can layout a formal procedure for constructing 
>> them anthropologists use.
>>
>> Technical note: Western style genealogical trees are generally presented 
>> TOP DOWN from ancestors. Anthropologist work from "EGO", i.e. a specific 
>> person and depict the relationships UP & DOWN from there. The final 
>> diagrams are IDENTICAL, but the mode of construction is different. Its 
>> perhaps worth noting that construction from "EGO" gives a very clear 
>> procedure because its always determinate.
>>
>>
>>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5b9f78a9-364f-4cf6-a2fa-b59d85135390%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] TiddlyWiki plugin: Call WebService.

2017-02-23 Thread Jed Carty 
They use a third party service called rss2json 
(https://rss2json.com/#rss_url=https%3A%2F%2Fnews.ycombinator.com%2Frss) to 
get around the problems, but it wouldn't work as a general solution and I 
don't like relying on things like that.

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1f61a4fd-1965-4a0e-a0f8-bfcca49320b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] TiddlyWiki plugin: Call WebService.

2017-02-23 Thread Dragon Cotterill 
On Thursday, 23 February 2017 12:24:51 UTC, Jed Carty wrote:
>
> I have looked into making things like this work, but browser security 
> makes it difficult. I made a widget somewhere that lets you make xmlhttp 
> requests but for many uses there are CORS problems that prevent it from 
> working.
>

Just as a suggestion, but you might want to have a look at 
https://github.com/55sketch/simple-rss to see how they handle CORS issues 
there. 

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1d7f5624-b2f2-44dc-ba80-e9db23c48475%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: [TW5] TiddlyWiki plugin: Call WebService.

2017-02-23 Thread Jed Carty 
I have looked into making things like this work, but browser security makes 
it difficult. I made a widget somewhere that lets you make xmlhttp requests 
but for many uses there are CORS problems that prevent it from working.

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/029f3cdc-4952-41c3-96c5-532c399b74ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw] Re: Tagging a tiddler and changing color field in one move

2017-02-23 Thread Matabele 
Hi

Unfortunately, the box widths and sizes are set with css styles. Although 
this worked fro the version used on the demo site -- the css has been 
messed up for more recent editions of TW5.

regards

On Monday, 20 February 2017 21:29:21 UTC+2, dlu...@emich.edu wrote:
>
> Matbele,
>
> I just discovered your simple tagger and really like it. 
>
> I'm wondering, however, if you can tell me why the height of the 
> add/remove input text box in my wiki is so much taller than yours? See 
> images below.
>
> Mine
>
>
> 
>
>
> Yours
>
>
> 
>
>
> Do you know what controls this and how to adjust it?
>
>
> I did not make any changes to your plugin. Just imported via drag and drop 
> import.
>
>
> Thanks in advance.
>
>
>
>
>
> On Wednesday, February 24, 2016 at 2:51:28 PM UTC-5, Matabele wrote:
>>
>> Hi Jo
>>
>> Have a look at simple tagger  -- 
>> might meet your requirements.
>>
>> regards
>>
>> On Wednesday, 24 February 2016 19:12:24 UTC+2, jen...@googlemail.com 
>> wrote:
>>>
>>> Hi,
>>>
>>> I like the easy tagging method with Eucalys PopupTagger. Now I have the 
>>> case that I want to change the color field of a tiddler corresponding with 
>>> the tag.
>>>
>>> PopupTagger itself just switches the tag. I thought about a conditional 
>>> template for setting the color, but this only changes the view, not the 
>>> tiddler itself. I know that I probably could use the action-setfield widget 
>>> in combination with a button. But I would like to set the color in the 
>>> background, not with an additional button for what PopupTagger already does.
>>>
>>> Has anyone an idea?
>>>
>>> Thanks
>>> Jo
>>>
>>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1e8ebf80-1986-48c9-8843-4d9d82e7d6ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw] [TW5-node]

2017-02-23 Thread Xavier Cazin 
Captain Packers,

I was thinking about something like replacing

<$list filter="[list[$:/StoryList]]" history="$:/HistoryList"
template="$:/core/ui/ViewTemplate" editTemplate="$:/core/ui/EditTemplate"
storyview={{$:/view}} emptyMessage={{$:/config/EmptyStoryMessage}}/>

by

<$list filter="*[title[Your Incoming Tiddler Title]!haschanged[]]*
[list[$:/StoryList]]" history="$:/HistoryList"
template="$:/core/ui/ViewTemplate" editTemplate="$:/core/ui/EditTemplate"
storyview={{$:/view}} emptyMessage={{$:/config/EmptyStoryMessage}}/>

Not quite satisfying as it would mean that your incoming tiddlers would be
sticky on the page until you change them in some ways. But maybe there is a
more clever use of the filters.

Cheers,
X.

-- Xavier Cazin

On Wed, Feb 22, 2017 at 9:16 PM, Captain Packers  wrote:

> How would you do that?
>
> --
> 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 post to this group, send email to tiddlywiki@googlegroups.com.
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/tiddlywiki/37800c82-ebff-495d-98f4-7f699b8d90ae%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CADeSwYMBRBU3JbC6OPH8bN4sNpUo0svpjDNAkVUE%3Da2F3L3i9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.