Warning
For "futofied" themes, the hint keys are intentionally transparent (they may look invisible even when enabled). This is a clean, personal preference.
If needed, you can make them visible by changing the foreground value for key-hint element in the theme options
Note
One-handed panel buttons may appear slightly off when using this FloriStyle version with FlorisBoard v5.2.0 or earlier
🆕 New Features
- Add new bordered MY themes "inspired" by Futo UI
- Add styles to support new floating window feature introduced in the FlorisBoard
v6.0.0-alpha01(#37)
🚀 Enhancements
- Make colors more vibrant again by updating the new
Pallete styleFlorisBoard option fromNeutralto defaultTonal Spot - Add property for popup URI, decreise size and max-lines visibility (
.edu,.com,.gov,.org,.net) (#36) - Remove
marginfromkey-popup-elementto prevent character clipping - Update all themes in the background to uniform the code. Some elements may look a little different then before
- Update file name from
gboardishtofloristyle
📝 Fix for monochromatic mode
Since the v0.5.2 FlorisBoard update, there is a noticeable shift in how system colors are processed. For users who prefer a pure monochromatic look, you might notice that some areas now have a blue-ish tint instead of staying neutral grey (specifically secondary-related and surface-related colors. For more you can check out this PR discussion
If you are using FloriStyle and want to restore a strictly greyscale palette, you can manually define the behavior within the theme settings.
Here is the extra step:
- Navigate to
Addons & Extensions>Theme extension - Select FloriStyle themes and tap
Edit - Locate your active theme and tap
Edit - Tap
Editagain in the first section (where the theme title and metadata are) - Scroll down to the
"Material You"heading - Under
Palette Style, manually switch the setting toMonochrome
Note
Just keep in mind that if you ever want your keyboard to follow a colorful system theme again, you'll need to go back and revert this setting.
If you know of a more efficient approach or if I've missed a simpler way to handle this, please feel free to share. I'm always looking to refine these steps.
Full Changelog: v5.1.1...v6.0.0