Themes too difficult

Yann1ck · 2021-11-09T13:46:06.820Z

Yeah, those themese dont look too nice. Have you tried plugin themes? They look much nicer.

This topic will only be updated when there are new or updated plugins. The following report was created on 2023-12-12 16:38:49 +0000 Updated plugins Plugin Version Freehand Drawing 2.7.1 Plugins Name Version Description Author ABC Sheet Music Plugin 1.0.3 Turns ABC text notation into sheet music Laurent Cozic Admonition markdown extension 1.1.0 Enables markdownIt…

iomari · 2021-11-09T14:06:31.122Z

Now I can't install plugins from a file.
The Manage your plugins->install from file, doesn't bring any dialog box. Nothing happens when I click it.
This is the same behavior when I try to import or export fro the file menu.
What's up?

james-carroll · 2021-11-09T14:07:35.588Z

That was a bug with the 2.5.8 release on Linux, try 2.5.10

iomari · 2021-11-09T14:08:04.415Z

thanks

iomari · 2021-11-09T14:40:31.758Z

Ok, I updated Joplin, now the dialogs are appearing but they appear behind the main window. It took me awhile to figure out that they were present..
This happens every time.

JackGruber · 2021-11-09T14:46:40.002Z

Plugins can also installed manual.
Drop the jpl file into .config\joplin-desktop\plugins

iomari · 2021-11-09T15:09:34.207Z

thanks

former_evernotist · 2021-11-09T23:30:29.867Z

I second @iomari's suggestion because in my humble opinion there's an issue with lack of contrast in the default settings: When I use the split-screen markdown editor (which I like very much because it gives me a 'centred' experience just like reading mode in Firefox), the font colour (light theme) seems somewhat greyish to me (not black).
What's even more problematic is the dark grey scrollbar in the notebooks section on the left of the screen: almost indistinguishable from the black background so that I accidentally end up nesting notebooks when I fail to hit the bar for scrolling.
Customisation is one of the great strenghts of Joplin, but for those unacquainted with CSS (or at least with its practical usage) it's rather hard to tackle with these issues.
Joplin 2.5.12 (prod, win32): really great app nonetheless!

dpoulton · 2021-11-10T13:53:48.646Z

@former_evernotist I too found the default light theme lacking a little bit of contrast.

Below is some css I have collected over the years to put a bit of contrast into the Joplin light theme. It still seems to work and It also makes the scrollbar easier to see.

I have commented the css so you can remove any bits you do not want / need.

userchrome.css

Click to expand

/* ==Interface modifications== */

::-webkit-scrollbar-thumb {
    /* changes the scrollbar slider colour */
     background: #c0c0c0 !important;
}
 div.note-list-item span {
    /* notelist - note title text */
     color: black !important;
}
 input.title-input {
    /* note - note title text*/
     color: black !important;
}
 a > span.icon-back,
 a > span.icon-forward,
 a > span.icon-share,
 a > span.icon-bold,
 a > span.icon-italic,
 a > span.icon-link,
 a > span.icon-code,
 a > span.icon-attachment,
 a > span.icon-bulleted-list,
 a > span.icon-numbered-list,
 a > span.icon-to-do-list,
 a > span.icon-heading,
 a > i.fa-ellipsis-h,
 a > span.icon-add-date,
 a > span.icon-layout,
 a > span.icon-info {
    /* changes toolbar icon colour - inactive icons are a % of this colour*/
    /* these can be broken out into individual entries if a "rainbow" of colours is wanted*/
     color: black !important;
}
/* Start - the below section is not required if you do not use the "Menu items, Shortcuts, Toolbar icons" plugin */
 a > i.fa-highlighter,
 a > i.fa-strikethrough,
 a > i.fa-underline,
 a > i.fa-superscript,
 a > i.fa-subscript {
    /* changes the "Menu items, Shortcuts, Toolbar icons" **plugin** toolbar icon size and colour - inactive icons are a % of this colour*/
    /* these can be broken out into individual entries if a "rainbow" of colours is wanted*/
     font-size: 1em !important;
     color: black !important;
     font-weight: 600 !important;
}
/* End - the above section is not required if you do not use the "Menu items, Shortcuts, Toolbar icons" plugin */

/* ==CodeMirror editor modifications== */

 span[role="presentation"] {
    /* editor pane text */
     color: black;
}

userstyle.css

Click to expand

 body,
 table th,
 table td {
    /* sets body text, table cell, and header cell font colour */
     color: #000000;
}
 code {
    /* sets code font colour - fenced code, inline code and pre */
     color: #000000;
    /* stops code boxes extending off the note page */
     white-space: pre-wrap;
}
 caption {
    /* puts a table caption underneath the table rather than the default (above) */
     caption-side: bottom;
    /* sets the colour of the table caption */
     color: #000000;
}

former_evernotist · 2021-11-10T14:41:56.275Z

Thank you very much @dpoulton! It's good to hear that things still work because there's this official warning somewhere else in the forum that every CSS customisation can potentially become unusable after an update…
Strange thing is that contrast in the markdown editor seems to be better on smaller and sharper screens such as a 12" Surface. Large fonts on a 17" laptop tend to look rather grey and blurry, but maybe I should check first what colours are effectively encoded (after giving up my reluctance to CSS tweaks of course…).

