[tw5] Re: Filter based on integer field values less than or equal to

[TW Tones]

Joshua,

Can we say the new filter operator is specifically a "title Filter", 
although it is true titles can be many things including non existent, or 
literal values. 

Regards
Tones
On Thursday, 3 December 2020 at 13:23:44 UTC+11 joshua@gmail.com wrote:

> You will be able to do this with core TW5 syntax once the new filter 
> operators with 5.1.23 are released.
>
> With the new "filter[]" operator, each input title is compared to the 
> filter given, and the TITLE of any matches are returned (instead of the 
> result of the subfilter being returned, as in the "subfilter[]" operator). 
> It is still a lot of syntax, though, in the base form:
>
> <$set $name="compareFilter" $value="[get[field_name]compare:integer:lteq  
> [100]]">
> <$list $filter="[all[tiddlers]tag[CompareList]filter]">
>
> <<>
> 
> 
>
> And it gets complicated when you want to change the field or index to 
> compare to, but does offer more flexibility.
>
> Best,
> Joshua F
>
> On Monday, November 30, 2020 at 1:43:21 PM UTC-8 History Buff wrote:
>
>> I agree that Joshua's plugin is much easier and clearer to use. Took me 
>> two minutes to install and implement exactly what I needed. At least for 
>> the way my brain works, it's much more intuitive.
>>
>> Damon
>>
>> On Monday, November 30, 2020 at 12:06:31 PM UTC-7 scarab...@gmail.com 
>> wrote:
>>
>>> Eric,
>>> Great tips there! I'll still recommend Joshua Fontany plugin, however, 
>>> for clarity and ease of use.
>>>
>>> Another tip on top of Tones comment; Looping through a list will 
>>> automatically overwrite the variable "currentTiddler", so if you want to 
>>> retain access to the tiddler you are working in, you will have to use the 
>>> "variable" argument in the list:
>>>
>>> E.g.:
>>> /* without 'variable' */
>>> <$list filter="[range[1,10]]">
>>> <>
>>> 
>>> /* output: 1 2 3 4 5 6 7 8 9 10 */
>>>
>>> /* with 'variable' */
>>> <$list filter="[range[1,10]]" variable="mynumber">
>>> <>:<>
>>> 
>>> /* output: 1:MyTitle 2:MyTitle 3:MyTitle 4:MyTitle 5:MyTitle 6:MyTitle 
>>> 7:MyTitle 8:MyTitle 9:MyTitle 10:MyTitle */
>>>
>>>
>>> On Sunday, November 29, 2020 at 6:41:58 PM UTC-8 TW Tones wrote:
>>>
 History 1Buff,

 I will just add to Erics note that when you cause the value of a field 
 or macro etc.. to be available as the result of a filter each item, is 
 considered a "title" even if their is not a tiddler with that title.

 Eg;
 <$list filter="[range[1,10]]">

 
 In side the list the currentTiddler title will be 1,2,3 - 10

 Regards
 Tones

 On Monday, 30 November 2020 at 07:19:43 UTC+11 Eric Shulman wrote:

> On Wednesday, September 30, 2020 at 1:34:39 PM UTC-7 
> scarab...@gmail.com wrote:
>
>> I'm looking for a way to get tiddlers based on comparing integer 
>> fields existing in them. This filter works:
>> [myfieldOne[2]myfieldTwo[2]]
>> I'd like something like:
>> [myfieldOne[lteq[2]]myfieldTwo[lteq[2]]]  
>> I know there are compare operators (
>> https://tiddlywiki.com/#compare%20Operator), but I haven't figured 
>> out how to use it to filter the lists.
>>
>
> To compare a single field value with an integer, returning the tiddler 
> title:
>
> [get[myfieldOne]compare:integer:lteq[2]then]
>
> To compare two different field values with integers, returning the 
> tiddler title:
>
> [get[myfieldOne]compare:integer:lteq[2]thenget[myfieldTwo]compare:integer:lteq[2]then]
>
> Note that each field must exist AND have a value (i.e., not blank)
>
> enjoy,
> -e
>


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

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[TW Tones]

Mark,

I have followed your code through, More testing but it seems to all make 
sense to me now, It would be great if we could turn such code into a 
hierarchy chart that also recognised the list re-iterations. The 
information is all there so automation would be possible. In this case I 
can use the decimals in the range operator to satisfy the OT.

Thank you

Regards
Tones

On Thursday, 3 December 2020 at 17:05:17 UTC+11 TW Tones wrote:

> Testing,
>
> Nice work, It takes a bit to follow the code, but I am sure I will learn 
> something, thanks so much.
>
> You may see it in a Unicode database soon.
>
> Tones
>
>
> On Thursday, 3 December 2020 at 16:53:47 UTC+11 Mark S. wrote:
>
>> Here's a recursive version that that can be any length of hex. Lightly 
>> tested. Hopefully it's working OK.
>>
>> \define hex2dec2(byte,mult:1)
>> <$vars 
>> myfilter="[search-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
>> <$list filter="
>> [<__byte__>subfilter] 
>> =[<__mult__>]
>> +[product[]]
>> "/>
>> 
>> \end
>> \define hex2dec-r(hex,mult)
>> <$list filter="[<__mult__>] =16 +[product[]]" variable="mult">
>> <$list filter="[<__hex__>split[]nth[1]]" variable="byte">
>> <$list filter="[<__hex__>split[]rest[]join[]]" variable="hex"
>> emptyMessage="<$macrocall $name=hex2dec2 byte=<<__hex__>> 
>> mult=<<__mult__>> />"
>> >
>> <$macrocall $name=hex2dec2 byte=<> mult=<<__mult__>> />
>> <$macrocall $name="hex2dec-r" hex=<> mult=<> />
>> 
>> \end
>> \define hex2dec-setup(hex)
>> <$list filter="[<__hex__>split[]reverse[]join[]]" variable=rhex>
>> <$macrocall $name=hex2dec-r hex=<> mult=1 />
>> 
>> \end
>> \define hex2dec(hex)
>> <$wikify text="<>" name=dec>
>> <$list filter="[enlistsum[]]"/>
>> 
>> \end
>>
>> <>
>>
>>
>>
>> On Wednesday, December 2, 2020 at 5:42:55 PM UTC-8 TW Tones wrote:
>>
>>> Mark,
>>>
>>> Good start. I was thinking how to get 16^0 16^1 16^2 and 16^3 and you 
>>> have hard coded it. If moving to a recursive process we may be able to 
>>> handle variable length hex.
>>>

>>>

-- 
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/bd1d8b52-c8d2-47e6-9214-21a31ca27054n%40googlegroups.com.

[tw5] Re: Using TiddlyWiki for fact-based information modelling and database engineering ???

[TW Tones]

Bob,

Very interesting. I can see plenty of ways to implement and automate the 
data model but need to digest the the meaning of each element and how to 
support discovery. Are there any examples or databases using this method we 
could get an example of?

I have a few ex-CSIRO's staff in my friend and acquaintance circles. 
Retirement of people with broad and deep knowledge is a creative and 
productive opportunity, so often neglected.

I imagine there may be information found in various domains that could be 
used to pre-populate such a database.

I have considered in depth expert systems learning, particularly in complex 
technical support areas, when the act of solving problems. builds a 
repository of knowledge and uses analytics and actual use to strengthen the 
expert system. I imagine this solution could be similar. The idea is to use 
the information so far and add when a gap is found, but with the gaps 
filled in a reusable way and when the answer/element exists promote the 
path taken to find an answer/mpodel according to its effectiveness. In 
effect providing conditional multi-dimensional decision trees, that respond 
to future interactions.

Only once a larger dataset exists can we start to derive new methods and 
mechanisms with less effort.

Regards
Tones 


On Thursday, 3 December 2020 at 16:00:47 UTC+11 bob...@gmail.com wrote:

> Colleagues,
>
> all this thinking started by Charlie's initial posting, has led me to 
> begin building a simple TW utilising the Toulmin Argument Model for 
> representing links and associations between TW tiddlers. This is something 
> I have been planning to do for some time, now that I am 'retired' I have 
> the time.
>
> My reasoning is that a completed statement represents the context in which 
> the link between Ground and Claim can be made. This then also supports many 
> different reasons for creating an association between a set of Grounds and 
> Claims each one providing a single instance of context in which the 
> association is deemed valid.
>
> My thoughts so far:
> A statement can be considered like an IF...THEN statement but more 
> complicated due to the additional elements, Warrant, Backing, Rebuttal and 
> Qualifier. The IF part represents the Ground and the THEN part the Claim.
>
> The Qualifier could be a percentage value or some other statement of 
> possibility/plausibility.
>
> Not all elements need to be utilised in any statement, only those that 
> make sense for that particular statement.
>
> Elements can be re-used between statements
>
> Statements can be collected together into a domain of thought or 
> applicability. Thus a single TW could cater for many domains.
>
> Each element is represented by its own tiddler and all tiddlers for a 
> statement are linked together to form the completed statement. Links are 
> stored as Field values in the statement tiddler and also in a Statement 
> field of each element tiddler as the links are essentially many-to-many in 
> ER terms.
>
> Quandries:
>
> How to handle content elements not text? Images, audio, video, etc...
>
> How to produce an 'active' instance of the domain, ie. an instance that 
> functions follow some reasoning mechanism (ie. forward chaining...)
>
> Shared TW:
>
> http://turtlelane.com.au/Development/ToulminModel/toulmin.html
>
> Happy to have your input/thoughts/etc.
>
> bobj
>
> On Wednesday, 2 December 2020 at 15:30:11 UTC+11 Charlie Veniot wrote:
>
>> Like misery, hyperactive-firing-on-all-cylinders synapses love company ...
>>
>> Although right here in this group is fine by me, I'm interested wherever 
>> discussion happens.
>>
>> On Tuesday, December 1, 2020 at 11:30:48 PM UTC-4 bob...@gmail.com wrote:
>>
>>> Charlie, Tones, TiddlyTweeter
>>>
>>> first off, I hold you personally responsible for firing up my dormant 
>>> synapses. Thanks for that, you have provided renewed impetus for me to 
>>> continue pondering these issues, which I essentially ceased to do in any 
>>> meaningful way since I left my research position at CSIRO (the Federal 
>>> Government's research body in Australia). A dormant area of my brain has 
>>> reawakened :-) This will also require me to unbox my library so suitable 
>>> books can be re-queried (all my books are in storage as we have been living 
>>> most of the time in South Korea for the past decade. Corona has left us 
>>> 'stranded' in Sydney).
>>>
>>> I will respond to the recent postings but, like Tones, need to think 
>>> things through a bit more rather than provide a rambling nonsense of ideas 
>>> and thoughts.
>>>
>>> One thought though. Maybe it is time to take discussion outside of this 
>>> group. Not that I want to disenfranchise anybody but the discussion has 
>>> wider ramifications/application than Tiddlywiki. It also can be applied to 
>>> Mediawiki and even Bill Atkinson's original Hypercard and its offshoots. 
>>> Also, this discussion can then take advantage to TW's linking facility, 
>>> etc. Just a thought.
>>>
>>> 

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[TW Tones]

Testing,

Nice work, It takes a bit to follow the code, but I am sure I will learn 
something, thanks so much.

You may see it in a Unicode database soon.

Tones


On Thursday, 3 December 2020 at 16:53:47 UTC+11 Mark S. wrote:

> Here's a recursive version that that can be any length of hex. Lightly 
> tested. Hopefully it's working OK.
>
> \define hex2dec2(byte,mult:1)
> <$vars 
> myfilter="[search-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
> <$list filter="
> [<__byte__>subfilter] 
> =[<__mult__>]
> +[product[]]
> "/>
> 
> \end
> \define hex2dec-r(hex,mult)
> <$list filter="[<__mult__>] =16 +[product[]]" variable="mult">
> <$list filter="[<__hex__>split[]nth[1]]" variable="byte">
> <$list filter="[<__hex__>split[]rest[]join[]]" variable="hex"
> emptyMessage="<$macrocall $name=hex2dec2 byte=<<__hex__>> 
> mult=<<__mult__>> />"
> >
> <$macrocall $name=hex2dec2 byte=<> mult=<<__mult__>> />
> <$macrocall $name="hex2dec-r" hex=<> mult=<> />
> 
> \end
> \define hex2dec-setup(hex)
> <$list filter="[<__hex__>split[]reverse[]join[]]" variable=rhex>
> <$macrocall $name=hex2dec-r hex=<> mult=1 />
> 
> \end
> \define hex2dec(hex)
> <$wikify text="<>" name=dec>
> <$list filter="[enlistsum[]]"/>
> 
> \end
>
> <>
>
>
>
> On Wednesday, December 2, 2020 at 5:42:55 PM UTC-8 TW Tones wrote:
>
>> Mark,
>>
>> Good start. I was thinking how to get 16^0 16^1 16^2 and 16^3 and you 
>> have hard coded it. If moving to a recursive process we may be able to 
>> handle variable length hex.
>>
>>>
>>

-- 
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/5c7a0bb5-5b9c-4c26-b4fd-a6f70da93508n%40googlegroups.com.

[tw5] Re: Step through a list of tiddlers using shortcut keys - the focus is lost

[Mohammad]

HI Saq,
 Many thanks for your solution. Works great!

In my original code I used $vars + filter {{{}}} instead of $wikify but it 
also does not work see

\define stateTid()  tt
\define myTag() HelloThere

\define next() <$action-setfield $tiddler=<> 
text=<> />
\define previous() <$action-setfield $tiddler=<> 
text=<> />

<$vars currentTid  ={{{ [get[text]] ~[tagfirst[]] }}} >
<$vars previousTid ={{{ [tagbefore] }}}
   nextTid ={{{ [tagafter]}}} >

<$keyboard key="right" actions=<> >
<$keyboard key="left" actions=<> >


{{tt}}







But your solution did the trick!


The <$wikify> forces all content within it to be refreshed, and your div 
> looses focus.
>
> \define stateTid()  state-tiddler
> \define myTag() HelloThere
>
>
> \define next() 
> <$vars currentTid={{{[get[text]]}}}>
> <$action-setfield $tiddler=<> text={{{ 
> [tagafter]  ~[tagfirst[]]}}} />
> 
> \end
>
> \define previous()
> <$vars currentTid={{{[get[text]]}}}>
> <$action-setfield $tiddler=<> text={{{ 
> [tagbefore] ~[taglast[]]  }}} />
> 
> \end
>
> <$keyboard key="right" actions=<> >
> <$keyboard key="left"  actions=<> >
>  tabindex=1>
> * Current tid:  <$text text={{{ [get[text]] }}}>/>
>
> 
> 
> 
>
>
> <$list filter="[tag]"/>
>
> شب بخیر  
>

:-) :-)

