[tw5] YES! BASIC augmented by TiddlyWiki !

2021-12-01 Thread Charlie Veniot 
BTW, I'm thinking of calling this "*BASIC Anywhere Machine*- wwwBasic 
augmented by TiddlyWiki".  Comments/suggestions always welcome.

Any part of a BASIC program dynamically generated by TiddlyWiki.  Pretty 
awesome.

Video: https://www.youtube.com/watch?v=RD6Qj2NG7Go
Give the latest version a 
spin: https://cjveniot.neocities.org/TW_BasicIDE.html

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

Re: [tw5] Re: An easier way to create a band of specific colors

2021-12-01 Thread Charlie Veniot 
Pff, no worries.  Totally worth it getting you to where you wanted to be.

Besides, I love this filtering stuff.  Great "brain-age games" kind of 
stuff.

On Tuesday, November 30, 2021 at 11:51:02 PM UTC-4 taale...@gmail.com wrote:

> And lastly - fixed. :/ sorry for the 2380756 emails
>
> \define lddots( likeThis )
> <$list filter="[[$likeThis$]split[,]]">
> <$vars thisStyle={{{ [[height:20px;width:20px;background-color:]] 
> [] [[;border-radius:50%;display:inline-block;border:3px 
> solid black;]] +[join[]] }}}>
> ] }}}>
> 
> 
> \end
>
> On Tuesday, November 30, 2021 at 8:47:21 PM UTC-7 taale...@gmail.com 
> wrote:
>
>> And I figured out the macro it seems, except it's still doing it in a 
>> column, not a row:
>> [image: test in columns.png]
>>
>> On Tuesday, November 30, 2021 at 8:35:24 PM UTC-7 taale...@gmail.com 
>> wrote:
>>
>>> And... Here's a shot of what it looks like on TW. When I was testing at 
>>> work this afternoon, the circles were less oval, and in a row.
>>>
>>> [image: TWsite test.png]
>>>
>>> On Tuesday, November 30, 2021 at 8:25:13 PM UTC-7 taale...@gmail.com 
>>> wrote:
>>>
 I thought the tids might help

 On Tuesday, November 30, 2021 at 8:17:33 PM UTC-7 cj.v...@gmail.com 
 wrote:

> Oh, column vs row.
>
> Although the blank lines make your work more readable, I'm thinking 
> one of those is causing a carriage return.
>
> *And* your macro is missing parentheses:
>
> \define lfdots*()*
>
> Otherwise, very cool.
> On Tuesday, November 30, 2021 at 11:09:20 PM UTC-4 taale...@gmail.com 
> wrote:
>
>> oh, and it works fine on tiddlywiki.com with my tweaks (except that 
>> the dots are in a column not a row as before)
>>
>> And I see I left out the () after the definition - but still no 
>> difference
>>
>>
>> On Tuesday, November 30, 2021 at 8:07:13 PM UTC-7 taale...@gmail.com 
>> wrote:
>>
>>> Everything worked on Tiddlywiki, but on my wiki, after my tweaks, no 
>>> good/no bueno/dim da (that last one is Welsh)
>>>
>>> My tweaks to the code:
>>>
>>> \define lfdots
>>>
>>> <$list filter="[{!!colors}split[,]] 
>>> +[search-replace:i[abr],[gold]] 
>>> +[search-replace:i[bgn],[teal]]
>>> +[search-replace:i[blk],[black]] 
>>> +[search-replace:i[blu],[blue]]
>>> +[search-replace:i[brn],[brown]] 
>>> +[search-replace:i[cyn],[cyan]]
>>> +[search-replace:i[grn],[limegreen]] 
>>> +[search-replace:i[gry],[gray]]
>>> +[search-replace:i[mag],[magenta]] 
>>> +[search-replace:i[org],[orange]]
>>> +[search-replace:i[ppl],[purple]] 
>>> +[search-replace:i[rbn],[sienna]]
>>> +[search-replace:i[red],[red]] 
>>> +[search-replace:i[tny],[burlywood]]
>>> +[search-replace:i[wht],[white]] 
>>> +[search-replace:i[ygn],[yellowgreen]]
>>> +[search-replace:i[yel],[yellow]] 
>>> +[search-replace:i[pnk],[pink]]
>>> +[search-replace:i[lbl],[skyblue]] 
>>> ">
>>>
>>> <$vars thisStyle={{{ 
>>> [[min-height:20px;width:20px;background-color:]] [] 
>>> [[;border-radius:50%;display:inline-block;border:3px solid black;]] 
>>> +[join[]] }}}>
>>> ] }}}>
>>>
>>> 
>>>
>>> 
>>> \end
>>>
>>>
>>>- number of   doesn't seem to matter as long as there's 
>>>one - on tiddlywiki.com
>>>- I realize that if I use a delimiter in the split, I can have 
>>>different length parameters, and therefore dont need abbreviations 
>>> or the 
>>>search-replace commands; I'm using them at the moment for habit's 
>>> sake
>>>
>>> So when I create the macro definition tiddler, when I saved it 
>>> before, it looked empty, but now it looks like this:
>>>
>>> [image: lfdots Macro tid.png]
>>>
>>> and the test tid, with the text <> (lfdots for large field 
>>> dots, as opposed to sddots = small defined dots) looks like this:
>>>
>>> [image: lfdots test.png]
>>>
>>> So what did I do wrong? I've been over and over for typos, but not 
>>> seeing it.
>>>
>>> On Tuesday, November 30, 2021 at 1:27:48 PM UTC-7 cj.v...@gmail.com 
>>> wrote:
>>>
 You got it.  Well, I could be out to lunch.  Proof is always in the 
 pudding.

 On Tuesday, November 30, 2021 at 3:38:44 PM UTC-4 
 taale...@gmail.com wrote:

