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
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.)
1 Like
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."
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."
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.
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.
1 Like
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
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?
thank you Charlie and Jeremy! yes: mine is a font-face.
the problem is: I love fonts! I use different fonts for different wiki, they embody the “soul” of the wiki (and I’d like to have the same font whether desktop or mobile, viewing or editing). that’s why until now i used the edit widget for editing. but this means: no toolbar, and it can be annoying, especially on mobile.
anyhow: thanks again for this priceless tool!
m.
thank you Charlie and Jeremy! yes: mine is a font-face.
the problem is: I love fonts! I use different fonts for different wiki, they embody the “soul” of the wiki (and I’d like to have the same font whether desktop or mobile, viewing or editing). that’s why until now i used the edit widget for editing. but this means: no toolbar, and it can be annoying, especially on mobile.
anyhow: thanks again for this priceless tool!
m.
Have you tried using the CodeMirror plugin? It allows you to change the editor font family through $:/ControlPanel settings panel
Best wishes
Jeremy
WOW! IT WORKS
I’m… elated.
Hi Maurizio,
That’s great to hear, I’m sorry I didn’t mention that option before.
Best wishes
Jeremy
PS - do send a screenshot of what you’ve ended up with, it might inspire others…
ok, this is a mobile screenshot. we are viewing a tiddler called “esistenza”. (the only content of “esistenza” is macro I use to edit/view/abstract/annotate/reorder all the tiddler tagged with “esistenza”). the tiddler “attraversare-ponte” is now in edit mode (inside “esistenza”). and it displays the same wonderful Baskerville it shows in view mode!
the only problem is that now .tc-editor-toolbar {position: sticky; top: 0;} doesn’t work anymore… I still haven’t guessed why
If of any use to anybody, here’s how I’ve setup the editor to use a www.w3schools font face. (I’m figuring TiddlyWiki could use a font face file sitting in the same file folder as the TiddlyWiki.)
1 Like
Hi Charlie, using a local font file, i.e
@font-face {
font-family: ‘CormorantGaramond’;
font-style: normal;
font-weight: 400;
src: url(./tiddly/CormorantGaramond-Regular.ttf);
}
does not work (it works anywhere in the wiki, but not in the EditTemplate).
anyhow, even if it worked, I prefer to have a single file (that’s why i use this method to embed my font-face: http://kookma.webfonts.tiddlyspot.com/)
summing up: CodeMirror plugin solves the problem (and of course adds other nice functionalities too) BUT the EditorToolbar does not stick anymore (to the top of the screen when scrolling). ie.
div.tc-editor-toolbar {
position: sticky;
top: 0;
}
does not work anymore.
(having a sticky toolbar is quite useful for me in mobile mode). (i tried to change to visible the overflow in CodeMirror to no avail).
thank you very much anyhow!
maurizio
1 Like
To Whom It May Concern: it was just a silly z-index problem.
div.tc-editor-toolbar {
position: sticky;
top: 0px;
z-index:1;
}
now I can use embedded font-face in the editor (thanks to CodeMirror) AND have a sticky toolbar. (and I’m perfectly happy!)
: )
nope. I spoke too soon. CodeMirror manage badly text selection on touchscreens. looks like CodeMirror 6 will fix this but until then… it’s of no use for me.
: (
Confirmation that this does indeed work with a local file.
(Well, unless there is something wonky going on. Maybe somebody else can confirm with their own computer setup. I am using a Chromebook.)
I went to Google Fonts and downloaded the Cormorant Garamond font family. In the ZIP file, I copied the CormorantGaramond-Regular.ttf file to the same folder in which the TiddlyWiki file resides.
See screenshot below, Note edits to core tiddler. In particular, the “./” when specifying the font-face src and let’s not forget (like I first did) to include that third class for the edit widget.
hmm… I really do not understand. For me it does not work, neither in firefox on windows nor in Chrome on windows.
The font file is accessible (because it can be used in view mode). but in edit mode it does not work.
anyhow: thank you Charlie for all the time you dedicated to this topic!
mt
1 Like
You have single quotes around the font-family name references in both “@font-face” and “.bubba” style sections.
I don’t in my sample.
I have no idea if that makes a difference.