It is 9:25 A.M now here, so Good Morning!

Cheers
Mohammad
 

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

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

['Mark S.' via TiddlyWiki]

Here's a recursive version that that can be any length of hex. Lightly 
tested. Hopefully it's working OK.

\define hex2dec2(byte,mult:1)
<$vars 
myfilter="[search-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
<$list filter="
[<__byte__>subfilter] 
=[<__mult__>]
+[product[]]
"/>

\end
\define hex2dec-r(hex,mult)
<$list filter="[<__mult__>] =16 +[product[]]" variable="mult">
<$list filter="[<__hex__>split[]nth[1]]" variable="byte">
<$list filter="[<__hex__>split[]rest[]join[]]" variable="hex"
emptyMessage="<$macrocall $name=hex2dec2 byte=<<__hex__>> mult=<<__mult__>> 
/>"
>
<$macrocall $name=hex2dec2 byte=<> mult=<<__mult__>> />
<$macrocall $name="hex2dec-r" hex=<> mult=<> />

\end
\define hex2dec-setup(hex)
<$list filter="[<__hex__>split[]reverse[]join[]]" variable=rhex>
<$macrocall $name=hex2dec-r hex=<> mult=1 />

\end
\define hex2dec(hex)
<$wikify text="<>" name=dec>
<$list filter="[enlistsum[]]"/>

\end

<>



On Wednesday, December 2, 2020 at 5:42:55 PM UTC-8 TW Tones wrote:

> Mark,
>
> Good start. I was thinking how to get 16^0 16^1 16^2 and 16^3 and you have 
> hard coded it. If moving to a recursive process we may be able to handle 
> variable length hex.
>
>>
>

-- 
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/83a31e68-8b4a-49c7-bce6-3cc5ebc6c761n%40googlegroups.com.

[tw5] Re: TW-Shiraz plugin 2.1.2: Stable release

[Mohammad]

Springer,
 There is two points here to note
1. If the table is sorted using tiddler name this may cause by adding a new 
row you may loose focus as new table entry causes a dynamic sort (so pay 
attention to this)
2. The clone feature of core navigate to new tiddler, so you need to have 
your own clone button (e.g. create a new tiddler but do not navigate to it.

You have your own clone button you have to use *action-createtiddler*

See https://tiddlywiki.com/prerelease/#ActionCreateTiddlerWidget

The *action-createtiddler* widget is an action widget 
 that creates new 
tiddlers. ActionWidgets  are 
used within triggering widgets such as the ButtonWidget 
.

There are several differences from the tm-new-tiddler message 
:

   - The new tiddler is not automatically displayed in the story river 
   
   - The title of the new tiddler is made available for subsequent 
   operations

Example: 
got to 
create a Test tiddler name: Test with few tags and fields and content
Then create another tiddler with the below code
\define mybase() Test
\define testCreate()
<$action-createtiddler $basetitle=<> $template=<> />
\end

<$button actions=<> >{{$:/core/images/clone-button}}



Click the clone button several times and see the Recent tab to see the new 
cloned tiddlers NO navigation to them no opening in story river.

Now use this code in the template I sent you instead <> use 
<>


Cheers
Mohammad

On Thursday, December 3, 2020 at 4:03:28 AM UTC+3:30 springer wrote:

> Mohammad,
>
> What I imagined was the ability to create a duplicate tiddler "here" 
> without *opening* it, so that editing focus remains on the dynamic table. 
> It would have the feel of "adding a row to the spreadsheet". Still, adding 
> the "clone" button column with just the regular button, in the way you 
> illustrate here, does make it a bit more efficient to use the dynamic table 
> as a springboard for adding tiddlers as needed.
>
> Thanks for the speedy and helpful response!
>
> -Springer
> On Wednesday, December 2, 2020 at 2:35:24 AM UTC-5 Mohammad wrote:
>
>> Hi Springer,
>>  I am happy you like Shiraz and it is useful in your workflow. Dynamic 
>> Tables are highly customizable using templates. 
>>  What you asked is not difficult and you can do yourself without any hack.
>>
>> The content of each column is displayed using column template. So you can 
>> have a column template to display the contents for example as a link or in 
>> red color and so on.
>>
>> Have a look at 
>> https://kookma.github.io/TW-Shiraz/#demo%2Fdynamic-tables-template
>>
>> As a first trial I attached a clone template! Drag and drop the attached 
>> JSON on https://kookma.github.io/TW-Shiraz/#
>> and see how test works!
>>
>> By the way if you could not implement your own template please submit a 
>> ticket here  https://github.com/kookma/TW-Shiraz  
>>
>> On Wednesday, December 2, 2020 at 4:47:58 AM UTC+3:30 springer wrote:
>>
>>> Mohammad,
>>>
>>> As you know, I love Shiraz, and especially the dynamic tables. They are 
>>> now essential to my workflow.
>>>
>>> I realize there's one desirable feature-possibility for dynamic tables 
>>> that would be amazing, and maybe popular enough to be worth requesting from 
>>> you rather than clumsily trying to hack for myself (as I was starting to do 
>>> on the biblio-demo project for compiling quotes... before reminding myself 
>>> that it's too steep a learning curve for me). 
>>>
>>> REQUEST: Let us specify a special column (perhaps one that appears only 
>>> in the table's internal editing mode) that effectively displays a "CLONE 
>>> this tiddler" button for its tiddler row. 
>>>
>>> Once the button is pressed, a new row is suddenly going to show up in 
>>> the dynamic table, and then (I imagine) the cursor should get automatically 
>>> moved into to the first editable field of that newly-created duplicate row, 
>>> for modifying as needed.
>>>
>>> (More fancy would be the option to create the new tiddler with all the 
>>> non-pivotal fields left blank, setting only those fields whose values 
>>> account for its fitting within the filter condition, but that's bells and 
>>> whistles.)
>>>
>>> Such a feature would make it much easier to respond more intuitively to 
>>> the "Oh, I want to add another row (tiddler) that belongs here" moment.
>>>
>>> Best regards and thanks in advance for entertaining the request!
>>>
>>> -Springer
>>> On Friday, November 13, 2020 at 2:44:25 PM UTC-5 Mohammad wrote:
>>>
 *Announcement:Shiraz plugin*
 *Date: Nov 13th, 2020*
 *Release: 2.1.2*
 *Status: Stable*


 Shiraz is now a mature and quite powerful plugin and it can be used as 
 a useful addition to Tiddlywiki empty edition.

 This 

[tw5] Re: Using TiddlyWiki for fact-based information modelling and database engineering ???

[Bob Jansen]

Colleagues,

all this thinking started by Charlie's initial posting, has led me to begin 
building a simple TW utilising the Toulmin Argument Model for representing 
links and associations between TW tiddlers. This is something I have been 
planning to do for some time, now that I am 'retired' I have the time.

My reasoning is that a completed statement represents the context in which 
the link between Ground and Claim can be made. This then also supports many 
different reasons for creating an association between a set of Grounds and 
Claims each one providing a single instance of context in which the 
association is deemed valid.

My thoughts so far:
A statement can be considered like an IF...THEN statement but more 
complicated due to the additional elements, Warrant, Backing, Rebuttal and 
Qualifier. The IF part represents the Ground and the THEN part the Claim.

The Qualifier could be a percentage value or some other statement of 
possibility/plausibility.

Not all elements need to be utilised in any statement, only those that make 
sense for that particular statement.

Elements can be re-used between statements

Statements can be collected together into a domain of thought or 
applicability. Thus a single TW could cater for many domains.

Each element is represented by its own tiddler and all tiddlers for a 
statement are linked together to form the completed statement. Links are 
stored as Field values in the statement tiddler and also in a Statement 
field of each element tiddler as the links are essentially many-to-many in 
ER terms.

Quandries:

How to handle content elements not text? Images, audio, video, etc...

How to produce an 'active' instance of the domain, ie. an instance that 
functions follow some reasoning mechanism (ie. forward chaining...)

Shared TW:

http://turtlelane.com.au/Development/ToulminModel/toulmin.html

Happy to have your input/thoughts/etc.

bobj

On Wednesday, 2 December 2020 at 15:30:11 UTC+11 Charlie Veniot wrote:

> Like misery, hyperactive-firing-on-all-cylinders synapses love company ...
>
> Although right here in this group is fine by me, I'm interested wherever 
> discussion happens.
>
> On Tuesday, December 1, 2020 at 11:30:48 PM UTC-4 bob...@gmail.com wrote:
>
>> Charlie, Tones, TiddlyTweeter
>>
>> first off, I hold you personally responsible for firing up my dormant 
>> synapses. Thanks for that, you have provided renewed impetus for me to 
>> continue pondering these issues, which I essentially ceased to do in any 
>> meaningful way since I left my research position at CSIRO (the Federal 
>> Government's research body in Australia). A dormant area of my brain has 
>> reawakened :-) This will also require me to unbox my library so suitable 
>> books can be re-queried (all my books are in storage as we have been living 
>> most of the time in South Korea for the past decade. Corona has left us 
>> 'stranded' in Sydney).
>>
>> I will respond to the recent postings but, like Tones, need to think 
>> things through a bit more rather than provide a rambling nonsense of ideas 
>> and thoughts.
>>
>> One thought though. Maybe it is time to take discussion outside of this 
>> group. Not that I want to disenfranchise anybody but the discussion has 
>> wider ramifications/application than Tiddlywiki. It also can be applied to 
>> Mediawiki and even Bill Atkinson's original Hypercard and its offshoots. 
>> Also, this discussion can then take advantage to TW's linking facility, 
>> etc. Just a thought.
>>
>> Ciao for now.
>>
>> bobj
>> On Wednesday, 2 December 2020 at 14:19:52 UTC+11 Bob Jansen wrote:
>>
>>> TiddlyTweeter wrote:
>>> "Very good case example (http://cultconv.com/  [footnote---on mobile 
>>> its too minuscule!])."
>>>
>>> yes, I know of the sizing issue on mobile devices. Not sure how to 
>>> handle that other than a redesign which I am loathe to do given usage stats 
>>> (~8,000 per month over last calendar year). The basic design is for 
>>> multiple synchronous channels of information, in this case four 
>>> (video/audio, transcript, table of contents and images with captions). 
>>> Altogether too much for a small screen. Plus on iPhone, the video takes 
>>> over the whole screen anyway.
>>>
>>> bobj
>>>
>>> On Tuesday, 1 December 2020 at 03:50:57 UTC+11 TiddlyTweeter wrote:
>>>
 Ciao bobj

 Very good case example (http://cultconv.com/  [footnote---on mobile 
 its too minuscule!]).

 BTW, I really took to your last point ...

 Throughout all of my research career, the issue that continually crops 
> up is context. I think this is the crucial component to keep things 
> understandable. Yet no agreed understanding of context exists yet we all 
> use it ...
>

 Right. In terms of information design issues there is no algorithm for 
 accurately deriving either "scope of meaning" or "scope of inference 
 (context implying)". Though it is pretty clear on net that within "fields 
 of interest" 