> So much awesomeness!
>
> Okay, so I see now it's not my classes, but regular html color 
> names. If I want #478AE2, how do I specify that? For some reason, I 
> think 
> [#478AE2] isn't right - or am I wrong?
>
> On Tue, Nov 30, 2021 at 12:34 PM Charlie Veniot  
> wrote:
>
>> And I hybrid, for the giggles:
>>
>> \define beDotted3(likeThis)
>>
>> <$list filter="[[$likeThis$]!is[blank]] [{!!colorway}] +[first[]]

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Charlie Veniot 
Thanks for the info, Jeremy.  2-tier client server guy over here, so the 
innards of web browsers is foreign territory for this kid.

So whatever browser Maurizio is using, that approach I'm suggesting should 
work with some font-family available by default in whatever browser 
Maurizio is using, right?

On Wednesday, December 1, 2021 at 1:15:16 PM UTC-4 jeremy...@gmail.com 
wrote:

> I think it's working for CJ because the "Brush Script MT" font is 
> available by default in that browser, without needing to be defined by a 
> font-face tag. That technique only works for built-in fonts because 
> there's no way to inject the CSS font-face declaration into the iframe.
>
> Best wishes
>
> Jeremy
>
>
>
>
>
> On Wednesday, December 1, 2021 at 5:03:36 PM UTC cj.v...@gmail.com wrote:
>
>> Just to confirm, I went to tiddlywiki.com, edited (i.e. clicked the 
>> "edit" button) that core tiddler, *(1)* added the style lines above the 
>> edit widget, and *(2)* altered the class for the edit widget, adding 
>> bubba as the third class.
>>
>> Works A-1 for me.
>>
>> Maybe Brush Script MT cursive doesn't work with your web browser?  
>> (Another screenshot for the proof in the pudding, with an obnoxious font 
>> size, below.)
>>
>> It is the font in the editor that you want adjusted, right?
>>
>> Total aside: "bubba" because it is easy for me to find and remember.  I'm 
>> a huge fan of the movie Forrest Gump, and really liked "Bubba" in that 
>> movie.
>>
>> [image: Screenshot 2021-12-01 12.58.38 PM.png]
>>
>> On Wednesday, December 1, 2021 at 12:45:03 PM UTC-4 Charlie Veniot wrote:
>>
>>> I forgot to mention, you have to add that "bubba" class to the edit text 
>>> widget.
>>>
>>> As per the screenshot, the editor is showing that funky font.
>>>
>>> However, it did strangely take half-a-minute or so for that font to take 
>>> effect.
>>>
>>> On Wednesday, December 1, 2021 at 11:45:47 AM UTC-4 torc...@gmail.com 
>>> wrote:
>>>
 thank you cj.v, but it didn't worked for me. 
 it assign the class bubba to the iframe (just as 
 $:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... 
 nothing 
 changes.
 i suspect it has to do with what Jeremy wrote:

 "The reason that custom fonts doesn’t work with the editor toolbar is 
 because of the way that it creates the textarea element within an embedded 
 iframe (this is done so that the selection in the textarea isn’t lost when 
 the user clicks on a toolbar button and the textarea loses focus).

 The iframe doesn’t inherit any of the styles in the main document, so 
 the code actually creates a hidden textarea and then reads back the 
 styles, 
 and then applies them to the textarea in the iframe. That means that any 
 formatting applied to the textarea will be faithfully reproduced within 
 the 
 iframe. However, it only works for CSS properties applied directly to the 
 textarea; it doesn’t transfer fonts, animations or other resources that 
 can 
 be defined in CSS.

 (The code is here: 
 https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
 )

 We could update things so that special stylesheets identified by a new 
 system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
 inserted within the iframe." 

 Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 
 cj.v...@gmail.com ha scritto:

> G'day,
>
> If you are not averse to changing core TiddlyWiki templates, you could 
> add a style at the top of the content in 
> $:/core/ui/EditTemplate/body/editor.
>
> See my screenshot below, in which I set the font to Brush Script MT 
> cursive.
>
> It would be good for more experienced TiddlyWiki users to chime in on 
> any downsides to this approach.
>
> *(BTW: please ignore the goofy-looking "!!! EditTemplate body" ... 
> that's me entering little breadcrumbs to figure out which core tiddler is 
> which.)*
>
> [image: Screenshot 2021-12-01 9.52.23 AM.png]
>
> On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com 
> wrote:
>
>> Hi everybody, any progress on this? (I really don't like see a 
>> different fontfamily when editing)
>> thank you so much for all the great work!
>>
>> maurizio
>>
>> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha 
>> scritto:
>>
>>> Hi Alfonso,
>>>
>>> If I remember correctly the following comes from Jeremy's TalkyTalky 
>>>  which uses the Google font 
>>> Lato:
>>>
>>> It contains the follwing stylesheet (a tiddler tagged with 
>>> $:/tags/Stylesheet):
>>>
>>> \define register-font(family,title,style,weight)
>>> @font-face {
>>>   font-family: "$family$";
>>>   font-style: $style$;
>>>   font-weight:

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Jeremy Ruston 
I think it's working for CJ because the "Brush Script MT" font is available 
by default in that browser, without needing to be defined by a font-face 
tag. That technique only works for built-in fonts because there's no way to 
inject the CSS font-face declaration into the iframe.

Best wishes

Jeremy





On Wednesday, December 1, 2021 at 5:03:36 PM UTC cj.v...@gmail.com wrote:

> Just to confirm, I went to tiddlywiki.com, edited (i.e. clicked the 
> "edit" button) that core tiddler, *(1)* added the style lines above the 
> edit widget, and *(2)* altered the class for the edit widget, adding 
> bubba as the third class.
>
> Works A-1 for me.
>
> Maybe Brush Script MT cursive doesn't work with your web browser?  
> (Another screenshot for the proof in the pudding, with an obnoxious font 
> size, below.)
>
> It is the font in the editor that you want adjusted, right?
>
> Total aside: "bubba" because it is easy for me to find and remember.  I'm 
> a huge fan of the movie Forrest Gump, and really liked "Bubba" in that 
> movie.
>
> [image: Screenshot 2021-12-01 12.58.38 PM.png]
>
> On Wednesday, December 1, 2021 at 12:45:03 PM UTC-4 Charlie Veniot wrote:
>
>> I forgot to mention, you have to add that "bubba" class to the edit text 
>> widget.
>>
>> As per the screenshot, the editor is showing that funky font.
>>
>> However, it did strangely take half-a-minute or so for that font to take 
>> effect.
>>
>> On Wednesday, December 1, 2021 at 11:45:47 AM UTC-4 torc...@gmail.com 
>> wrote:
>>
>>> thank you cj.v, but it didn't worked for me. 
>>> it assign the class bubba to the iframe (just as 
>>> $:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... nothing 
>>> changes.
>>> i suspect it has to do with what Jeremy wrote:
>>>
>>> "The reason that custom fonts doesn’t work with the editor toolbar is 
>>> because of the way that it creates the textarea element within an embedded 
>>> iframe (this is done so that the selection in the textarea isn’t lost when 
>>> the user clicks on a toolbar button and the textarea loses focus).
>>>
>>> The iframe doesn’t inherit any of the styles in the main document, so 
>>> the code actually creates a hidden textarea and then reads back the styles, 
>>> and then applies them to the textarea in the iframe. That means that any 
>>> formatting applied to the textarea will be faithfully reproduced within the 
>>> iframe. However, it only works for CSS properties applied directly to the 
>>> textarea; it doesn’t transfer fonts, animations or other resources that can 
>>> be defined in CSS.
>>>
>>> (The code is here: 
>>> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
>>> )
>>>
>>> We could update things so that special stylesheets identified by a new 
>>> system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
>>> inserted within the iframe." 
>>>
>>> Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 
>>> cj.v...@gmail.com ha scritto:
>>>
 G'day,

 If you are not averse to changing core TiddlyWiki templates, you could 
 add a style at the top of the content in 
 $:/core/ui/EditTemplate/body/editor.

 See my screenshot below, in which I set the font to Brush Script MT 
 cursive.

 It would be good for more experienced TiddlyWiki users to chime in on 
 any downsides to this approach.

 *(BTW: please ignore the goofy-looking "!!! EditTemplate body" ... 
 that's me entering little breadcrumbs to figure out which core tiddler is 
 which.)*

 [image: Screenshot 2021-12-01 9.52.23 AM.png]

 On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com 
 wrote:

> Hi everybody, any progress on this? (I really don't like see a 
> different fontfamily when editing)
> thank you so much for all the great work!
>
> maurizio
>
> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha 
> scritto:
>
>> Hi Alfonso,
>>
>> If I remember correctly the following comes from Jeremy's TalkyTalky 
>>  which uses the Google font Lato:
>>
>> It contains the follwing stylesheet (a tiddler tagged with 
>> $:/tags/Stylesheet):
>>
>> \define register-font(family,title,style,weight)
>> @font-face {
>>   font-family: "$family$";
>>   font-style: $style$;
>>   font-weight: $weight$;
>>   src: url(<>) format("woff");
>> }
>> \end
>> \rules only filteredtranscludeinline transcludeinline macrodef 
>> macrocallinline
>>
>> /*
>> ** Fonts
>> */
>>
>> <> "900">>
>> <> "italic" "900">>
>> <> "700">>
>> <> "italic" "700">>
>> <> "normal" "100">>
>> <> "italic" "100">>
>> <> "400">>
>> <> "300">>
>> <> "italic" "300">>
>> <> "400">>
>>
>> Hope that helps.
>>
>> Cheers,
>>
>> Ton

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Charlie Veniot 
I forgot to mention, you have to add that "bubba" class to the edit text 
widget.

As per the screenshot, the editor is showing that funky font.

However, it did strangely take half-a-minute or so for that font to take 
effect.

On Wednesday, December 1, 2021 at 11:45:47 AM UTC-4 torc...@gmail.com wrote:

> thank you cj.v, but it didn't worked for me. 
> it assign the class bubba to the iframe (just as 
> $:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... nothing 
> changes.
> i suspect it has to do with what Jeremy wrote:
>
> "The reason that custom fonts doesn’t work with the editor toolbar is 
> because of the way that it creates the textarea element within an embedded 
> iframe (this is done so that the selection in the textarea isn’t lost when 
> the user clicks on a toolbar button and the textarea loses focus).
>
> The iframe doesn’t inherit any of the styles in the main document, so the 
> code actually creates a hidden textarea and then reads back the styles, and 
> then applies them to the textarea in the iframe. That means that any 
> formatting applied to the textarea will be faithfully reproduced within the 
> iframe. However, it only works for CSS properties applied directly to the 
> textarea; it doesn’t transfer fonts, animations or other resources that can 
> be defined in CSS.
>
> (The code is here: 
> https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
> )
>
> We could update things so that special stylesheets identified by a new 
> system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
> inserted within the iframe." 
>
> Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 cj.v...@gmail.com 
> ha scritto:
>
>> G'day,
>>
>> If you are not averse to changing core TiddlyWiki templates, you could 
>> add a style at the top of the content in 
>> $:/core/ui/EditTemplate/body/editor.
>>
>> See my screenshot below, in which I set the font to Brush Script MT 
>> cursive.
>>
>> It would be good for more experienced TiddlyWiki users to chime in on any 
>> downsides to this approach.
>>
>> *(BTW: please ignore the goofy-looking "!!! EditTemplate body" ... that's 
>> me entering little breadcrumbs to figure out which core tiddler is which.)*
>>
>> [image: Screenshot 2021-12-01 9.52.23 AM.png]
>>
>> On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com 
>> wrote:
>>
>>> Hi everybody, any progress on this? (I really don't like see a different 
>>> fontfamily when editing)
>>> thank you so much for all the great work!
>>>
>>> maurizio
>>>
>>> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha 
>>> scritto:
>>>
 Hi Alfonso,

 If I remember correctly the following comes from Jeremy's TalkyTalky 
  which uses the Google font Lato:

 It contains the follwing stylesheet (a tiddler tagged with 
 $:/tags/Stylesheet):

 \define register-font(family,title,style,weight)
 @font-face {
   font-family: "$family$";
   font-style: $style$;
   font-weight: $weight$;
   src: url(<>) format("woff");
 }
 \end
 \rules only filteredtranscludeinline transcludeinline macrodef 
 macrocallinline

 /*
 ** Fonts
 */

 <>>> "900">>
 <>>> "italic" "900">>
 <>>> "700">>
 <>>> "italic" "700">>
 <>>> "100">>
 <>>> "italic" "100">>
 <>>> "400">>
 <>>> "300">>
 <>>> "italic" "300">>
 <>>> "400">>

 Hope that helps.

 Cheers,

 Ton




-- 
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/39f6263c-f8a4-4074-97ae-a0fab715d79dn%40googlegroups.com.

[tw5] Re: Please help us test v5.2.1-prerelease so we can expedite its release

2021-12-01 Thread Stobot 
Don't know if you're looking for "no issue" replies or if it's just noise, 
but I haven't run into any concerns on any of my wikis I've tested so far - 
mostly Node on Windows so far. 
On Wednesday, November 24, 2021 at 12:10:49 PM UTC-5 ma...@makiaea.org 
wrote:

> i'm sure it's just something weird in my source tiddlywiki but if i just 
> upgrade as-is, it breaks. deselecting all tiddlers and selecting all 
> tiddlers to upgrade (i.e. to include state tiddlers etc. -- lots of my 
> tiddlers have state-tiddler-dependent moving parts) in the wizard seems to 
> produce a working file. tested on mac chrome Version 96.0.4664.55 (Official 
> Build) (arm64), mac monterey safari Version 15.1 (17612.2.9.1.20), and ios 
> 14.3
>
> wanted to attach some files: original 20210120makiaea tiddlywiki; upgrade 
> (broken) brings up $:/library/sjcl.js on startup; and upgrade-2 (working)
>
> but google groups complained the message was too long(!)
>
>>

-- 
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/33642041-eb23-4440-9eb9-825fc8cc55aan%40googlegroups.com.

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Maurizio Torchio 
 thank you cj.v, but it didn't worked for me. 
it assign the class bubba to the iframe (just as 
$:/themes/tiddlywiki/vanilla/settings/editorfontfamily does) but... nothing 
changes.
i suspect it has to do with what Jeremy wrote:

"The reason that custom fonts doesn’t work with the editor toolbar is 
because of the way that it creates the textarea element within an embedded 
iframe (this is done so that the selection in the textarea isn’t lost when 
the user clicks on a toolbar button and the textarea loses focus).

The iframe doesn’t inherit any of the styles in the main document, so the 
code actually creates a hidden textarea and then reads back the styles, and 
then applies them to the textarea in the iframe. That means that any 
formatting applied to the textarea will be faithfully reproduced within the 
iframe. However, it only works for CSS properties applied directly to the 
textarea; it doesn’t transfer fonts, animations or other resources that can 
be defined in CSS.

(The code is here: 
https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
)

We could update things so that special stylesheets identified by a new 
system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
inserted within the iframe." 

Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 cj.v...@gmail.com 
ha scritto:

> G'day,
>
> If you are not averse to changing core TiddlyWiki templates, you could add 
> a style at the top of the content in $:/core/ui/EditTemplate/body/editor.
>
> See my screenshot below, in which I set the font to Brush Script MT 
> cursive.
>
> It would be good for more experienced TiddlyWiki users to chime in on any 
> downsides to this approach.
>
> *(BTW: please ignore the goofy-looking "!!! EditTemplate body" ... that's 
> me entering little breadcrumbs to figure out which core tiddler is which.)*
>
> [image: Screenshot 2021-12-01 9.52.23 AM.png]
>
> On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com 
> wrote:
>
>> Hi everybody, any progress on this? (I really don't like see a different 
>> fontfamily when editing)
>> thank you so much for all the great work!
>>
>> maurizio
>>
>> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha 
>> scritto:
>>
>>> Hi Alfonso,
>>>
>>> If I remember correctly the following comes from Jeremy's TalkyTalky 
>>>  which uses the Google font Lato:
>>>
>>> It contains the follwing stylesheet (a tiddler tagged with 
>>> $:/tags/Stylesheet):
>>>
>>> \define register-font(family,title,style,weight)
>>> @font-face {
>>>   font-family: "$family$";
>>>   font-style: $style$;
>>>   font-weight: $weight$;
>>>   src: url(<>) format("woff");
>>> }
>>> \end
>>> \rules only filteredtranscludeinline transcludeinline macrodef 
>>> macrocallinline
>>>
>>> /*
>>> ** Fonts
>>> */
>>>
>>> <>> "900">>
>>> <>> "italic" "900">>
>>> <>> >>
>>> <>> "700">>
>>> <>> "100">>
>>> <>> "italic" "100">>
>>> <>> "400">>
>>> <>> "300">>
>>> <>> "italic" "300">>
>>> <>> "400">>
>>>
>>> Hope that helps.
>>>
>>> Cheers,
>>>
>>> Ton
>>>
>>>
>>>

-- 
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/4692a382-91e6-43b9-af01-e4fb9b7754adn%40googlegroups.com.

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Maurizio Torchio 
thank you cj.v... , but it does not work for me. 
it adds the class bubba to the textframe (just as 
$:/themes/tiddlywiki/vanilla/settings/editorfontfamily does), and on 
inspecting the element, font-family is correctly assigned but... nothing 
changes.
I think it has to do with what Jeremy said:

"The reason that custom fonts doesn’t work with the editor toolbar is 
because of the way that it creates the textarea element within an embedded 
iframe (this is done so that the selection in the textarea isn’t lost when 
the user clicks on a toolbar button and the textarea loses focus).

The iframe doesn’t inherit any of the styles in the main document, so the 
code actually creates a hidden textarea and then reads back the styles, and 
then applies them to the textarea in the iframe. That means that any 
formatting applied to the textarea will be faithfully reproduced within the 
iframe. However, it only works for CSS properties applied directly to the 
textarea; it doesn’t transfer fonts, animations or other resources that can 
be defined in CSS.

(The code is here: 
https://github.com/Jermolene/TiddlyWiki5/blob/master/core/modules/editor/engines/framed.js
)

We could update things so that special stylesheets identified by a new 
system tag such as $:/tags/Stylesheet/FramedEditor would be automatically 
inserted within the iframe." 

Il giorno mercoledì 1 dicembre 2021 alle 14:57:19 UTC+1 cj.v...@gmail.com 
ha scritto:

> G'day,
>
> If you are not averse to changing core TiddlyWiki templates, you could add 
> a style at the top of the content in $:/core/ui/EditTemplate/body/editor.
>
> See my screenshot below, in which I set the font to Brush Script MT 
> cursive.
>
> It would be good for more experienced TiddlyWiki users to chime in on any 
> downsides to this approach.
>
> *(BTW: please ignore the goofy-looking "!!! EditTemplate body" ... that's 
> me entering little breadcrumbs to figure out which core tiddler is which.)*
>
> [image: Screenshot 2021-12-01 9.52.23 AM.png]
>
> On Wednesday, December 1, 2021 at 6:19:45 AM UTC-4 torc...@gmail.com 
> wrote:
>
>> Hi everybody, any progress on this? (I really don't like see a different 
>> fontfamily when editing)
>> thank you so much for all the great work!
>>
>> maurizio
>>
>> Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha 
>> scritto:
>>
>>> Hi Alfonso,
>>>
>>> If I remember correctly the following comes from Jeremy's TalkyTalky 
>>>  which uses the Google font Lato:
>>>
>>> It contains the follwing stylesheet (a tiddler tagged with 
>>> $:/tags/Stylesheet):
>>>
>>> \define register-font(family,title,style,weight)
>>> @font-face {
>>>   font-family: "$family$";
>>>   font-style: $style$;
>>>   font-weight: $weight$;
>>>   src: url(<>) format("woff");
>>> }
>>> \end
>>> \rules only filteredtranscludeinline transcludeinline macrodef 
>>> macrocallinline
>>>
>>> /*
>>> ** Fonts
>>> */
>>>
>>> <>> "900">>
>>> <>> "italic" "900">>
>>> <>> >>
>>> <>> "700">>
>>> <>> "100">>
>>> <>> "italic" "100">>
>>> <>> "400">>
>>> <>> "300">>
>>> <>> "italic" "300">>
>>> <>> "400">>
>>>
>>> Hope that helps.
>>>
>>> Cheers,
>>>
>>> Ton
>>>
>>>
>>>

-- 
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/fd52f29f-17c9-47bc-8127-42e9cf18a8a9n%40googlegroups.com.

Re: [tw5] Re: Bug in TW 5.2.0 in zoomin view.

2021-12-01 Thread Jeremy Ruston 
Hi Siniy-Kit

> In TW 5.2.1-prereliase  everything is good. And it is great!

Excellent news, thanks for your help,

Best wishes

Jeremy

> 
> http://heeg.ru/shop2_3.html?id=10Q1RMs2QeKlvKywq7MGHSRltcDYXYTD5y2HFs0aygqE
> 
> понедельник, 29 ноября 2021 г. в 17:56:35 UTC+3, Siniy-Kit: 
>> Here  I have update my TW5 to 5.2.0  template. 
>> http://heeg.ru/shop2_3_.html?id=10Q1RMs2QeKlvKywq7MGHSRltcDYXYTD5y2HFs0aygqE#index
>> if I press back button (previous page) it scrolled to the bottom of the 
>> page. May be we can fix it by css styles?
>> 
>> вторник, 9 ноября 2021 г. в 19:57:29 UTC+3, jeremy...@gmail.com: 
>>> Hi Siniy-Kit,
>> 
>>> 
>>> I can confirm the problem with v5.2.0. I also checked v5.1.23 and it seems 
>>> to have the same problem.
>>> 
>>> Do you know when the problem was introduced? Did it indeed ever work 
>>> properly?
>>> 
>>> Best wishes
>>> 
>>> Jeremy
>>> 
>>> On Tuesday, November 9, 2021 at 4:45:33 PM UTC Jeremy Ruston wrote:
 Hi Siniy-Kit
 
 Thanks for the report, I'll investigate.
 
 Best wishes
 
 Jeremy
 
 On Sunday, November 7, 2021 at 9:40:19 AM UTC Siniy-Kit wrote:
> Jeremy, help me please. I want to update my template to  new version, but 
> it works only with zoomin view. 
> 
> четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 
>> Old TW5 works good. But now it has bad auto scroll while navigating 
>> between tiddlers 
>> For example open this tiddler https://tiddlywiki.com/#Filter%20Operators 
>> then make zoomin view
>> 
>>  then go back to Filter Operators tiddler and press "range"
>> 
>> 
>> after click you will see this
>> 
>> 
>> I want to see the top of this tiddler, but it autoscroll to middle. Can 
>> we fix this bug? 
> 
> -- 
> 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/767e74c3-36a7-4b8c-a633-0bb7f13b5c24n%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/6D8FC6F6-CBE2-4A68-BA85-C1476CD7F211%40gmail.com.

[tw5] Re: Bug in TW 5.2.0 in zoomin view.

2021-12-01 Thread Siniy-Kit 
In TW 5.2.1-prereliase  everything is good. And it is great!

http://heeg.ru/shop2_3.html?id=10Q1RMs2QeKlvKywq7MGHSRltcDYXYTD5y2HFs0aygqE

понедельник, 29 ноября 2021 г. в 17:56:35 UTC+3, Siniy-Kit: 

> Here  I have update my TW5 to 5.2.0  template. 
>
> http://heeg.ru/shop2_3_.html?id=10Q1RMs2QeKlvKywq7MGHSRltcDYXYTD5y2HFs0aygqE#index
> if I press back button (previous page) it scrolled to the bottom of the 
> page. May be we can fix it by css styles?
>
> вторник, 9 ноября 2021 г. в 19:57:29 UTC+3, jeremy...@gmail.com: 
>
>> Hi Siniy-Kit,
>
>
>> I can confirm the problem with v5.2.0. I also checked v5.1.23 and it 
>> seems to have the same problem.
>>
>> Do you know when the problem was introduced? Did it indeed ever work 
>> properly?
>>
>> Best wishes
>>
>> Jeremy
>>
>> On Tuesday, November 9, 2021 at 4:45:33 PM UTC Jeremy Ruston wrote:
>>
>>> Hi Siniy-Kit
>>>
>>> Thanks for the report, I'll investigate.
>>>
>>> Best wishes
>>>
>>> Jeremy
>>>
>>> On Sunday, November 7, 2021 at 9:40:19 AM UTC Siniy-Kit wrote:
>>>
 Jeremy, help me please. I want to update my template to  new version, 
 but it works only with zoomin view. 

 четверг, 28 октября 2021 г. в 15:52:49 UTC+3, Siniy-Kit: 

> Old TW5 works good. But now it has bad auto scroll while navigating 
> between tiddlers 
> For example open this tiddler 
> https://tiddlywiki.com/#Filter%20Operators then make zoomin view
> [image: Снимок экрана 2021-10-28 154440.png]
>  then go back to Filter Operators tiddler and press "range"
> [image: Снимок экрана 2021-10-28 154716.png]
>
> after click you will see this
> [image: Снимок экрана 2021-10-28 154853.png]
>
> I want to see the top of this tiddler, but it autoscroll to middle. 
> Can we fix this bug? 
>


-- 
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/767e74c3-36a7-4b8c-a633-0bb7f13b5c24n%40googlegroups.com.

Re: [tw5] Re: Embedding images on Android

2021-12-01 Thread Xavier Cazin 
Speaking of "local network host", there is an easy way to create one on
Android, using the RCX app. See instructions at the end of
https://talk.tiddlywiki.org/t/use-webdav-for-saving-a-single-file-wiki/441.
This would allow you to make the directory where your wiki resides
available to Chrome through webdav.

Cheers,
-- Xavier

On Wed, Dec 1, 2021 at 12:20 AM Joshua Fontany 
wrote:

> Chrome on Android cannot access local file paths:
> https://blog.chromium.org/2008/12/security-in-depth-local-web-pages.html
>
> This is an instance where having the images AS
> base64-encoded-image-tiddlers will work out "easiest". Otherwise, you'll
> have to host those images online or on a local network host, and make sure
> the _canonical_uris are pointing to the correct paths.
>
> Best,
> Joshua Fontany
>
> On Tuesday, November 30, 2021 at 1:29:53 PM UTC-8 alvi...@gmail.com wrote:
>
>> Hey guys,
>>
>> I'm new here. I've been having this issue where local images won't load
>> on android (Chrome) where they would on my laptop. I'm using the single
>> html file TiddlyWiki. I've tried having the image in the same directory as
>> well as in a sub directory. I first tried the [img[(file path]] syntax as
>> well as the _canonical_uri. Again they work fine on my pc but on android it
>> just shows this image icon.
>>
>> Does anyone know what's going on?
>>
>> Thank you,
>> Alvin
>>
>>
>> --
> 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/5c903670-f1a0-4009-9880-00683d790410n%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/CADeSwYOqvGXHgntmewOY7hrk1cy7w3kbb%2BONiOcRMwJYFUXtFg%40mail.gmail.com.

[tw5] Re: [tw] Using Custom Font in Tiddler Editor

2021-12-01 Thread Maurizio Torchio 
Hi everybody, any progress on this? (I really don't like see a different 
fontfamily when editing)
thank you so much for all the great work!

maurizio

Il giorno martedì 30 gennaio 2018 alle 21:09:06 UTC+1 Ton Gerner ha scritto:

> Hi Alfonso,
>
> If I remember correctly the following comes from Jeremy's TalkyTalky 
>  which uses the Google font Lato:
>
> It contains the follwing stylesheet (a tiddler tagged with 
> $:/tags/Stylesheet):
>
> \define register-font(family,title,style,weight)
> @font-face {
>   font-family: "$family$";
>   font-style: $style$;
>   font-weight: $weight$;
>   src: url(<>) format("woff");
> }
> \end
> \rules only filteredtranscludeinline transcludeinline macrodef 
> macrocallinline
>
> /*
> ** Fonts
> */
>
> < >>
> < "900">>
> <>
> < "700">>
> < "100">>
> < "italic" "100">>
> < >>
> < >>
> < "300">>
> < "400">>
>
> Hope that helps.
>
> Cheers,
>
> Ton
>
>
>

-- 
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/6e0fbd90-a27c-433f-a93c-9973e6addf3en%40googlegroups.com.

[tw5] Re: On using a hierarchical notation for tiddler titles to support better retrieval and naming

2021-12-01 Thread PMario 
Hi,
We call this type of tiddler titles "namespace" and we use it for core 
tiddlers. 
The first TW namespace uses $:/ prefix for all system tiddlers. eg: 
$:/temp/, $:/state/ and so on. 

There is a macro named: tree-macro used like: `<>` ... that should work for you. 
See the docs about the tree-macro 


have fun!
mario


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