Adrián Pérez @aperezdc@mastodon.social

Today's #opensource #typography recommendation is the beautifullt designed Gidole typeface → http://gidole.github.io/

% apropos pinky
pinky (1) - lightweight finger

Seems about right. #unix #commandline

(Kudos if you thought “this one goes up to eleven” and secretly giggled for yourself.)

0. Grab a good pair of headphones.
1. Crank up the volume.
2. Open https://www.youtube.com/watch?v=xS9hYS9guRU&list=PL2c62ZQ8kOmn8rXktiGgiCqcPBgwuhqqE
3. Enjoy 🤘

Today I didn't have the chance of writing much code for upstream projects. Still, I can offer you a quick hack: a #Zsh plugin to quickly search and create text (Markdown) notes: https://github.com/aperezdc/zsh-notes

This came to be after a workmate mentioned terminal_velocity for note taking, saying that probably I would be able to cobble together something similar in a shell script. He was right.

Today I made a follow up to yesterday's #GIMP patch. In modern #webkitgtk the WebKitWebView widget does not need to be inside a GtkScrolledWindow because it handles scrolling (and painting of scroll bars) by itself.

This MR simplifies the code a bit by removing the unneeded GtkScrolledWindow: https://gitlab.gnome.org/GNOME/gimp/merge_requests/17

Yay, this just got merged into the GIMP repository 🙌

There are improvements that could be made, but at least the help browser and the web page capture plug-ins are back!

I may have accidentally^W ported the GIMP plug-ins that use WebKitGTK+ to the current API, which makes them usable again in the GTK+ 3 port: https://gitlab.gnome.org/GNOME/gimp/merge_requests/15 #coding

This will allow solving https://github.com/Igalia/cog/issues/11 and that makes me happy.

So far I haven't worked on actual code today, but at least I've already gone through bugmail and reviewed the chabges needed to add API in WPE which will allow specifying the back end library to use:

- https://github.com/WebPlatformForEmbedded/WPEBackend/pull/18
- https://bugs.webkit.org/show_bug.cgi?id=186841

It may not sound like a big deal, but it will allow sharing the same WPE WebKit build among different applications, regardless of which back end they want to use.

FTR, Cog is both a launcher/browser which uses the WPE WebKit port, and a library that can be used to implement your custom one. So far in the few situations it's used the custom version didn't happen, and Cog (the browser) ended up being improved instead. In beginning to question the whole library thing, specially if the support for plugins proves enough.

Dunno, or maybe even without the CW. I guess talking about code is in general neutral? What does the #fediverse think?

Not sure how long I'm going to keep it up, but let's do some posting under the “coding” CW. About thing I do for work (and fun sometimes) which are Open Source.

Quite happy about where the direction that this refactoring is taking: https://github.com/Igalia/cog/pull/41

Depending on how this evolves, I might consider removing libcogcore, which currently provides functionality used by Cog only, and exposing only extension points — I'm not aware of any other browser using libcogcore anyway.