subtle isn't dead yet! (1 comment)
if anyone noticed, I couldn't make it to this year's FrOSCon, I rather spent the time sick in bed, so I hope you enjoyed it even without a subtle booth.
I took quite a long break from development, toying around with some Android ideas and dealing with some nasty project deadlines. Nevertheless, the project isn't dead yet, I actively use it daily and I am still very pleased and still want to go on.
There are some features that currently aren't pushed like virtual screen splitting, but I am eager to make them available once I finished the styling thing I have in my mind.
So be patient with me.
Previously the .spawn method belonged to Subtlext::Subtle, which was fine until I changed it to return a valid client object that is backed with some light event caching to make it useful for e.g. the launcher. Since it returns a real object I think it should belong to Subtlext::Client, end of story.
Edit: This change also breaks the scratchpad snippet, so make sure to change Subtlext::Subtle.spawn to Subtlext::Client.spawn in your config.
Sometimes it can be pretty nasty to add tags, when you just need something stupid to move a certain window to a view. That can be done with a loop, but that also adds lots of tags and there cannot be more than 32 of them.
An easy way to bypass this is to add logic to tags and act differently for certain clients. The latest version of subtle extends the properties with on_match. This can be used to add a Ruby proc to a tag that is called whenever the tag is applied.
When you are located in Germany, live close to Oberhausen and have some spare time this weekend (12/13.11) visit us at our booth at the OpenRheinRuhr.
Finder in subtlext (1 comment)
Finder in subtlext are used to select different kind of objects like one client or more clients based on different matching options. With the changes in r3104, #find and # always return an array regardless whether an object was found or not. If you need just one result use #first instead.
Separator and styles revamped (3 comments)
According to my plan, to combine styling options ultimately in the styles it is now time to move the separator. A nice side effect, is that this allows different separators for views, sublets and the panel in case you ever wanted to do that.
Another change is the removal of the unoccupied style, it made no sense at all, TBH. Unoccupied views are just views and this is probably not worth a special state. Just make sure to think twice what values are inherited now and which one you need to overwrite. (Joy of inheritance)
TL;DR: You need to update your config, again. Move the separator config option to the separator style like this:
Therefore, r3023 adds a new optional style to highlight visible views. This style defines additional values, that are assigned on top of the current style values like :occupied. I also changed the :urgent style to behave similar.
So if you are around - visit us.
And the second probably unoticed change is the addition of a more flexbile way to enable gravity tiling. Instead of just enabling it globally this can be a) done per gravity now and b) either horizontally or vertically.
I did it again, Styles have changed slightly. This time without any breakage of existing configs, just expect some deprecation warnings and adopt your configs over the next weeks.
Why more changes?¶
The styles are a bit odd, there are some real classes and some other are mere states of a existing class. Yes, I am talking about the view styles. We have :focus, :occupied, :unoccupied and :urgent: Each inherits from :views and :views from :all and makes no sense as standalone style. So what we really need is a way to define nested styles.
Also the foreground, background, text_fg and icon_fg config option mess requires a sane solution with styles.
What has changed?¶
Subtlext::Sublet have a #style= method to set these styles.
Long story short¶
|Styles for sublets||
|Update sublet colors||
Also available in: Atom