Better theme config about superfile

[AnshumanNeon]

i absolutely love the toml file but i don't think that a json file is any bad. It just needs better naming conventions.

[AnshumanNeon]

i also prefer it. I just wanted to say that json doesn't feel that bad. But yeah, toml is nice. I will look forward to it. You can call me to translate the themes

[AnshumanNeon]

i like this

[yorukot]

Thank you for bringing this up
I have never designed a theme. I may redesign the theme file in a few days.May i ask for your suggestion?

[lescx]

Sure thing. A few suggestions:

A short design lecture

A common design pattern is to separate UI elements like menus from the main editor/work UI element. In the case of a file manager, the editor would be your file selection(s).

There is also a design decision to be made about whether or not to use a border. IDEs often allow the use of two different themes based on this concept - bordered and borderless themes.

Menu items and borders have two properties that need separation in design:

1. Active/Inactive(/Last) item. These often have different text or border colours. Design implies function. For example, for the Processes window in the superfile for a light theme:

Normal text in processes: primary (middle)
Border (active): secondary color (brightest)
Processes: tertiary color (darkest)

2. Visual coherence. For a side menu, these are handled by a background colour different from the editor or a separation by a border colour != the text colour.

An example of this using my Tmux status bar:

On the left is our "menu". The keyboard shortcuts (1, 2, 3) are the same because they serve all the same purpose. The text marks the current active or inactive window. In tmux you can also implement a "last window" state but I don't use that feature.

Although it is cleaner and perhaps more aesthetically pleasing to use the same background colour for the rest of the terminal, it is good to have a separation in context.

Notes

I am against supporting legacy standards until the world freezes over (4 bit, 8 bit colours).
Still, it might be a consideration to support 256 colors for terminals that do not support true color. terminfo should handle this… terminfo is broken. Helix and Neovim check if the terminal supports true color. Also, there is the $COLORTERM variable used by some applications (Helix uses it to force 24 bit colors if the terminal doesn't tell it correctly but supports it anyway).

---

I'm at university right now. I will come back in a few hours and come up with a mock-up for the theming with a JSON.

[yorukot]

Oh my god

I really appreciate you typing up such a long list to introduce knowledge about the theme!!

[lescx]

It is common to write config files for in Go written applications in toml. This would be my first take on how to properly define a theme architecture.

[theme.your-theme]

# Text Colors
text_primary = "" # Default text color
text_secondary = "" # Often less colorful version of primary; e.g. non-active border
text_tertiary = "" # Accent text color for special stuff, e.g. `Processes`, `Clipboard` text

# Background
background = "" 

# Borders
border = ""        
border_active = ""  

# Special Colors
hint = ""
info = ""
warning = ""
error = ""
accent = ""  # E.g. default folder color

# Gradient
# The gradient could also be used for the Super Files" in the top left corner after opening `spf`
# or for loading animations when there is a blocking wait going on.
gradient_color_1 = ""
gradient_color_2 = ""

# Cursor
cursor = ""
selection = ""
selection_active = ""

Also, a few things I noticed:

Documents should be the same color as the other entries in the directory selection but bold.

The icon next to /home/luca/.config/superfile should be the same as the folder icon in the file browser. No need to specify a new color for this icon.

Clipboard and Browser 1/4 should be the same tertiary color, no matter if one of them is the active tab or not.

[yorukot]

i will update this!

[yorukot]

I think the bottom and sidebar border_active need to be separated separately

selection = ""
selection_active = ""

what is this different

[lescx]

I think a TOML file is easier to use for a config file which gets edited by an end user. A lot of popular applications use TOML (or plain old key = value which is easy to parse). I don't see that for JSON.

[AnshumanNeon]

yes it is easy. but json isn't hard too. We can change to toml anytime. I would require a bit of changing packages and code in the src code. But it will be a piece of cake on the user customization side of things

[yorukot]

So I think I'm going to change all the config files to toml, which I think is better.

[AnshumanNeon]

all themes are translated now.

[yorukot]

Thank you so much!

I'm still trying to redesign the new theme configuration.

[yorukot]

# Border
file_panel_border = "#868686"
sidebar_border = "#868686"
footer_border = "#868686"
modal_border = "#868686"

# Border Active
file_panel_border_active = "#FFF1C5"
sidebar_border_active = "#D79921"
footer_border_active = "#D79921"
modal_border_active = "#868686"

# Background (bg)

full_screen_bg = "#282828"
file_panel_bg = "#282828"
sidebar_bg = "#282828"
footer_bg = "#282828"
modal_bg = "#282828"

# Foreground (fg)

full_screen_fg = "#EBDBB2"
file_panel_fg = "#EBDBB2"
sidebar_fg = "#EBDBB2"
footer_fg = "#EBDBB2"
modal_fg = "#EBDBB2"

# Special Color

cursor = "#8EC07C"
correct = "#8ec07c"
error = "#FF6969"
hint = "#468588"
cancel = "#838383"
warn = "#FF0000"
gradient_color = ["#689d6a", "#fb4934"]

# File Panel Special Items

file_panel_top_directory_icon = "#8EC07C"
file_panel_top_path = "#458588"
file_panel_item_selected_fg = "#D3869B"
file_panel_item_selected_bg = ""

# Sidebar Special Items

sidebar_title = "#CC241D"
sidebar_item_selected_fg = "#E8751A"
sidebar_item_selected_bg = "#282828"

# Modal Special Items

modal_cancel_fg = "#EBDBB2"
modal_cancel_bg = "#6D6D6D"
modal_confirm_fg = "#EBDBB2"
modal_confirm_bg = "#FF4D00"

What do you guys think about this

[yorukot]

#66