[tw5] Re: Fields other than the default text field being able to be treated also as a textarea?

[Cade Roux]

Thanks, I will check that out once we get through this current release.

We started with TW just being a great way to output a single HTML file of 
data dictionary/build status/testing results to be shared and approved 
instead of Word/Excel document artifacts.  But we treated it as a target 
document output until we had enough time to play with it, see how 
stakeholders responded and learned how to use it.  We wanted to be able to 
pivot away from it if users weren't happy with it.

But now, Instead of treating it as a target where we generate all the lists 
and tiddlers fully formed the way we want them to be presented like you 
might generate multiple HTML pages on a site, we've moved to really using 
it more "natively" in the sense of only exporting very simple data-like 
tiddlers and using filters and macros within TW tiddlers to generate 
information from them.

Thanks,

Cade
On Wednesday, December 2, 2020 at 7:32:58 PM UTC-6 TW Tones wrote:

> Cade,
>
> I have a solution I am proud of that uses all the mechaisiums you are 
> asking for. It is attached. Let me know if you need more instructions.
>
> I am yet to polish it for publication but it is a tool to have local view 
> templates specific to a tiddler, it works by only allowing you to edit the 
> local-viewtemplate field in a multiline editor in edit mode. It gets hidden 
> from the field in edit mode otherwise the you loose the line breaks.
>
>
>- Drop the package local-viewtemplate on a wiki. It does nothing 
>without further action.
>- Edit a tiddler and add a field "local-viewtemplate" with or without 
>a value, click add
>- Now the multiline editor of the local-viewtemplate field appears in 
>edit mode.
>- In this case there is a local view template that will display the 
>fields contents in view mode.
>
> Not only does it demonstrate multiline fields it provides a quick and easy 
> test bed for writing view Template tests that will not appear everywhere.
>
> There is a possibility tiddler may not be saved correctly on node 
> implementations. But I checked right now on Bobexe and it survived a save 
> and reload.
>
> Regards
> Tones
>
>
> On Thursday, 3 December 2020 at 04:19:10 UTC+11 Cade Roux wrote:
>
>> I was wondering if anyone has done anything like this where a tiddler has 
>> another field "promoted" to a "textarea"-type of field like the main text 
>> field so that a tiddler has two text areas when it's in edit mode, where 
>> one is the text of the tiddler and one is the field denoted to be edited in 
>> a textarea instead of a textbox with all the other (shorter) fields.
>>
>> In my particular use case, the second field is directly related to the 
>> first, but an alternate rendering or similar.  In my case, one is HTML and 
>> the other is raw XML or some other related data but they differ such that 
>> they aren't realistically directly transformable from one to the other 
>> within the browser.
>>
>> In the past I have put that text in a separate tiddler that is directly 
>> linked to the first, but I have found over time, that that technique has 
>> grown unwieldy and I have moved many things back into fields in the main 
>> tiddler (including these large bits of text/data - which are just very 
>> difficult to read in edit mode in their fields - they are obviously fine 
>> when transcluded or otherwise used).
>>
>> Thanks in advance,
>>
>> Cade
>>
>

-- 
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/6d0df992-84dd-462f-9691-bd78ff853addn%40googlegroups.com.

[tw5] Re: Avoid TW Desktop backing up Wiki's

[Alfonso Arciniega]

At least 3 times my TW was corrupted (or I modified the TW and I regretted 
it later) in the past year. I was always able to go back to a previous 
version. Definitely I wouldn't disable the backup feature.

This is what I do: Every week (or every X number of days, your preference), 
I delete all previous versions except the last one of each day (i.e. I keep 
the latest version of each weekday) and delete the rest.

Alfonso

On Monday, November 30, 2020 at 10:16:17 AM UTC-7 Cl0d wrote:

> Oh ... 
>
> Thank you !
> On Monday, 30 November 2020 at 02:06:30 UTC+1 Mark S. wrote:
>
>> At least on 0.0.13, each TW file has an "advanced" option in the main TD 
>> console. Click on "advanced" and there is an option to turn off backups.
>>
>> On Sunday, November 29, 2020 at 2:14:29 PM UTC-8 Cl0d wrote:
>>
>>>
>>> Hello everyone,
>>>
>>> I'm using TiddlyDesktop to access my Wiki's and I was looking for a way 
>>> to stop or at least reduce the backups (I wasn't able just to leave the 
>>> path empty). 
>>>
>>> I'm used to "CTRL + S" a lot, so my backup folders get pretty quickly 
>>> big and since I'm storing on my NAS on which I use HDD's, it creates 
>>> useless writings.
>>>
>>> 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/52a29f50-e9c1-4f6c-9115-5ba1fb05f180n%40googlegroups.com.

[tw5] Re: Filter based on integer field values less than or equal to

[Joshua Fontany]

You will be able to do this with core TW5 syntax once the new filter 
operators with 5.1.23 are released.

With the new "filter[]" operator, each input title is compared to the 
filter given, and the TITLE of any matches are returned (instead of the 
result of the subfilter being returned, as in the "subfilter[]" operator). 
It is still a lot of syntax, though, in the base form:

<$set $name="compareFilter" $value="[get[field_name]compare:integer:lteq  
[100]]">
<$list $filter="[all[tiddlers]tag[CompareList]filter]">

<<>



And it gets complicated when you want to change the field or index to 
compare to, but does offer more flexibility.

Best,
Joshua F

On Monday, November 30, 2020 at 1:43:21 PM UTC-8 History Buff wrote:

> I agree that Joshua's plugin is much easier and clearer to use. Took me 
> two minutes to install and implement exactly what I needed. At least for 
> the way my brain works, it's much more intuitive.
>
> Damon
>
> On Monday, November 30, 2020 at 12:06:31 PM UTC-7 scarab...@gmail.com 
> wrote:
>
>> Eric,
>> Great tips there! I'll still recommend Joshua Fontany plugin, however, 
>> for clarity and ease of use.
>>
>> Another tip on top of Tones comment; Looping through a list will 
>> automatically overwrite the variable "currentTiddler", so if you want to 
>> retain access to the tiddler you are working in, you will have to use the 
>> "variable" argument in the list:
>>
>> E.g.:
>> /* without 'variable' */
>> <$list filter="[range[1,10]]">
>> <>
>> 
>> /* output: 1 2 3 4 5 6 7 8 9 10 */
>>
>> /* with 'variable' */
>> <$list filter="[range[1,10]]" variable="mynumber">
>> <>:<>
>> 
>> /* output: 1:MyTitle 2:MyTitle 3:MyTitle 4:MyTitle 5:MyTitle 6:MyTitle 
>> 7:MyTitle 8:MyTitle 9:MyTitle 10:MyTitle */
>>
>>
>> On Sunday, November 29, 2020 at 6:41:58 PM UTC-8 TW Tones wrote:
>>
>>> History 1Buff,
>>>
>>> I will just add to Erics note that when you cause the value of a field 
>>> or macro etc.. to be available as the result of a filter each item, is 
>>> considered a "title" even if their is not a tiddler with that title.
>>>
>>> Eg;
>>> <$list filter="[range[1,10]]">
>>>
>>> 
>>> In side the list the currentTiddler title will be 1,2,3 - 10
>>>
>>> Regards
>>> Tones
>>>
>>> On Monday, 30 November 2020 at 07:19:43 UTC+11 Eric Shulman wrote:
>>>
 On Wednesday, September 30, 2020 at 1:34:39 PM UTC-7 
 scarab...@gmail.com wrote:

> I'm looking for a way to get tiddlers based on comparing integer 
> fields existing in them. This filter works:
> [myfieldOne[2]myfieldTwo[2]]
> I'd like something like:
> [myfieldOne[lteq[2]]myfieldTwo[lteq[2]]]  
> I know there are compare operators (
> https://tiddlywiki.com/#compare%20Operator), but I haven't figured 
> out how to use it to filter the lists.
>

 To compare a single field value with an integer, returning the tiddler 
 title:

 [get[myfieldOne]compare:integer:lteq[2]then]

 To compare two different field values with integers, returning the 
 tiddler title:

 [get[myfieldOne]compare:integer:lteq[2]thenget[myfieldTwo]compare:integer:lteq[2]then]

 Note that each field must exist AND have a value (i.e., not blank)

 enjoy,
 -e

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6aa4848a-92ab-409f-8b90-cb5b83b99c6bn%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[TW Tones]

Mark,

Good start. I was thinking how to get 16^0 16^1 16^2 and 16^3 and you have 
hard coded it. If moving to a recursive process we may be able to handle 
variable length hex.

But it is a little mind bending.

Tones

On Thursday, 3 December 2020 at 08:41:11 UTC+11 Mark S. wrote:

> Here's my first attempt. It uses the 5.1.23 search-replace filter 
> operator. It requires the input to be padded to 4 bytes.
>
> Now that I've done it, I realize it could probably be written with a 
> recursive loop and be open ended (not needing to be padded).
>
> \define hex2dec2(hex)
> <$vars myhex=<<__hex__>> 
> myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
> <$list filter="1 2 3 4" variable="place"><>
> <$list filter="[subfilter] 
> [compare:number:eq[1]then[4096]else[1]] [subfilter] 
> [compare:number:eq[2]then[256]else[1]] [subfilter] 
> [compare:number:eq[3]then[16]else[1]]+[product[]]"/>
> 
> 
> \end
> \define hex2dec(hex)
> <$wikify text="<>" name=dec>
> <$list filter="[enlistsum[]]"/>
> 
> \end
> <>
>
> On Wednesday, December 2, 2020 at 3:34:02 AM UTC-8 TW Tones wrote:
>
>> Mark,
>>
>> On this occasion I need to convert a 4 digit Hex to a decimal, so that I 
>> can use it in the range widget, because we cant generate a range of hex 
>> numbers.
>>
>>>


-- 
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/717db388-89c1-4e69-a0be-dfae63b73933n%40googlegroups.com.

[tw5] Re: Fields other than the default text field being able to be treated also as a textarea?

[TW Tones]

Cade,

I have a solution I am proud of that uses all the mechaisiums you are 
asking for. It is attached. Let me know if you need more instructions.

I am yet to polish it for publication but it is a tool to have local view 
templates specific to a tiddler, it works by only allowing you to edit the 
local-viewtemplate field in a multiline editor in edit mode. It gets hidden 
from the field in edit mode otherwise the you loose the line breaks.


   - Drop the package local-viewtemplate on a wiki. It does nothing without 
   further action.
   - Edit a tiddler and add a field "local-viewtemplate" with or without a 
   value, click add
   - Now the multiline editor of the local-viewtemplate field appears in 
   edit mode.
   - In this case there is a local view template that will display the 
   fields contents in view mode.

Not only does it demonstrate multiline fields it provides a quick and easy 
test bed for writing view Template tests that will not appear everywhere.

There is a possibility tiddler may not be saved correctly on node 
implementations. But I checked right now on Bobexe and it survived a save 
and reload.

Regards
Tones


On Thursday, 3 December 2020 at 04:19:10 UTC+11 Cade Roux wrote:

> I was wondering if anyone has done anything like this where a tiddler has 
> another field "promoted" to a "textarea"-type of field like the main text 
> field so that a tiddler has two text areas when it's in edit mode, where 
> one is the text of the tiddler and one is the field denoted to be edited in 
> a textarea instead of a textbox with all the other (shorter) fields.
>
> In my particular use case, the second field is directly related to the 
> first, but an alternate rendering or similar.  In my case, one is HTML and 
> the other is raw XML or some other related data but they differ such that 
> they aren't realistically directly transformable from one to the other 
> within the browser.
>
> In the past I have put that text in a separate tiddler that is directly 
> linked to the first, but I have found over time, that that technique has 
> grown unwieldy and I have moved many things back into fields in the main 
> tiddler (including these large bits of text/data - which are just very 
> difficult to read in edit mode in their fields - they are obviously fine 
> when transcluded or otherwise used).
>
> Thanks in advance,
>
> Cade
>

-- 
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/d73a2e89-6942-4f1c-9d1b-41dfee05ca22n%40googlegroups.com.


local-viewtemplate.json
Description: application/json

[tw5] Re: [theme] Presenting "Mono" theme

[Anjar]

JD - I think your theme is amazing! It is so fun to work with and it is so 
easy to make things look great!

A small suggestion (which I guess would apply to tiddlywiki in general, not 
just the mono theme) from me is to enhance the print css a little:) After 
some fiddling, I find this nice:

@media print {
@page {
  size: A4;
  margin: 2cm;
}
.tc-sidebar-scrollable, .tc-topbar, .tc-tiddler-controls{
  display: none !important;
}
.tc-titlebar, .tc-tiddler-title{
  position: static;
  top: 0mm;
}
h2.tc-title{
  font-size: xx-large !important;
}
.tc-story-river{
  display: block;
  margin-top: 0mm;
}
.tc-tiddler-frame{
  background-color: white;
  display: block;
}
.tc-tiddler-body{
  page-break-after: always;
}
}


