Custom CSS bugs

mariusu

I’ve been an early Moo.do user, went away for a few years, then rediscovered it as Legend. I am mindblown by how much the app has evolved and I’ve switched to it and never looked back!

I am using the MacApp, but there are several issues with the editor, most of them due to automatic reformatting of CSS:

New classes are not always added - or if they are added, they are moved around and hard to find.
Hard to work with indentation (Tab key does not work, indenting with spaces is odd).
Changing existing classes works. Adding new classes/styles does not work.

So two fixes are needed:

Do not reformat the CSS upon saving (if we need to reset, we can use the reset button).
Make sure that all custom CSS reflects in the UI (which means it’s loaded last)— this will allow power users to control the UI to their liking.

Thank you so much for your work!

Marius

Jay

This is because it’s not exactly a CSS per-se - it’s more of a custom editor for changing the built-in theme styles, and changes a theme object under the hood rather than being like a css file. That’s why adding other classes does not work.

We could consider changing how that works though. Could you tell me more about what kinds of classes you’re trying to add? A video of what you’re trying to do would be super helpful if you have time to record something 🙂

mariusu

Jay just following up on this. Would it be possible to just allow extra classes in the current CSS editor for the theme? It would be of great help to improve some UI inconsistencies (like calendar events overlapping despite being in different slots etc., alignment, etc.).

mariusu

Hi Jay,

The app looks great and there are several reasons why I would want full CSS control:

Fix minor UI inconsistencies (rather than bother you with them). Sometimes, things are not pixel perfect or even confusing (dragging an email into a todo list).
Personalized theme. I want to experiment with different alignments, tags, etc. This requires using multiple classes/selectors/pseudoelements in the CSS declarations — which get ignored/removed.
Productivity in experimenting with UI changes. Now the CSS gets reformatted and the editor is very clumsy (especially with indentation).

So, as a solution, I’d rather see one CSS (which can be reset to your default), fully customizable (loaded AFTER the default CSS, as a “theme”). Splitting the custom CSS in two (color/layout) is also somehow confusing for someone who uses CSS, because of having to change in two places if you want to customize a single UI component.

Happy to jump on a call for more details—I don’t know what I can record as a relevant video).