dpoulton · 2021-11-10T15:48:09.168Z

former_evernotist:

... that every CSS customisation can potentially become unusable after an update…

Yes, that's true and is why I mentioned it! However it's not that common and, of course, the less you customise the less chance there is that something will stop displaying as you wanted it to!

former_evernotist:

Large fonts on a 17" laptop tend to look rather grey and blurry,...

It's possibly not that strange. If the 17" screen has a comparitively lower resolution (pixels-per-inch) the font-smoothing can become more noticeable and make the letters look at bit "greyer / blurry".

Looking into Joplin shows that the default editor text colour is #32373F which is noticably lighter than black and can then be made to look a bit lighter again by font-smoothing.

colours

former_evernotist · 2021-11-10T16:23:29.860Z

Thank you very much again for that clarification! So I would like to suggest that the standard font should be made blacker and the bar for scrolling the notebooks list be made lighter - and all would be so well...
Maybe I'm a bit obsessed with UX issues, because one of these made me leave Evernote (not privacy concerns, although I know I should have had them all along). After switching form Android to iOS I was shocked to discover that Evernote doesn't support dynamic text (which it does on Android), and the standard font is ever so tiny. But that's what I pointed out in another posting:

iOS: dynamic text feature Features

Is it correct that Apple's dynamic text on mobile devices only works with Joplin's markdown editor, not with the viewer that's rendering markdown? As a workaround for better accessibility, I use the editor for viewing, but scrolling is no fun with the keyboard displayed on the lower half of the device. Evernote and OneNote offer the ability to collapse the keyboard and hide it from view, but that function seems to toggle viewing and editing modes, so it doesn't provide a customizable viewing si…

3ter · 2021-11-16T19:57:46.433Z

I really hope someone helps Ohmine to gain some traction by adding an easy switch. It's pure eyecandy imho

github.com/Nacandev/Ohmine-Dark-Theme-For-Joplin

[feature-request] Make this theme a plugin

opened 10:17AM - 02 Nov 21 UTC

closed 09:09PM - 10 Nov 21 UTC

3ter

I'm really enjoying this theme but I'd like to be able to switch back and forth …easily. What do you think about packing it as a plugin like the [macOS-Theme](https://github.com/ajilderda/joplin-macos-native-theme) did? Thanks for all your magical `important!` CSS efforts :slightly_smiling_face: .

fernlover · 2021-11-17T14:22:12.711Z

I can definitely second the general sentiment.

Some time ago Joplin changed its default styles to add padding on the sides; this was undesirable for my purposes, so I went to revert the change and found out about the process, which involves hunting down classes in the dev console for each one of the several different editing components that Joplin uses.

The nitty-gritty details of the process are virtually undocumented, making even simple modifications opaque and time-consuming.

Daeraxa · 2021-11-17T14:41:07.437Z

Out of interest what padding are you referring to?

I would argue the main areas are pretty much covered.

Selection of inbuilt themes
Addition of theme via plugin (like macOS theme)
Addition of themes via CSS
UI modification for advanced users by CSS.

I wouldn't say that eliminating UI padding by modifying the application CSS is a standard user practice, many apps don't offer anywhere near that level of granularity outside of advanced config such as css.

fernlover · 2021-11-17T22:51:00.505Z

Daeraxa:

Out of interest what padding are you referring to?

On the sides of the editing area, to limit line length.

Daeraxa · 2021-11-17T23:10:37.972Z

If you mean the editor width then you didn't need to do it via css:

Please read this if you are wondering why there's now a margin on the note text News

The latest version of Joplin sets a maximum width for the note content in order to improve readability. You can disable this by going into Configuration > Appearance and set the width to "0".

fernlover · 2021-11-21T02:13:29.066Z

That's good to know! But it doesn't change the fact that doing it manually takes quite some work and requires figuring out stuff by trial and error because it's undocumented.

(Ofc if documentation has been published since my last search on the subject I'd be very happy to be proven wrong).

The core of the problem seems to boil down to with the way Joplin is put together, and more or less the same reason why it's impossible to do any editing on Android that isn't super basic (albeit, the last time I did attempt that was quite some time ago, so if things have improved I'll stand corrected).

For whatever that may be worth, as it is my understanding, that any attempt at remediation would require a significant, lengthy effort. So, thanks for the pointer.

PS: and also, apologies for the brief diversion from the specific topic of discussion.

Daeraxa · 2021-11-21T02:55:13.935Z

fernlover:

But it doesn't change the fact that doing it manually takes quite some work and requires figuring out stuff by trial and error because it's undocumented.

I don't think it is normal to document literally every setting, feature and button of an application if they are somewhat self-documenting - the setting in question already has a description in the setting wording. It was included in the change notes (granted I think the wording isn't as clear as it could be but it wasn't some hidden setting with a complicated way of changing the value).

fernlover:

The core of the problem seems to boil down to with the way Joplin is put together, and more or less the same reason why it's impossible to do any editing on Android that isn't super basic

I don't quite understand what is meant by this? What exactly is this reason and how does an appearance setting relate to the mobile editor?
As for editing on mobile, the new beta editor is certainly better than the old one, the main issue for me is just inputting markdown via a stock mobile keyboard is a bit of a faff (mostly making task lists).

system · 2021-12-21T02:55:21.372Z

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.