Best,
Anders

lørdag 1. august 2020 kl. 03:14:59 UTC+2 skrev JD:

> Oh wow, thanks for the compliments TT, this is making me want to speed up 
> my update process more and delay some new TW projects (ahaha!)
>
> I'll look into it! 
>
> -jd
>
>
> On Saturday, August 1, 2020 at 5:01:47 AM UTC+9, TiddlyTweeter wrote:
>>
>> Ciao JD
>>
>> Replying as of Late July 2020.
>>
>> I'd like to suggest you make a "Plugin Library" for all your themes. Why? 
>> Because its obvious they are widely appreciated and used. Because having a 
>> single install point makes that efficient. Better for users. Easier for you 
>> to maintain & distribute canonical versions.
>>
>> Best wishes
>> TT
>>
>> On Monday, 4 February 2019 00:08:01 UTC+1, JD wrote:
>>>
>>> Hello everyone,
>>>
>>> JD here, offering a kind of stark theme that incorporates my most 
>>> personal needs for a writing interface:
>>>
>>> [x] Sidebar to the <- left
>>> [x] Built-in mobile layout
>>> [x] Centered story river (when sidebar is closed)
>>> [x] Sidebar segments visibility toggler at Control Panel 
>>> [x] TopLeftBar buttons visibility toggler at Control Panel 
>>> [x] EmptyStoryMessage template
>>> [x] Splashcreen template
>>> [x] TiddlerFrame style
>>> [x] AdvancedSearch tabs on TopRightBar searchbar
>>> [x] TopRightBar searchbar you can create a tiddler from like NTFS or NTFS19
>>> [x] Font scroller button
>>> [x] Day/night palete switcher button
>>>
>>>
>>> *Here is the main conceit of the mobile UI:*
>>>
>>> The main change has been to TopBarLeft and TopBarRight. They are still 
>>> separated, but are now contained in a wrapper, like this:
>>>
>>>
>>> 
>>> 
>>> (items tagged $:/tags/TopLeftBar)
>>> 
>>> 
>>> (items tagged $:/tags/TopRightBar)
>>> 
>>> 
>>>
>>>
>>> On desktop, the wrapper, tc-topbar, is by default arranged in a row... 
>>> but on mobile it has this: flex-wrap: wrap;... so if tc-topbar-left has 
>>> width: 
>>> 100%;, tc-topbar-right will automatically be stacked below it.
>>>
>>>
>>> By combining the left and right topbars, the special class 
>>> tc-adjust-top-of-scroll is now incorporated to both 
>>> the TopBarLeft and TopBarRight templates. This is especially useful for 
>>> mobile UI.
>>>
>>>
>>> I might extract just this bit into the next iteration of 
>>> my MobilePlugin, albeit it will only be for TW5.1.19 and above.
>>>
>>>
>>> You can try it out, and install from here:
>>>
>>>
>>> http://j.d.mono.tiddlyspot.com/
>>>
>>>
>>> A future update would be this:
>>>
>>>
>>> [ ] hoverable buttons <- for next update
>>>
>>> [ ] hoverable topbar on desktop <- for next update
>>>
>>>  and some other stuff I'm forgetting right now
>>>
>>>
>>> I've been using this with BTC's app, and it works so nice so I'm sharing 
>>> this with you all :D
>>>
>>>
>>> -jd
>>>
>>>
>>> P.S.: 
>>>
>>>
>>> Shoutout to BTC and his amazing development! I love it and it's great 
>>> with an automatic GoogleDrive android->desktop syncer
>>>
>>>
>>> Thank you everyone for the inspiration!
>>>
>>>
>>>

-- 
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/587b4790-4044-410b-a0d1-bf2309288775n%40googlegroups.com.

[tw5] Re: Announcement: Modular theme and Maple color palette

[David Gifford]

Added to the toolmap, both the color palette and the theme, in their 
respective categories.

On Wednesday, December 2, 2020 at 3:33:25 PM UTC-6 bimlas wrote:

> Originally, I just wanted to share my own TiddlyWiki theme and color 
> palette with you. Since there are some changes that may not be to 
> everyone’s liking, I wanted to make most things optional. This work has 
> evolved until the theme itself is actually just a framework-like solution 
> that allows the use of optional stylesheet components, and the "in-theme 
> theme" is the sum of these components and their settings.
>
> https://bimlas.gitlab.io/tw5-modular-theme-maple-palette/
>
> I think this solution is flexible enough to even be included in the core. 
> What do you think about this?
>

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

[tw5] Re: Announcement: Modular theme and Maple color palette

[jtech108]

VERY interesting approach...kudos...bimlas.

Thanks!

All the best,
Julio

On Wednesday, December 2, 2020 at 6:15:53 PM UTC-5 Mohammad wrote:

> Great job bimlas! 
>
> Thank you for sharing.
>
> On Thursday, December 3, 2020 at 1:03:25 AM UTC+3:30 bimlas wrote:
>
>> Originally, I just wanted to share my own TiddlyWiki theme and color 
>> palette with you. Since there are some changes that may not be to 
>> everyone’s liking, I wanted to make most things optional. This work has 
>> evolved until the theme itself is actually just a framework-like solution 
>> that allows the use of optional stylesheet components, and the "in-theme 
>> theme" is the sum of these components and their settings.
>>
>> https://bimlas.gitlab.io/tw5-modular-theme-maple-palette/
>>
>> I think this solution is flexible enough to even be included in the core. 
>> What do you think about this?
>>
>

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

[tw5] Re: TW-Shiraz plugin 2.1.2: Stable release

[springer]

Mohammad,

What I imagined was the ability to create a duplicate tiddler "here" 
without *opening* it, so that editing focus remains on the dynamic table. 
It would have the feel of "adding a row to the spreadsheet". Still, adding 
the "clone" button column with just the regular button, in the way you 
illustrate here, does make it a bit more efficient to use the dynamic table 
as a springboard for adding tiddlers as needed.

Thanks for the speedy and helpful response!

-Springer
On Wednesday, December 2, 2020 at 2:35:24 AM UTC-5 Mohammad wrote:

