How about doing what GNOME does with Adwaita where a small drop shadow is applied on the bottom of the button to create the illusion of a push-in-able button only for the shadow to then go when the button is being pushed down?
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Nov 16 2019
Oct 23 2019
Edited code based on feedback and added Latte Dock layout and BorderlessMaximisedWindow value changing functionality
Added in the Latte Dock changing to patch D23117, however direct layout importing is not yet implemented into this patch (I think that should come in a later patch at a later time as you're still working on getting the code completely done on Latte's side at this point in time anyway).
Added support for BorderlessMaximizedWindows and specifying a Latte Layout - Based on a code review, re-added original behaviour for Splash Screen setting if there's no 'defaults' file
Started working on a patch for the Latte Dock layout specifying part at least. Is there a DBus Signal I can use for cleanly quitting Latte so that Look & Feels can also specify to not have Latte running at all?
That is a pretty good idea. Also for Latte not running we can use KWriteConfig for the layout changing part too so it always changes no matter what, though Import will be another pain of its own, potentially.
Oct 22 2019
In T7622#204511, @mvourlakos wrote:@The-Feren-OS-Dev hello I read at a new article at https://medium.com/feren-os/a-whole-slew-of-updates-got-released-for-feren-os-next-6c880d6eedda that you are playing with Latte and more specific:
lattedockrc: UniversalSettings: currentLayoutI suppose you are using it in order to swich at a Latte layout. I would like to ask if you are using the dbus way or manually(1. close Latte, change the currentLayout and reload Latte afterwards)
Sep 19 2019
@fvogt Nope, but now you've mentioned that I've added an extra line if there's no defaults file found to set the Splash Screen to be the Look & Feel name like it originally would do.
- Based on a code review, re-added original behaviour for Splash Screen setting if there's no 'defaults' file
Sep 16 2019
Sep 4 2019
Alright, in terms of strings if I were to make one suggestion it'd be this:
Change the SHIFT tips to language like "(Hold SHIFT to Blah)" (e.g.: "Hold SHIFT to Magnify").
Sep 3 2019
To be honest I'd say it'd probably look better if it's more in-line with how status boxes look on Discover (and throughout Kirigami, IIRC) style-wise with its background, border and shadows, but hey that's just my opinion on it.
Aug 26 2019
Pong.
Aug 23 2019
If I add my late input on this: I'd say the + should indeed be on the right side of the input and on the right of - so that both are touching each other. Just that this is the most commonly used design that users except for a spinbutton outside of both being on top of each other (aka the currently used design), plus it'd add a bit of consistency with the GTK Breeze themeing.
Aug 13 2019
Aug 12 2019
Jul 18 2019
In T11227#192242, @cblack wrote:In T11227#192240, @The-Feren-OS-Dev wrote:-snip-
That means instead of the loading bar we should then just have the spinning indicator. While it may remove some detail in terms of how much a program has left to load, we can either move that into their window list item's progress bar ala Spectacle's timer or we could just take into account the fact that once it starts progressing it'll most likely be finished doing whatever it does on most of these applications anyway in a few seconds (therefore making having a progress bar redundant anyway).The point of a longform loading screen is to be for things that may not complete in a few seconds like refreshing repositories on Discover's start (add distro repositories + repos for universal packages and there's probably a lot to do). Nothing kills user experience more than a dreaded nonstop loading screen with an indeterminate indicator. If loading must take a while, there should be effort to let users know how much time is left or how much is done versus how much there is to do.
In T11227#192173, @cblack wrote:In T11227#192157, @ngraham wrote:GNOME does something pretty nice: they draw a blank/white background with a monochrome desaturated version of the app's icon in the middle. It looks really classy IMO. We could do the same, maybe also with a monochrome desaturated indeterminate progress bar below the icon.
That's pretty much the long form loading that I described - mostly because that's what I drew most of my inspiration from.
The example I gave of what Discover could be is literally just a description of GNOME Software's start loading screen
Jun 10 2019
I'd like to step in here if it's fine. I've been working on Feren OS Next, a Plasma-using Ubuntu Distribution that aims to do multiple things. One of those things happens to be providing a more-complete Look & Feel layout application process which affects more than what it currently does.
Examples of things it also affects includes:
- The current Latte Dock layout being used
- The titlebar buttons layout in both KWin and GTK Headerbars (when used in conjunction with an XSettings Daemon like the one Feren OS Next uses, otherwise only KWin is affected)
- The applied GTK 2 and 3 theme
- The icon set applied to GTK 2 and 3 Applications to add consistency
- The cursor theme applied to GTK 2 and 3 Applications for the same reason
- Whether titlebars are hidden on maximise
- Whether to assign Meta input to Latte Dock or Plasmashell (this was before I found out that Latte Dock made that an option in their Settings window)
- More