> Hi Springer,
>  I am happy you like Shiraz and it is useful in your workflow. Dynamic 
> Tables are highly customizable using templates. 
>  What you asked is not difficult and you can do yourself without any hack.
>
> The content of each column is displayed using column template. So you can 
> have a column template to display the contents for example as a link or in 
> red color and so on.
>
> Have a look at 
> https://kookma.github.io/TW-Shiraz/#demo%2Fdynamic-tables-template
>
> As a first trial I attached a clone template! Drag and drop the attached 
> JSON on https://kookma.github.io/TW-Shiraz/#
> and see how test works!
>
> By the way if you could not implement your own template please submit a 
> ticket here  https://github.com/kookma/TW-Shiraz  
>
> On Wednesday, December 2, 2020 at 4:47:58 AM UTC+3:30 springer wrote:
>
>> Mohammad,
>>
>> As you know, I love Shiraz, and especially the dynamic tables. They are 
>> now essential to my workflow.
>>
>> I realize there's one desirable feature-possibility for dynamic tables 
>> that would be amazing, and maybe popular enough to be worth requesting from 
>> you rather than clumsily trying to hack for myself (as I was starting to do 
>> on the biblio-demo project for compiling quotes... before reminding myself 
>> that it's too steep a learning curve for me). 
>>
>> REQUEST: Let us specify a special column (perhaps one that appears only 
>> in the table's internal editing mode) that effectively displays a "CLONE 
>> this tiddler" button for its tiddler row. 
>>
>> Once the button is pressed, a new row is suddenly going to show up in the 
>> dynamic table, and then (I imagine) the cursor should get automatically 
>> moved into to the first editable field of that newly-created duplicate row, 
>> for modifying as needed.
>>
>> (More fancy would be the option to create the new tiddler with all the 
>> non-pivotal fields left blank, setting only those fields whose values 
>> account for its fitting within the filter condition, but that's bells and 
>> whistles.)
>>
>> Such a feature would make it much easier to respond more intuitively to 
>> the "Oh, I want to add another row (tiddler) that belongs here" moment.
>>
>> Best regards and thanks in advance for entertaining the request!
>>
>> -Springer
>> On Friday, November 13, 2020 at 2:44:25 PM UTC-5 Mohammad wrote:
>>
>>> *Announcement:Shiraz plugin*
>>> *Date: Nov 13th, 2020*
>>> *Release: 2.1.2*
>>> *Status: Stable*
>>>
>>>
>>> Shiraz is now a mature and quite powerful plugin and it can be used as a 
>>> useful addition to Tiddlywiki empty edition.
>>>
>>> This *stable release* is a bug fix release and distributing under 
>>> Kookma Plugin Library.
>>>
>>>
>>> Code and demo
>>>
>>>- Demo: https://kookma.github.io/TW-Shiraz
>>>- Code: https://github.com/kookma/TW-Shiraz
>>>
>>>
>>>
>>> Star it if you like it and send your feedback!
>>> Documentation proof reading for English is welcome!
>>>
>>>
>>>
>>> --Mohammad
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8d6bc29c-b52e-497a-94e7-3e30105003e9n%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

['Mark S.' via TiddlyWiki]

Ok, cleaned it up a bit:

\define hex2dec2(hex)
<$vars myhex=<<__hex__>> 
myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
<$list filter="1 2 3 4" variable="place">
<$list filter="
[subfilter] 
[compare:number:eq[1]then[4096]else[1]]  
[compare:number:eq[2]then[256]else[1]]  
[compare:number:eq[3]then[16]else[1]]
[compare:number:eq[4]then[1]else[1]]
+[product[]]
"/>


\end
\define hex2dec(hex)
<$wikify text="<>" name=dec>
<$list filter="[enlistsum[]]"/>

\end
<>


On Wednesday, December 2, 2020 at 2:21:30 PM UTC-8 coda coder wrote:

> 10 is the sum of 1 2 3 4

-- 
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/7e7f496c-33db-4ef6-a97f-6934f2de0f7an%40googlegroups.com.

[tw5] Re: Step through a list of tiddlers using shortcut keys - the focus is lost

[Saq Imtiaz]

The <$wikify> forces all content within it to be refreshed, and your div 
looses focus.

\define stateTid()  state-tiddler
\define myTag() HelloThere


\define next() 
<$vars currentTid={{{[get[text]]}}}>
<$action-setfield $tiddler=<> text={{{ 
[tagafter]  ~[tagfirst[]]}}} />

\end

\define previous()
<$vars currentTid={{{[get[text]]}}}>
<$action-setfield $tiddler=<> text={{{ 
[tagbefore] ~[taglast[]]  }}} />

\end

<$keyboard key="right" actions=<> >
<$keyboard key="left"  actions=<> >

* Current tid:  <$text text={{{ [get[text]] }}}>/>






<$list filter="[tag]"/>

شب بخیر  

-- 
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/4e2bf497-10a7-48c9-aab8-83a6a601428en%40googlegroups.com.

[tw5] Re: Announcement: Modular theme and Maple color palette

[Mohammad]

Great job bimlas! 

Thank you for sharing.

On Thursday, December 3, 2020 at 1:03:25 AM UTC+3:30 bimlas wrote:

> Originally, I just wanted to share my own TiddlyWiki theme and color 
> palette with you. Since there are some changes that may not be to 
> everyone’s liking, I wanted to make most things optional. This work has 
> evolved until the theme itself is actually just a framework-like solution 
> that allows the use of optional stylesheet components, and the "in-theme 
> theme" is the sum of these components and their settings.
>
> https://bimlas.gitlab.io/tw5-modular-theme-maple-palette/
>
> I think this solution is flexible enough to even be included in the core. 
> What do you think about this?
>

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

[tw5] Re: Step through a list of tiddlers using shortcut keys - the focus is lost

[Mohammad]

The reason I attached zip file is Google forum does not attached tid files 
(may be it thinks JS code has been attached!)

On Thursday, December 3, 2020 at 2:37:47 AM UTC+3:30 Mohammad wrote:

> I am playing with keyboard shortcuts. attached there are two tiddlers. 
>  
> *Test 01: Works fine*
>
> Drag and drop the Keyboard_01.tid into https://tiddlywiki.com/prerelease
>
> click on the orange box and then use left right arrow keys and see how the 
> number changes inside orange box.
>
> *Keyboard/01*
> \define addup()  <$action-setfield $tiddler=TempTid text={{{ 
> [[TempTid]get[text]add[1]]~[[1]] }}}  />
> \define reducedown() <$action-setfield $tiddler=TempTid text={{{ 
> [[TempTid]get[text]subtract[1]]~[[0]] }}} />
>
> <$keyboard key="right" actions=<>>
> <$keyboard key="left" actions=<>>
>
> 
>
> !! Display me
>
> Temp value: {{TempTid}}
> 
> 
> 
>
>
>
> *Test 02: Focus is lost*
> Drag  and drop the Keyboard_02.tid into https://tiddlywiki.com/prerelease
>
> click on the orange box and use left right arrows and see title appears 
> inside orange box
>
> *Keyboard/02*
> \define stateTid()  state-tiddler
> \define myTag() HelloThere
>
>
> \define next() <$action-setfield $tiddler=<> text={{{ 
> [tagafter]  ~[tagfirst[]]}}} />
> \define previous() <$action-setfield $tiddler=<> text={{{ 
> [tagbefore[$(currentTid)$]] ~[taglast[]]  }}} />
>
> <$wikify name=currentTid text={{{ [get[text]] }}}>
> <$keyboard key="right" actions=<> >
> <$keyboard key="left"  actions=<> >
>  tabindex=1>
>
> * Current tid:  <>
>
>
> 
> 
> 
> 
>
>
> What is the reason? I have to click on the orange box after every 
> Right/Left arrow keys pressed, because the focus is lost.
>
> Ultimate purpose: Transclude a tiddler from a list and step through using 
> Left/Right arrow keys.
>
> --Mohammad
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/81570fd0-ef0c-4af1-be92-8702ee203379n%40googlegroups.com.

[tw5] Step through a list of tiddlers using shortcut keys - the focus is lost

[Mohammad]

I am playing with keyboard shortcuts. attached there are two tiddlers. 
 
*Test 01: Works fine*

Drag and drop the Keyboard_01.tid into https://tiddlywiki.com/prerelease

click on the orange box and then use left right arrow keys and see how the 
number changes inside orange box.

*Keyboard/01*
\define addup()  <$action-setfield $tiddler=TempTid text={{{ 
[[TempTid]get[text]add[1]]~[[1]] }}}  />
\define reducedown() <$action-setfield $tiddler=TempTid text={{{ 
[[TempTid]get[text]subtract[1]]~[[0]] }}} />

<$keyboard key="right" actions=<>>
<$keyboard key="left" actions=<>>



!! Display me

Temp value: {{TempTid}}






*Test 02: Focus is lost*
Drag  and drop the Keyboard_02.tid into https://tiddlywiki.com/prerelease

click on the orange box and use left right arrows and see title appears 
inside orange box

*Keyboard/02*
\define stateTid()  state-tiddler
\define myTag() HelloThere


\define next() <$action-setfield $tiddler=<> text={{{ 
[tagafter]  ~[tagfirst[]]}}} />
\define previous() <$action-setfield $tiddler=<> text={{{ 
[tagbefore[$(currentTid)$]] ~[taglast[]]  }}} />

<$wikify name=currentTid text={{{ [get[text]] }}}>
<$keyboard key="right" actions=<> >
<$keyboard key="left"  actions=<> >


* Current tid:  <>








What is the reason? I have to click on the orange box after every 
Right/Left arrow keys pressed, because the focus is lost.

Ultimate purpose: Transclude a tiddler from a list and step through using 
Left/Right arrow keys.

--Mohammad





-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/cd34bb09-b8a0-4a07-b91a-fb6e44575eb7n%40googlegroups.com.
<>

Re: [tw5] Re: [Request] Numbered lists need some love

[Saq Imtiaz]

I've posted an issue on 
Github: https://github.com/Jermolene/TiddlyWiki5/issues/5186

On Monday, November 30, 2020 at 6:22:57 PM UTC+1 springer wrote:

> +1 on this sentiment. 
> Handling nested ordered lists in the numeric-alpha-roman way Dave suggests 
> is also my preference, and with each wiki project I stumble across the need 
> to reconstruct that css fix (usually at a moment when I really just want to 
> focus on the content).
> -Springer
>
> On Monday, November 30, 2020 at 9:48:31 AM UTC-5 saq.i...@gmail.com wrote:
>
>> @Dave I think there is a good case for including in TW a class that 
>> handles nested numbered lists better.
>>
>> On Monday, November 30, 2020 at 3:36:26 PM UTC+1 David Gifford wrote:
>>
>>> How sad, all these years I thought this was a limitation of TiddlyWiki. 
>>> I had no idea there was such an easy fix with CSS. This really needs to be 
>>> added to the tiddlywiki.com documentation so people are aware of this. 
>>> I will definitely add it to my "documenting TW" file soon. (
>>> https://giffmex.org/gifts/documenting.tw.html)
>>>
>>> Thanks for the help, Saq!
>>>
>>> On Mon, Nov 30, 2020 at 8:18 AM Saq Imtiaz  wrote:
>>>
 Also of interest might be counters
 https://www.w3schools.com/css/css_counters.asp

 On Monday, November 30, 2020 at 3:17:08 PM UTC+1 Saq Imtiaz wrote:

> Dave: I believe all you need for this is the appropriate CSS for 
> nested lists.
> https://www.w3schools.com/cssref/pr_list-style-type.asp
> On Monday, November 30, 2020 at 3:06:59 PM UTC+1 David Gifford wrote:
>
>> Hi all
>>
>> To be honest, this is not really a request for my own personal 
>> projects. I tend to prefer unordered lists myself. This is a request 
>> thinking of new users.
>>
>> Second and subsequent levels of numbered lists just repeat the arabic 
>> numerals. 
>>
>> 1.
>>
>>- 1.
>>
>>
>>- 1.
>>
>> I have a feeling this turns people away from using multiple level 
>> numbered lists in TiddlyWiki. 
>>
>> Would it be possible for someone to create a plugin so that numbered 
>> lists look like this? (no bullets, obviously - the new Google Groups ui 
>> seems to have eliminated indenting as a text formatting option.)
>>
>> 1.
>>
>>- a.
>>   - i.
>>
>> Another nice option would be
>>
>> 1.
>>
>>- 1.1
>>   - 1.1.1
>>   
>> I have no idea if either or both of these are possible. But it would 
>> definitely be a welcome improvement, even as a plugin rather than as a 
>> core 
>> improvement.
>>
>> Perhaps Saq's Editor-Autolists plugin would be the best candidate to 
>> add this kind of functionality? I wonder if that is something he might 
>> consider pursuing. Or would this be better as its own plugin?
>>
>> Thank you all for your consideration. Blessings!
>>
> -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "TiddlyWiki" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/tiddlywiki/ZWwNlhR-9N8/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 tiddlywiki+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/tiddlywiki/ff78cbce-e7db-4e51-8298-c183b4e9d4c9n%40googlegroups.com
  
 
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/94f20f0e-2d11-4670-907f-9775f876adban%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[coda coder]

10 is the sum of 1 2 3 4

On Wednesday, December 2, 2020 at 4:20:52 PM UTC-6 coda coder wrote:

> Mark... I see it. You left some debugging in there: <>
>
> On Wednesday, December 2, 2020 at 4:17:21 PM UTC-6 saq.i...@gmail.com 
> wrote:
>
>> If it helps there is a pad[] operator in the pre-release.
>>
>> On Wednesday, December 2, 2020 at 10:41:11 PM UTC+1 Mark S. wrote:
>>
>>> Here's my first attempt. It uses the 5.1.23 search-replace filter 
>>> operator. It requires the input to be padded to 4 bytes.
>>>
>>> Now that I've done it, I realize it could probably be written with a 
>>> recursive loop and be open ended (not needing to be padded).
>>>
>>> \define hex2dec2(hex)
>>> <$vars myhex=<<__hex__>> 
>>> myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
>>> <$list filter="1 2 3 4" variable="place"><>
>>> <$list filter="[subfilter] 
>>> [compare:number:eq[1]then[4096]else[1]] [subfilter] 
>>> [compare:number:eq[2]then[256]else[1]] [subfilter] 
>>> [compare:number:eq[3]then[16]else[1]]+[product[]]"/>
>>> 
>>> 
>>> \end
>>> \define hex2dec(hex)
>>> <$wikify text="<>" name=dec>
>>> <$list filter="[enlistsum[]]"/>
>>> 
>>> \end
>>> <>
>>>
>>> On Wednesday, December 2, 2020 at 3:34:02 AM UTC-8 TW Tones wrote:
>>>
 Mark,

 On this occasion I need to convert a 4 digit Hex to a decimal, so that 
 I can use it in the range widget, because we cant generate a range of hex 
 numbers.

>
>>

-- 
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/c1848e59-5358-4cc2-bfdd-bd9eb4417346n%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[coda coder]

Mark... I see it. You left some debugging in there: <>

On Wednesday, December 2, 2020 at 4:17:21 PM UTC-6 saq.i...@gmail.com wrote:

> If it helps there is a pad[] operator in the pre-release.
>
> On Wednesday, December 2, 2020 at 10:41:11 PM UTC+1 Mark S. wrote:
>
>> Here's my first attempt. It uses the 5.1.23 search-replace filter 
>> operator. It requires the input to be padded to 4 bytes.
>>
>> Now that I've done it, I realize it could probably be written with a 
>> recursive loop and be open ended (not needing to be padded).
>>
>> \define hex2dec2(hex)
>> <$vars myhex=<<__hex__>> 
>> myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
>> <$list filter="1 2 3 4" variable="place"><>
>> <$list filter="[subfilter] 
>> [compare:number:eq[1]then[4096]else[1]] [subfilter] 
>> [compare:number:eq[2]then[256]else[1]] [subfilter] 
>> [compare:number:eq[3]then[16]else[1]]+[product[]]"/>
>> 
>> 
>> \end
>> \define hex2dec(hex)
>> <$wikify text="<>" name=dec>
>> <$list filter="[enlistsum[]]"/>
>> 
>> \end
>> <>
>>
>> On Wednesday, December 2, 2020 at 3:34:02 AM UTC-8 TW Tones wrote:
>>
>>> Mark,
>>>
>>> On this occasion I need to convert a 4 digit Hex to a decimal, so that I 
>>> can use it in the range widget, because we cant generate a range of hex 
>>> numbers.
>>>

>

-- 
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/83921613-8d13-42bd-9f7b-4d17637fd387n%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[Saq Imtiaz]

If it helps there is a pad[] operator in the pre-release.

On Wednesday, December 2, 2020 at 10:41:11 PM UTC+1 Mark S. wrote:

> Here's my first attempt. It uses the 5.1.23 search-replace filter 
> operator. It requires the input to be padded to 4 bytes.
>
> Now that I've done it, I realize it could probably be written with a 
> recursive loop and be open ended (not needing to be padded).
>
> \define hex2dec2(hex)
> <$vars myhex=<<__hex__>> 
> myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
> <$list filter="1 2 3 4" variable="place"><>
> <$list filter="[subfilter] 
> [compare:number:eq[1]then[4096]else[1]] [subfilter] 
> [compare:number:eq[2]then[256]else[1]] [subfilter] 
> [compare:number:eq[3]then[16]else[1]]+[product[]]"/>
> 
> 
> \end
> \define hex2dec(hex)
> <$wikify text="<>" name=dec>
> <$list filter="[enlistsum[]]"/>
> 
> \end
> <>
>
> On Wednesday, December 2, 2020 at 3:34:02 AM UTC-8 TW Tones wrote:
>
>> Mark,
>>
>> On this occasion I need to convert a 4 digit Hex to a decimal, so that I 
>> can use it in the range widget, because we cant generate a range of hex 
>> numbers.
>>
>>>


-- 
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/f4efb31f-8116-4223-9262-52a312ef6b7fn%40googlegroups.com.

[tw5] Re: Announcement: Modular theme and Maple color palette

[Saq Imtiaz]

Very nicely organized and love the flexibility. 

Just an FYI that it is planned to introduce a new alternative flexbox based 
layout for the core after 5.1.23. 
There might be potential there for incorporating or at least learning from  
some aspects of your approach.
Cheers,
Saq
On Wednesday, December 2, 2020 at 10:33:25 PM UTC+1 bimlas wrote:

> Originally, I just wanted to share my own TiddlyWiki theme and color 
> palette with you. Since there are some changes that may not be to 
> everyone’s liking, I wanted to make most things optional. This work has 
> evolved until the theme itself is actually just a framework-like solution 
> that allows the use of optional stylesheet components, and the "in-theme 
> theme" is the sum of these components and their settings.
>
> https://bimlas.gitlab.io/tw5-modular-theme-maple-palette/
>
> I think this solution is flexible enough to even be included in the core. 
> What do you think about this?
>

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

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[coda coder]

Mark - you're adding 10 (decimal) somewhere.

 -> 65545
 -> 10

On Wednesday, December 2, 2020 at 3:41:11 PM UTC-6 Mark S. wrote:

> Here's my first attempt. It uses the 5.1.23 search-replace filter 
> operator. It requires the input to be padded to 4 bytes.
>
> Now that I've done it, I realize it could probably be written with a 
> recursive loop and be open ended (not needing to be padded).
>
> \define hex2dec2(hex)
> <$vars myhex=<<__hex__>> 
> myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
> <$list filter="1 2 3 4" variable="place"><>
> <$list filter="[subfilter] 
> [compare:number:eq[1]then[4096]else[1]] [subfilter] 
> [compare:number:eq[2]then[256]else[1]] [subfilter] 
> [compare:number:eq[3]then[16]else[1]]+[product[]]"/>
> 
> 
> \end
> \define hex2dec(hex)
> <$wikify text="<>" name=dec>
> <$list filter="[enlistsum[]]"/>
> 
> \end
> <>
>
> On Wednesday, December 2, 2020 at 3:34:02 AM UTC-8 TW Tones wrote:
>
>> Mark,
>>
>> On this occasion I need to convert a 4 digit Hex to a decimal, so that I 
>> can use it in the range widget, because we cant generate a range of hex 
>> numbers.
>>
>>>


-- 
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/0011fd81-7d7b-431c-876d-ce7fb879d563n%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

['Mark S.' via TiddlyWiki]

Here's my first attempt. It uses the 5.1.23 search-replace filter operator. 
It requires the input to be padded to 4 bytes.

Now that I've done it, I realize it could probably be written with a 
recursive loop and be open ended (not needing to be padded).

\define hex2dec2(hex)
<$vars myhex=<<__hex__>> 
myfilter="[split[]nthsearch-replace:g[A],[10]search-replace:g[B],[11]search-replace:g[C],[12]search-replace:g[D],[13]search-replace:g[E],[14]search-replace:g[F],[15]]">
<$list filter="1 2 3 4" variable="place"><>
<$list filter="[subfilter] 
[compare:number:eq[1]then[4096]else[1]] [subfilter] 
[compare:number:eq[2]then[256]else[1]] [subfilter] 
[compare:number:eq[3]then[16]else[1]]+[product[]]"/>


\end
\define hex2dec(hex)
<$wikify text="<>" name=dec>
<$list filter="[enlistsum[]]"/>

\end
<>

On Wednesday, December 2, 2020 at 3:34:02 AM UTC-8 TW Tones wrote:

> Mark,
>
> On this occasion I need to convert a 4 digit Hex to a decimal, so that I 
> can use it in the range widget, because we cant generate a range of hex 
> numbers.
>
>>
>>>

-- 
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/f436d87d-a67d-49e9-ac48-434819708919n%40googlegroups.com.

[tw5] Announcement: Modular theme and Maple color palette

[bimlas]

Originally, I just wanted to share my own TiddlyWiki theme and color 
palette with you. Since there are some changes that may not be to 
everyone’s liking, I wanted to make most things optional. This work has 
evolved until the theme itself is actually just a framework-like solution 
that allows the use of optional stylesheet components, and the "in-theme 
theme" is the sum of these components and their settings.

https://bimlas.gitlab.io/tw5-modular-theme-maple-palette/

I think this solution is flexible enough to even be included in the core. 
What do you think about this?

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/96a8c029-2c1f-4319-a90e-5d46b3ae54b8n%40googlegroups.com.

[tw5] Re: Make editor plugins work for <$edit-text> widgets

[Stobot]

Thanks!

On Wednesday, December 2, 2020 at 3:34:03 PM UTC-5 saq.i...@gmail.com wrote:

> PS: drop the style declaration from the transclude widget as it wont work 
> nor is needed.
>
> On Wednesday, December 2, 2020 at 9:33:20 PM UTC+1 Saq Imtiaz wrote:
>
>> Try this:
>>
>> 
>> .my-editor .tc-editor-toolbar {
>> display:none;
>> }
>> 
>>
>> 
>>
>> <$edit tiddler="$:/temp/testing">
>> <$list 
>> filter="[all[shadows+tiddlers]tag[$:/tags/EditorToolbar]!has[draft.of]]">
>> <$transclude style="height:0px" 
>> tiddler="$:/core/ui/EditTemplate/body/toolbar/button" mode="inline"/>
>> 
>> 
>> 
>>
>

-- 
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/b21a735f-ec6d-4da2-b187-b70277280114n%40googlegroups.com.

[tw5] Re: Make editor plugins work for <$edit-text> widgets

[Saq Imtiaz]

PS: drop the style declaration from the transclude widget as it wont work 
nor is needed.

On Wednesday, December 2, 2020 at 9:33:20 PM UTC+1 Saq Imtiaz wrote:

> Try this:
>
> 
> .my-editor .tc-editor-toolbar {
> display:none;
> }
> 
>
> 
>
> <$edit tiddler="$:/temp/testing">
> <$list 
> filter="[all[shadows+tiddlers]tag[$:/tags/EditorToolbar]!has[draft.of]]">
> <$transclude style="height:0px" 
> tiddler="$:/core/ui/EditTemplate/body/toolbar/button" mode="inline"/>
> 
> 
> 
>

-- 
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/20f181c8-ab70-4d06-ab64-b19514730929n%40googlegroups.com.

[tw5] Re: Make editor plugins work for <$edit-text> widgets

[Saq Imtiaz]

Try this:


.my-editor .tc-editor-toolbar {
display:none;
}



<$edit tiddler="$:/temp/testing">
<$list 
filter="[all[shadows+tiddlers]tag[$:/tags/EditorToolbar]!has[draft.of]]">
<$transclude style="height:0px" 
tiddler="$:/core/ui/EditTemplate/body/toolbar/button" mode="inline"/>




-- 
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/e7bf1e7f-c640-48c6-97e1-adde0f07ec71n%40googlegroups.com.

[tw5] Re: Make editor plugins work for <$edit-text> widgets

[Stobot]

Ha, tried this and it made some change - but now all the buttons just 
overlap the input box... 


.hideme {
height:0px
}


<$edit tiddler="$:/temp/testing">
<$list 
filter="[all[shadows+tiddlers]tag[$:/tags/EditorToolbar]!has[draft.of]]">
<$transclude style="height:0px" 
tiddler="$:/core/ui/EditTemplate/body/toolbar/button" mode="inline"/>



On Wednesday, December 2, 2020 at 3:13:26 PM UTC-5 Stobot wrote:

> Thanks!
> Ok, for autocomplete the <$edit> worked where <$edit-text> didn't - 
> perfect!
> For your autolist, I got it to work, but you're right - hiding the toolbar 
> would be excellent. 
>
> This is where I'm at that technically works - simplification of the 
> $:/core/ui/EditTemplate/body/editor tiddler you suggested I reference
>
> <$edit tiddler="$:/temp/testing">
> <$list 
> filter="[all[shadows+tiddlers]tag[$:/tags/EditorToolbar]!has[draft.of]]">
> <$transclude tiddler="$:/core/ui/EditTemplate/body/toolbar/button" 
> mode="inline"/>
> 
> 
>
> My best guess would be some magic "hide css" to put inside a class or 
> style for the transclude widget or something? Sorry - totally lost there. 
>
> Thanks in advance again!
>
> On Wednesday, December 2, 2020 at 2:47:11 PM UTC-5 saq.i...@gmail.com 
> wrote:
>
>> Editor-autolist depends on the editor toolbar - but you can hide it with 
>> css if you find it distracting.
>> Have a look at the *contents* of the <$edit> widget here which sets up 
>> the toolbar:
>> $:/core/ui/EditTemplate/body/editor 
>>
>> Also, using <$edit> instead of <$edit-text> might get the autocomplete 
>> working as well. It's been a while since I looked at it though. If that 
>> does not work, use <$edit-comptext>.
>>
>>
>> On Wednesday, December 2, 2020 at 7:44:41 PM UTC+1 Stobot wrote:
>>
>>>
>>> Hi Folks,
>>>
>>> There are some amazing plugins I can't live without for the editor 
>>> experience - 2 quick ones would be:
>>> 1. Editor-autolist from Saq
>>> 2. Edit-comptext from Snowgoon88
>>>
>>> Concurrently I'm experimenting with some setups where I end up editing 
>>> via an edit-text widget rather than the normal edittemplate. Is there a way 
>>> I can setup the edit-text widget to trick the plugins to function like it's 
>>> a full tiddler in edit-mode? 
>>> I hope that makes sense... Thanks!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/237fd2bf-686c-4cc9-a6b9-6e8cfe4546d0n%40googlegroups.com.

[tw5] Re: Make editor plugins work for <$edit-text> widgets

[Stobot]

Thanks!
Ok, for autocomplete the <$edit> worked where <$edit-text> didn't - perfect!
For your autolist, I got it to work, but you're right - hiding the toolbar 
would be excellent. 

This is where I'm at that technically works - simplification of the 
$:/core/ui/EditTemplate/body/editor tiddler you suggested I reference

<$edit tiddler="$:/temp/testing">
<$list 
filter="[all[shadows+tiddlers]tag[$:/tags/EditorToolbar]!has[draft.of]]">
<$transclude tiddler="$:/core/ui/EditTemplate/body/toolbar/button" 
mode="inline"/>



My best guess would be some magic "hide css" to put inside a class or style 
for the transclude widget or something? Sorry - totally lost there. 

Thanks in advance again!

On Wednesday, December 2, 2020 at 2:47:11 PM UTC-5 saq.i...@gmail.com wrote:

> Editor-autolist depends on the editor toolbar - but you can hide it with 
> css if you find it distracting.
> Have a look at the *contents* of the <$edit> widget here which sets up 
> the toolbar:
> $:/core/ui/EditTemplate/body/editor 
>
> Also, using <$edit> instead of <$edit-text> might get the autocomplete 
> working as well. It's been a while since I looked at it though. If that 
> does not work, use <$edit-comptext>.
>
>
> On Wednesday, December 2, 2020 at 7:44:41 PM UTC+1 Stobot wrote:
>
>>
>> Hi Folks,
>>
>> There are some amazing plugins I can't live without for the editor 
>> experience - 2 quick ones would be:
>> 1. Editor-autolist from Saq
>> 2. Edit-comptext from Snowgoon88
>>
>> Concurrently I'm experimenting with some setups where I end up editing 
>> via an edit-text widget rather than the normal edittemplate. Is there a way 
>> I can setup the edit-text widget to trick the plugins to function like it's 
>> a full tiddler in edit-mode? 
>> I hope that makes sense... Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/acfdef65-b220-4d63-967f-1af26fb31e8cn%40googlegroups.com.

[tw5] Re: Make editor plugins work for <$edit-text> widgets

[Saq Imtiaz]

Editor-autolist depends on the editor toolbar - but you can hide it with 
css if you find it distracting.
Have a look at the *contents* of the <$edit> widget here which sets up the 
toolbar:
$:/core/ui/EditTemplate/body/editor 

Also, using <$edit> instead of <$edit-text> might get the autocomplete 
working as well. It's been a while since I looked at it though. If that 
does not work, use <$edit-comptext>.


On Wednesday, December 2, 2020 at 7:44:41 PM UTC+1 Stobot wrote:

>
> Hi Folks,
>
> There are some amazing plugins I can't live without for the editor 
> experience - 2 quick ones would be:
> 1. Editor-autolist from Saq
> 2. Edit-comptext from Snowgoon88
>
> Concurrently I'm experimenting with some setups where I end up editing via 
> an edit-text widget rather than the normal edittemplate. Is there a way I 
> can setup the edit-text widget to trick the plugins to function like it's a 
> full tiddler in edit-mode? 
> I hope that makes sense... Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a70429df-0d8e-4b27-8239-48ddf12a939en%40googlegroups.com.

[tw5] Re: Fields other than the default text field being able to be treated also as a textarea?

[David Gifford]

I can't speak to the issue of linking or the relationship between the 
fields, but if the issue is just the small side of the edit box, you could 
try the editwidget. I use the following in one tiddler to adjust the 
content of a custom field of a second tiddler.

<$edit tag="textarea" tiddler="yourtiddlernamehere" 
field="yourfieldnamehere" class="tc-edit-texteditor"/>

For your case scenario, it would be a matter of changing tiddler="" to a 
'currentTiddler' filter, adding it to a tiddler, and tagging the tiddler 
$:/tags/EditTemplate . Not sure what you would need to put. But that would 
give you a bigger area to work with for that field / those fields.

On Wednesday, December 2, 2020 at 11:19:10 AM UTC-6 Cade Roux wrote:

> I was wondering if anyone has done anything like this where a tiddler has 
> another field "promoted" to a "textarea"-type of field like the main text 
> field so that a tiddler has two text areas when it's in edit mode, where 
> one is the text of the tiddler and one is the field denoted to be edited in 
> a textarea instead of a textbox with all the other (shorter) fields.
>
> In my particular use case, the second field is directly related to the 
> first, but an alternate rendering or similar.  In my case, one is HTML and 
> the other is raw XML or some other related data but they differ such that 
> they aren't realistically directly transformable from one to the other 
> within the browser.
>
> In the past I have put that text in a separate tiddler that is directly 
> linked to the first, but I have found over time, that that technique has 
> grown unwieldy and I have moved many things back into fields in the main 
> tiddler (including these large bits of text/data - which are just very 
> difficult to read in edit mode in their fields - they are obviously fine 
> when transcluded or otherwise used).
>
> Thanks in advance,
>
> Cade
>

-- 
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/ff2e049e-a494-4102-9b3d-71455eecb43dn%40googlegroups.com.

[tw5] Make editor plugins work for <$edit-text> widgets

[Stobot]

Hi Folks,

There are some amazing plugins I can't live without for the editor 
experience - 2 quick ones would be:
1. Editor-autolist from Saq
2. Edit-comptext from Snowgoon88

Concurrently I'm experimenting with some setups where I end up editing via 
an edit-text widget rather than the normal edittemplate. Is there a way I 
can setup the edit-text widget to trick the plugins to function like it's a 
full tiddler in edit-mode? 
I hope that makes sense... Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/21773a58-e0b3-47fd-b6ee-2edea34c1958n%40googlegroups.com.

[tw5] Fields other than the default text field being able to be treated also as a textarea?

[Cade Roux]

I was wondering if anyone has done anything like this where a tiddler has 
another field "promoted" to a "textarea"-type of field like the main text 
field so that a tiddler has two text areas when it's in edit mode, where 
one is the text of the tiddler and one is the field denoted to be edited in 
a textarea instead of a textbox with all the other (shorter) fields.

In my particular use case, the second field is directly related to the 
first, but an alternate rendering or similar.  In my case, one is HTML and 
the other is raw XML or some other related data but they differ such that 
they aren't realistically directly transformable from one to the other 
within the browser.

In the past I have put that text in a separate tiddler that is directly 
linked to the first, but I have found over time, that that technique has 
grown unwieldy and I have moved many things back into fields in the main 
tiddler (including these large bits of text/data - which are just very 
difficult to read in edit mode in their fields - they are obviously fine 
when transcluded or otherwise used).

Thanks in advance,

Cade

-- 
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/c7253837-8129-4310-b98f-2bcf43dc0e70n%40googlegroups.com.

Re: [tw5] Re: Popup Tagger Plugin problems

[strikke...@gmail.com]

i think it is meant to be an example tagbar with filter, tags and so on to 
show how it can look. Maybe I misunderstood but I think we are encouraged 
to create our own tagbar so as not to overwrite the eucaly example.

I think you are right it is a little confusing. I spend a lot of time 
figuring out how to, when I first used that plugin. It is very useful 
though.

Birthe

On Wednesday, December 2, 2020 at 1:25:07 PM UTC+1 David Gifford wrote:

> Wow, ok, changing that worked. Thanks strikke... Why would Eucaly pre-load 
> the plugin with something that wouldn't work for users? Doesn't make sense. 
> The documentation for this plugin is very confusing. And I find it amazing 
> that this is the ONLY TiddlyWiki plugin for creating a dropdown list to add 
> a tag to a tiddler from a subset of tags. But hey, it works now, so this 
> will be a big help for me. Thanks again!
>
>
> On Wed, Dec 2, 2020 at 6:05 AM strikke...@gmail.com  
> wrote:
>
>> At the Controlpage, look at the filter.  You have, but you are not 
>> creator eucaly.
>> *[all[tiddlers+shadows]regexp:creator[eucaly(?i)]],*
>>
>>
>> On Tuesday, December 1, 2020 at 6:34:54 PM UTC+1 David Gifford wrote:
>>
>>>
>>> Hi all
>>>
>>> I am trying to use the http://eucaly-tw5.tiddlyspot.com/#PopupTagger.  
>>> It is simply not visible in any tiddler, even though 
>>> $:/plugins/eucaly/popuptagger/TagBar is tagged $:/tags/ViewTemplate.
>>>
>>> See https://giffmex.org/experiments/sp.dumpster.template.html. Open any 
>>> regular tiddler. The popuptagger does not appear. Go to 
>>> $:/plugins/eucaly/popuptagger/TagBar and you will see it is tagged 
>>> $:/tags/ViewTemplate.  
>>>
>>> Is this plugin not compatible with more recent versions of TiddlyWiki? 
>>> Or any idea what else might be wrong?
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/Z0NU7vVfluo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/ce7a6e5f-f676-4524-be34-c357c177d8a0n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9b1f003b-2c3e-47a6-8123-4fb962f941a4n%40googlegroups.com.

Re: [tw5] Re: Popup Tagger Plugin problems

[David Gifford]

Wow, ok, changing that worked. Thanks strikke... Why would Eucaly pre-load
the plugin with something that wouldn't work for users? Doesn't make sense.
The documentation for this plugin is very confusing. And I find it amazing
that this is the ONLY TiddlyWiki plugin for creating a dropdown list to add
a tag to a tiddler from a subset of tags. But hey, it works now, so this
will be a big help for me. Thanks again!


On Wed, Dec 2, 2020 at 6:05 AM strikke...@gmail.com <
strikkeglad...@gmail.com> wrote:

> At the Controlpage, look at the filter.  You have, but you are not creator
> eucaly.
> *[all[tiddlers+shadows]regexp:creator[eucaly(?i)]],*
>
>
> On Tuesday, December 1, 2020 at 6:34:54 PM UTC+1 David Gifford wrote:
>
>>
>> Hi all
>>
>> I am trying to use the http://eucaly-tw5.tiddlyspot.com/#PopupTagger.
>> It is simply not visible in any tiddler, even though
>> $:/plugins/eucaly/popuptagger/TagBar is tagged $:/tags/ViewTemplate.
>>
>> See https://giffmex.org/experiments/sp.dumpster.template.html. Open any
>> regular tiddler. The popuptagger does not appear. Go to
>> $:/plugins/eucaly/popuptagger/TagBar and you will see it is tagged
>> $:/tags/ViewTemplate.
>>
>> Is this plugin not compatible with more recent versions of TiddlyWiki? Or
>> any idea what else might be wrong?
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/Z0NU7vVfluo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/ce7a6e5f-f676-4524-be34-c357c177d8a0n%40googlegroups.com
> 
> .
>

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

[tw5] Re: Tiddler Opening Behaviour Bug in v5.1.23 Pre-Release

[Saq Imtiaz]

This issue should now be resolved.

On Tuesday, December 1, 2020 at 5:43:37 AM UTC+1 Saq Imtiaz wrote:

> Thank you for reporting this. I've posted an issue on github: 
> https://github.com/Jermolene/TiddlyWiki5/issues/5162
>
> On Tuesday, December 1, 2020 at 3:08:17 AM UTC+1 ivanlion...@gmail.com 
> wrote:
>
>> It appears that tiddlers opened from within the story river will always 
>> open below the current tiddler in the v5.1.23 pre-release, even if they are 
>> set to open above or at the top/bottom of the story river. Is this being 
>> addressed?
>>
>

-- 
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/6acc1a75-30c9-4812-9b0b-b821608cdfc8n%40googlegroups.com.

[tw5] Re: Popup Tagger Plugin problems

[strikke...@gmail.com]

At the Controlpage, look at the filter.  You have, but you are not creator 
eucaly.
*[all[tiddlers+shadows]regexp:creator[eucaly(?i)]],*


On Tuesday, December 1, 2020 at 6:34:54 PM UTC+1 David Gifford wrote:

>
> Hi all
>
> I am trying to use the http://eucaly-tw5.tiddlyspot.com/#PopupTagger.  It 
> is simply not visible in any tiddler, even though 
> $:/plugins/eucaly/popuptagger/TagBar is tagged $:/tags/ViewTemplate.
>
> See https://giffmex.org/experiments/sp.dumpster.template.html. Open any 
> regular tiddler. The popuptagger does not appear. Go to 
> $:/plugins/eucaly/popuptagger/TagBar and you will see it is tagged 
> $:/tags/ViewTemplate.  
>
> Is this plugin not compatible with more recent versions of TiddlyWiki? Or 
> any idea what else might be wrong?
>
>
>

-- 
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/ce7a6e5f-f676-4524-be34-c357c177d8a0n%40googlegroups.com.

[tw5] Re: clever default value for a parameter

[Saq Imtiaz]

<$set name="last" filter="[{!!title}removeprefix[jingle ]]" 
select="0"><>  

When assigning the value of a set widget via a filter, it is important to 
note that the value is a title list and not a title.
In a title list, tiddler titles with spaces are enclosed in double brackets.

https://tiddlywiki.com/#SetWidget
Please see the section Filtered List Variable Assignment

Filtered List Variable Assignment

This form of the set variable widget evaluates the filter and assigns the 
result to the variable as a space-separated list (using double square 
brackets for titles containing spaces).
<$set name="myVariable" filter="[tag[HelloThere]]"> <$text 
text=<>/> Filtered Item Variable Assignment

 NEW IN: 5.1.14 This form of the set variable widget evaluates the filter 
and assigns the specified result to the variable as a single item (ie, not 
using double square brackets for titles containing spaces).
<$set name="myVariable" filter="[tag[HelloThere]]" select="0"> <$text 
text=<>/>   

and https://tiddlywiki.com/#Title%20List

On Wednesday, December 2, 2020 at 12:23:40 PM UTC+1 jn.pierr...@gmail.com 
wrote:

> Further investigating: the difference lies in the title and what you 
> finally get. If you're left with a single word, then you get a simple text. 
> If you have any space, then it's a link.
>
> thus the following code 
>
> <$set name="last" filter="[{!!title}removeprefix[jingle ]]"><>
>
> will produce a "bells" simple text in the "jingle bells" tiddler BUT a 
> "bells song" link in a "jingle bells song" tiddler.
>
> Le mercredi 2 décembre 2020 à 12:14:19 UTC+1, Jean-Pierre Rivière a écrit :
>
>> a typo in my code : theme3=<<> instead of theme3=<>
>> with that fix, I can see theme3 as a simple text, "thème 5" in the result 
>> line beginning by bag=
>>
>> as for the code with removeprefix, it works OK in an other tiddler. But 
>> here, it keeps being dizzy. the tiddler types are all set to tw5. any idea 
>> to spot the cause of this?
>>
>> Le mercredi 2 décembre 2020 à 11:36:18 UTC+1, Jean-Pierre Rivière a 
>> écrit :
>>
>>> @Eric. Tahnk you! It does the trick but... not so much as I wanted. see 
>>> the output I get:
>>>
>>> [image: unwanted-link.png]
>>>
>>> "thème 5" is indeed the tittle of an existing tiddler.
>>>
>>> What I am looking for is only the text "thème 5", not the link to "thème 
>>> 5".
>>>
>>> Now, I know how to use $wikify to acieve that goal with the current 
>>> linking result. But what I don't understand is why I got this linking in 
>>> the first place!
>>>
>>> my code (same as yours):
>>>
>>> \define itemlist2(tag:"thème", field:"theme", excluding)
>>> <$set name="rejecting" 
>>> filter="[[$excluding$]!match[]then[$excluding$]else[$tag$]]">
>>> tag=$tag$, field=$field$, excluding=$excluding$, rejecting=<>.
>>> 
>>> \end
>>>
>>> and my using that code (to get the picture above) in tiddler "choix des 
>>> critères du thème 5"
>>>
>>> <$set name=beg value="choix des critères du ">
>>> <$set name=theme2 filter="[{!!title}removeprefix]">
>>> <$wikify name=theme3 text="<>">
>>> <$wikify name="theme-label" text="""<$transclude tiddler=<> 
>>> field=theme/>""">
>>> beg=<> theme2=<> theme3=<<> 
>>> theme-label=<>
>>> <$macrocall $name=itemlist2 tag=<> field=criterion 
>>> excluding=<>/>
>>> 
>>> 
>>>
>>> And I get also this line:
>>>
>>> [image: unwanted-link2.png]
>>>
>>> (where I neither understand why theme2 is a link and theme3 is void)
>>>
>>>
>>> Le mardi 1 décembre 2020 à 21:24:39 UTC+1, Eric Shulman a écrit :
>>>
 On Tuesday, December 1, 2020 at 12:09:38 PM UTC-8 jn.pierr...@gmail.com 
 wrote:

> I am writing a macro with three parameters. If omitted, the third 
> shall be equal to the first one. This cannot be hardwired of course! So I 
> need to code it. With a filter.

 \define itemlist2(tag:"thème", field:"theme", excluding)
> <$set name="rejecting" filter="[$excluding$]+[regexp[^.]then[YES 
> $excluding$]else[NO $tag$]]">
> tag=$tag$, field=$field$, excluding=$excluding$, 
> rejecting=<>.
> 
> \end
>

 Try using the !match[...] filter, like this:
 \define itemlist2(tag:"thème", field:"theme", excluding)
 <$set name="rejecting" filter="[[$excluding$]!match[]then[$excluding
 $]else[$tag$]]">
 tag=$tag$, field=$field$, excluding=$excluding$, 
 rejecting=<>.
 
 \end

 -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/1c9f11ea-18fe-4c79-9ba5-f21b6edad429n%40googlegroups.com.

[tw5] Re: Query: RANGE Operator. Does it only work in base-10?

[TW Tones]

Mark,

On this occasion I need to convert a 4 digit Hex to a decimal, so that I 
can use it in the range widget, because we cant generate a range of hex 
numbers.

Hence this issue https://github.com/Jermolene/TiddlyWiki5/issues/5177

I think I can do it but if you know how please share.

Tones 

On Tuesday, 1 December 2020 at 06:37:40 UTC+11 Mark S. wrote:

> Just for fun. Convert 0-255 to Hex.
>
>
> *<$vars hexlist="0 1 2 3 4 5 6 7 8 9 A B C D E F">*
> *<$list filter="[range[31,40]]" variable=dec>*
> *<$list filter="[divide[16]trunc[]add[1]]" variable="byte">*
> *<$list filter="[remainder[16]add[1]]" variable="bit">*
> *<$list 
> filter="[enlistnth]=[enlistnth]+[join[]]" 
> variable="hex1">*
> *<> <> *
> **
> **
>
> On Monday, November 30, 2020 at 3:09:46 AM UTC-8 TiddlyTweeter wrote:
>
>>
>> *So.* My query is whether there might be a way to feed hex numbers 
>> (convert to decimal first?) to Range so we could at least feed in hex even 
>> if the number crunching is digital?
>>
>>
>>

-- 
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/dff217f3-e285-4fee-b4bb-fbfb6f6443a5n%40googlegroups.com.

[tw5] Re: clever default value for a parameter

[Jean-Pierre Rivière]

Further investigating: the difference lies in the title and what you 
finally get. If you're left with a single word, then you get a simple text. 
If you have any space, then it's a link.

thus the following code 

<$set name="last" filter="[{!!title}removeprefix[jingle ]]"><>

will produce a "bells" simple text in the "jingle bells" tiddler BUT a 
"bells song" link in a "jingle bells song" tiddler.

Le mercredi 2 décembre 2020 à 12:14:19 UTC+1, Jean-Pierre Rivière a écrit :

> a typo in my code : theme3=<<> instead of theme3=<>
> with that fix, I can see theme3 as a simple text, "thème 5" in the result 
> line beginning by bag=
>
> as for the code with removeprefix, it works OK in an other tiddler. But 
> here, it keeps being dizzy. the tiddler types are all set to tw5. any idea 
> to spot the cause of this?
>
> Le mercredi 2 décembre 2020 à 11:36:18 UTC+1, Jean-Pierre Rivière a écrit :
>
>> @Eric. Tahnk you! It does the trick but... not so much as I wanted. see 
>> the output I get:
>>
>> [image: unwanted-link.png]
>>
>> "thème 5" is indeed the tittle of an existing tiddler.
>>
>> What I am looking for is only the text "thème 5", not the link to "thème 
>> 5".
>>
>> Now, I know how to use $wikify to acieve that goal with the current 
>> linking result. But what I don't understand is why I got this linking in 
>> the first place!
>>
>> my code (same as yours):
>>
>> \define itemlist2(tag:"thème", field:"theme", excluding)
>> <$set name="rejecting" 
>> filter="[[$excluding$]!match[]then[$excluding$]else[$tag$]]">
>> tag=$tag$, field=$field$, excluding=$excluding$, rejecting=<>.
>> 
>> \end
>>
>> and my using that code (to get the picture above) in tiddler "choix des 
>> critères du thème 5"
>>
>> <$set name=beg value="choix des critères du ">
>> <$set name=theme2 filter="[{!!title}removeprefix]">
>> <$wikify name=theme3 text="<>">
>> <$wikify name="theme-label" text="""<$transclude tiddler=<> 
>> field=theme/>""">
>> beg=<> theme2=<> theme3=<<> 
>> theme-label=<>
>> <$macrocall $name=itemlist2 tag=<> field=criterion 
>> excluding=<>/>
>> 
>> 
>>
>> And I get also this line:
>>
>> [image: unwanted-link2.png]
>>
>> (where I neither understand why theme2 is a link and theme3 is void)
>>
>>
>> Le mardi 1 décembre 2020 à 21:24:39 UTC+1, Eric Shulman a écrit :
>>
>>> On Tuesday, December 1, 2020 at 12:09:38 PM UTC-8 jn.pierr...@gmail.com 
>>> wrote:
>>>
 I am writing a macro with three parameters. If omitted, the third shall 
 be equal to the first one. This cannot be hardwired of course! So I need 
 to 
 code it. With a filter.
>>>
>>> \define itemlist2(tag:"thème", field:"theme", excluding)
 <$set name="rejecting" filter="[$excluding$]+[regexp[^.]then[YES 
 $excluding$]else[NO $tag$]]">
 tag=$tag$, field=$field$, excluding=$excluding$, 
 rejecting=<>.
 
 \end

>>>
>>> Try using the !match[...] filter, like this:
>>> \define itemlist2(tag:"thème", field:"theme", excluding)
>>> <$set name="rejecting" filter="[[$excluding$]!match[]then[$excluding
>>> $]else[$tag$]]">
>>> tag=$tag$, field=$field$, excluding=$excluding$, 
>>> rejecting=<>.
>>> 
>>> \end
>>>
>>> -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/5169ffa2-05c7-46ba-9bf8-edad4911e102n%40googlegroups.com.

[tw5] Re: clever default value for a parameter

[Jean-Pierre Rivière]

a typo in my code : theme3=<<> instead of theme3=<>
with that fix, I can see theme3 as a simple text, "thème 5" in the result 
line beginning by bag=

as for the code with removeprefix, it works OK in an other tiddler. But 
here, it keeps being dizzy. the tiddler types are all set to tw5. any idea 
to spot the cause of this?

Le mercredi 2 décembre 2020 à 11:36:18 UTC+1, Jean-Pierre Rivière a écrit :

> @Eric. Tahnk you! It does the trick but... not so much as I wanted. see 
> the output I get:
>
> [image: unwanted-link.png]
>
> "thème 5" is indeed the tittle of an existing tiddler.
>
> What I am looking for is only the text "thème 5", not the link to "thème 
> 5".
>
> Now, I know how to use $wikify to acieve that goal with the current 
> linking result. But what I don't understand is why I got this linking in 
> the first place!
>
> my code (same as yours):
>
> \define itemlist2(tag:"thème", field:"theme", excluding)
> <$set name="rejecting" 
> filter="[[$excluding$]!match[]then[$excluding$]else[$tag$]]">
> tag=$tag$, field=$field$, excluding=$excluding$, rejecting=<>.
> 
> \end
>
> and my using that code (to get the picture above) in tiddler "choix des 
> critères du thème 5"
>
> <$set name=beg value="choix des critères du ">
> <$set name=theme2 filter="[{!!title}removeprefix]">
> <$wikify name=theme3 text="<>">
> <$wikify name="theme-label" text="""<$transclude tiddler=<> 
> field=theme/>""">
> beg=<> theme2=<> theme3=<<> 
> theme-label=<>
> <$macrocall $name=itemlist2 tag=<> field=criterion 
> excluding=<>/>
> 
> 
>
> And I get also this line:
>
> [image: unwanted-link2.png]
>
> (where I neither understand why theme2 is a link and theme3 is void)
>
>
> Le mardi 1 décembre 2020 à 21:24:39 UTC+1, Eric Shulman a écrit :
>
>> On Tuesday, December 1, 2020 at 12:09:38 PM UTC-8 jn.pierr...@gmail.com 
>> wrote:
>>
>>> I am writing a macro with three parameters. If omitted, the third shall 
>>> be equal to the first one. This cannot be hardwired of course! So I need to 
>>> code it. With a filter.
>>
>> \define itemlist2(tag:"thème", field:"theme", excluding)
>>> <$set name="rejecting" filter="[$excluding$]+[regexp[^.]then[YES 
>>> $excluding$]else[NO $tag$]]">
>>> tag=$tag$, field=$field$, excluding=$excluding$, 
>>> rejecting=<>.
>>> 
>>> \end
>>>
>>
>> Try using the !match[...] filter, like this:
>> \define itemlist2(tag:"thème", field:"theme", excluding)
>> <$set name="rejecting" filter="[[$excluding$]!match[]then[$excluding
>> $]else[$tag$]]">
>> tag=$tag$, field=$field$, excluding=$excluding$, 
>> rejecting=<>.
>> 
>> \end
>>
>> -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/e49e4ed1-c2cd-4ec8-8bbf-890277bb15a2n%40googlegroups.com.

[tw5] Re: clever default value for a parameter

[Jean-Pierre Rivière]

@Eric. Tahnk you! It does the trick but... not so much as I wanted. see the 
output I get:

[image: unwanted-link.png]

"thème 5" is indeed the tittle of an existing tiddler.

What I am looking for is only the text "thème 5", not the link to "thème 5".

Now, I know how to use $wikify to acieve that goal with the current linking 
result. But what I don't understand is why I got this linking in the first 
place!

my code (same as yours):

\define itemlist2(tag:"thème", field:"theme", excluding)
<$set name="rejecting" 
filter="[[$excluding$]!match[]then[$excluding$]else[$tag$]]">
tag=$tag$, field=$field$, excluding=$excluding$, rejecting=<>.

\end

and my using that code (to get the picture above) in tiddler "choix des 
critères du thème 5"

<$set name=beg value="choix des critères du ">
<$set name=theme2 filter="[{!!title}removeprefix]">
<$wikify name=theme3 text="<>">
<$wikify name="theme-label" text="""<$transclude tiddler=<> 
field=theme/>""">
beg=<> theme2=<> theme3=<<> 
theme-label=<>
<$macrocall $name=itemlist2 tag=<> field=criterion 
excluding=<>/>



And I get also this line:

[image: unwanted-link2.png]

(where I neither understand why theme2 is a link and theme3 is void)


Le mardi 1 décembre 2020 à 21:24:39 UTC+1, Eric Shulman a écrit :

> On Tuesday, December 1, 2020 at 12:09:38 PM UTC-8 jn.pierr...@gmail.com 
> wrote:
>
>> I am writing a macro with three parameters. If omitted, the third shall 
>> be equal to the first one. This cannot be hardwired of course! So I need to 
>> code it. With a filter.
>
> \define itemlist2(tag:"thème", field:"theme", excluding)
>> <$set name="rejecting" filter="[$excluding$]+[regexp[^.]then[YES 
>> $excluding$]else[NO $tag$]]">
>> tag=$tag$, field=$field$, excluding=$excluding$, 
>> rejecting=<>.
>> 
>> \end
>>
>
> Try using the !match[...] filter, like this:
> \define itemlist2(tag:"thème", field:"theme", excluding)
> <$set name="rejecting" filter="[[$excluding$]!match[]then[$excluding
> $]else[$tag$]]">
> tag=$tag$, field=$field$, excluding=$excluding$, 
> rejecting=<>.
> 
> \end
>
> -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/556fbdc4-5da2-4fdc-833c-fed2ddcd8aa0n%40googlegroups.com.

Re: [tw5] Re: Understanding how macro expansion works

[Mohammad]

Thanks Nico!


On Wednesday, December 2, 2020 at 11:59:51 AM UTC+3:30 Nicolas Petton wrote:

> Mohammad  writes:
>
> Hi Mohammad,
>
> > Welcome back.
>
> Thanks :)
>
> > Off topic:
> >
> > I know your Project Manager plugin and more specific the Notebook 
> > theme and palette (https://nicolas.petton.fr/tw/project-manager.html) 
> have 
> > a lot of fans! You may put the code on GitHub lets user send their issue 
> > and idea there.
>
> Yes, that's exactly what I'm planning to do. I resumed work on both
> projects.
>
> > I use Notebook on mobile and its amazing! Thank you Nico.
>
> Glad you like it!
>
> Cheers,
> Nico
>

-- 
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/247efe93-002e-4a8e-b971-44010ddae589n%40googlegroups.com.

Re: [tw5] Re: Understanding how macro expansion works

[Nicolas Petton]

Mohammad  writes:

Hi Mohammad,

> Welcome back.

Thanks :)

> Off topic:
>
> I know your Project Manager plugin and more specific the Notebook 
> theme and palette (https://nicolas.petton.fr/tw/project-manager.html) have 
> a lot of fans! You may put the code on GitHub lets user send their issue 
> and idea there.

Yes, that's exactly what I'm planning to do.  I resumed work on both
projects.

> I use Notebook on mobile and its amazing! Thank you Nico.

Glad you like it!

Cheers,
Nico

-- 
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/87tut4391x.fsf%40petton.fr.


signature.asc
Description: PGP signature