diff --git a/content/posts/borg-backup-continued/index.md b/content/posts/borg-backup-continued/index.md index 0aeb02e..674313d 100644 --- a/content/posts/borg-backup-continued/index.md +++ b/content/posts/borg-backup-continued/index.md @@ -200,4 +200,4 @@ But at least from my side: thanks to the BorgBackup developers to provide the wo At least my backup setup got successfully assimilated .P -{{< image src="/posts/borg-backup-continued/images/borg-backup-logo.png" alt="BorgBackup" >}} +{{< image src="images/borg-backup-logo.png" alt="BorgBackup" >}} diff --git a/content/posts/borg-backup/index.md b/content/posts/borg-backup/index.md index a76bb64..96ce857 100644 --- a/content/posts/borg-backup/index.md +++ b/content/posts/borg-backup/index.md @@ -48,7 +48,7 @@ duplicity is just nicely installable via pkg there, too! I investigated a bit more what I could use as duplicity replacement, and ended up giving [BorgBackup](https://www.borgbackup.org/) a try. -{{< image src="/posts/borg-backup/images/borg-backup-logo.png" alt="BorgBackup" >}} +{{< image src="images/borg-backup-logo.png" alt="BorgBackup" >}} The [documentation](https://borgbackup.readthedocs.io/en/stable/) is a nice starting point, beside that, you find plenty of useful tutorial online. diff --git a/content/posts/join-the-kde-ev/index.md b/content/posts/join-the-kde-ev/index.md index f01d919..c24ea2a 100644 --- a/content/posts/join-the-kde-ev/index.md +++ b/content/posts/join-the-kde-ev/index.md @@ -26,7 +26,7 @@ The e.V. shall stay a representation of the currently active KDE contributors/co Just take a look at the [2002 e.V. meeting](https://ev.kde.org/reports/2002/) group photo below: -{{< image src="/posts/join-the-kde-ev/images/2002_meeting.png" alt="2002 KDE e.V. meeting" >}} +{{< image src="images/2002_meeting.png" alt="2002 KDE e.V. meeting" >}} A few of this people are still active, some of them many of the current active KDE community members have never heard of. The group pictured above isn't that diverse either. @@ -36,7 +36,7 @@ I actually fished that picture out of my private data storage .P Let's take a look at the Akademy 2020 group photo below (CC BY 4.0, created by the Akademy team): -{{< image src="/posts/join-the-kde-ev/images/akademy2020_group_photo_1080.png" alt="Akademy 2020 group photo" >}} +{{< image src="images/akademy2020_group_photo_1080.png" alt="Akademy 2020 group photo" >}} This looks a lot more like the KDE community we all know and love. Therefore it would be fantastic if active people take care to join the e.V., too! diff --git a/content/posts/kate-and-icons/images/2024-kate-linux-wayland.png b/content/posts/kate-and-icons/images/2024-kate-linux-wayland.png new file mode 100644 index 0000000..65bd748 Binary files /dev/null and b/content/posts/kate-and-icons/images/2024-kate-linux-wayland.png differ diff --git a/content/posts/kate-and-icons/images/2024-kate-macos.png b/content/posts/kate-and-icons/images/2024-kate-macos.png new file mode 100644 index 0000000..b14f594 Binary files /dev/null and b/content/posts/kate-and-icons/images/2024-kate-macos.png differ diff --git a/content/posts/kate-and-icons/images/2024-kate-windows.png b/content/posts/kate-and-icons/images/2024-kate-windows.png new file mode 100644 index 0000000..1158481 Binary files /dev/null and b/content/posts/kate-and-icons/images/2024-kate-windows.png differ diff --git a/content/posts/kate-and-icons/index.md b/content/posts/kate-and-icons/index.md index 213795c..a75b54d 100644 --- a/content/posts/kate-and-icons/index.md +++ b/content/posts/kate-and-icons/index.md @@ -12,23 +12,23 @@ author: "Christoph Cullmann" ### Linux & BSDs -{{< image src="/posts/kate-on-all-platforms-2024/images/2024-kate-linux-wayland.png" alt="Linux & BSDs" >}} +{{< image src="images/2024-kate-linux-wayland.png" alt="Linux & BSDs" >}} ### Windows -{{< image src="/posts/kate-on-all-platforms-2024/images/2024-kate-windows.png" alt="Windows" >}} +{{< image src="images/2024-kate-windows.png" alt="Windows" >}} ### macOS -{{< image src="/posts/kate-on-all-platforms-2024/images/2024-kate-macos.png" alt="macOS" >}} +{{< image src="images/2024-kate-macos.png" alt="macOS" >}} ## State on Fedora 40 Workstation & XFCE Spin... Screenshots taken from the [GNOME bugtracker](https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/288), copies to not stall their GitLab instance. -{{< image src="/posts/kate-and-icons/images/fedora-40-workstation.jpg" alt="Fedora 40 Workstation" >}} +{{< image src="images/fedora-40-workstation.jpg" alt="Fedora 40 Workstation" >}} -{{< image src="/posts/kate-and-icons/images/fedora-40-xfce.png" alt="Fedora 40 XFCE Spin" >}} +{{< image src="images/fedora-40-xfce.png" alt="Fedora 40 XFCE Spin" >}} I think that is rather unpleasant and for e.g. the left icon-only border just an unusable insult. diff --git a/content/posts/kate-history-kde-4-porting/index.md b/content/posts/kate-history-kde-4-porting/index.md index 38b0456..ed26b05 100644 --- a/content/posts/kate-history-kde-4-porting/index.md +++ b/content/posts/kate-history-kde-4-porting/index.md @@ -4,7 +4,7 @@ date: 2019-04-12T23:52:00+02:00 draft: false categories: [kde, kate, development] tags: [kde, kate] -url: /posts/kate-history-kde-4-porting/ +url: author: "Christoph Cullmann" --- @@ -16,19 +16,19 @@ The KDE 3 -> 4 transition was a large hassle. It did take weeks of work just to We first started with some trivial KTextEditor container (a mini KWrite) for the porting to get KTextEditor at all doing something. That started out with something that even had no menu or toolbars working: -{{< image src="/posts/kate-history-kde-4-porting/images/katetest-kde4-20050515-more.png" alt="no menu or toolbars working kde 4" >}} +{{< image src="images/katetest-kde4-20050515-more.png" alt="no menu or toolbars working kde 4" >}} This evolved after two days into a kind of working KWrite port (icons still randomly missing): -{{< image src="/posts/kate-history-kde-4-porting/images/katetest-kde4-20050517.png" alt="kwrite kde 4" >}} +{{< image src="images/katetest-kde4-20050517.png" alt="kwrite kde 4" >}} After the KTextEditor part did work "reasonable", we started with Kate: -{{< image src="/posts/kate-history-kde-4-porting/images/kate-kde4-20050519.png" alt="kate kde 4" >}} +{{< image src="images/kate-kde4-20050519.png" alt="kate kde 4" >}} And ended up with an initial ported prototype three days later: -{{< image src="/posts/kate-history-kde-4-porting/images/kate-kde4-20050522.png" alt="kate kde 4" >}} +{{< image src="images/kate-kde4-20050522.png" alt="kate kde 4" >}} And after that a long time of actual polishing for KDE 4.0 did start. Kate was actually one of the first ported applications during the KDE 3 -> 4 transition. @@ -36,6 +36,6 @@ The KDE 4 -> KF5 transition was much nicer, even thought the Frameworks split di And where did we end up with this ~14 years later? Actually, just here: -{{< image src="/posts/kate-history-kde-4-porting/images/kate-kf5-20190412.png" alt="kate kf5" >}} +{{< image src="images/kate-kf5-20190412.png" alt="kate kf5" >}} It is still recognizable the same application, thought I hope some progress is visible :=) diff --git a/content/posts/kate-lsp-client-continued/index.md b/content/posts/kate-lsp-client-continued/index.md index 863f937..7590b85 100644 --- a/content/posts/kate-lsp-client-continued/index.md +++ b/content/posts/kate-lsp-client-continued/index.md @@ -4,7 +4,7 @@ date: 2019-07-14T15:33:00+02:00 draft: false categories: [kde, kate, development] tags: [kde, kate] -url: /posts/kate-lsp-client-continued/ +url: author: "Christoph Cullmann" --- @@ -20,21 +20,21 @@ What is new? * Diagnostics support: A tab in the LSP client toolview will show the diagnistics, grouped by file with links to jump to the locations. Issues will be highlighted in the editor view, too. -{{< image src="/posts/kate-lsp-client-continued/images/kate-diagnostics.png" alt="Diagnostics support" >}} +{{< image src="images/kate-diagnostics.png" alt="Diagnostics support" >}} * Find references: Find all references for some variable/function in your complete program. They are listed like the diagnostics grouped per file in an extra tab. -{{< image src="/posts/kate-lsp-client-continued/images/kate-find-references.png" alt="Find references" >}} +{{< image src="images/kate-find-references.png" alt="Find references" >}} * Improved document highlight: Highlight all occurrences of a variable/... inside the current document. Beside highlighting the reads/writes/uses, you get a jump list like for the other stuff as tab, too. -{{< image src="/posts/kate-lsp-client-continued/images/kate-document-highlight.png" alt="Improved document highlight" >}} +{{< image src="images/kate-document-highlight.png" alt="Improved document highlight" >}} A feature I missed to show last time: * Hover support: Show more meta info about a code location, like the proper type, useful e.g. for [almost-always-auto](https://herbsutter.com/2013/08/12/gotw-94-solution-aaa-style-almost-always-auto/) C++ programming. -{{< image src="/posts/kate-lsp-client-continued/images/kate-hover.png" alt="Hover support" >}} +{{< image src="images/kate-hover.png" alt="Hover support" >}} We even got already two patches for the fresh plugin: diff --git a/content/posts/kate-lsp-client-restart/index.md b/content/posts/kate-lsp-client-restart/index.md index 374a384..199873d 100644 --- a/content/posts/kate-lsp-client-restart/index.md +++ b/content/posts/kate-lsp-client-restart/index.md @@ -4,7 +4,7 @@ date: 2019-07-07T15:13:00+02:00 draft: false categories: [kde, kate, development] tags: [kde, kate] -url: /posts/kate-lsp-client-restart/ +url: author: "Christoph Cullmann" --- @@ -29,15 +29,15 @@ What does work (tested with clangd and kate.git/work projects) at the moment: * Auto completion: you get the proper LSP server provided completion items -{{< image src="/posts/kate-lsp-client-restart/images/kate-auto-completion.png" alt="Auto completion" >}} +{{< image src="images/kate-auto-completion.png" alt="Auto completion" >}} * Outline view: Get an extra tool view with the symbols of your current view -{{< image src="/posts/kate-lsp-client-restart/images/kate-outline-view.png" alt="Outline view" >}} +{{< image src="images/kate-outline-view.png" alt="Outline view" >}} * Document highlight: highlight all occurrences of a variable/... inside the current view -{{< image src="/posts/kate-lsp-client-restart/images/kate-document-highlight.png" alt="Document highlight" >}} +{{< image src="images/kate-document-highlight.png" alt="Document highlight" >}} * Code navigation: jump to the definition/declaration diff --git a/content/posts/kate-lsp-status-july-21/index.md b/content/posts/kate-lsp-status-july-21/index.md index 7032477..4d9344e 100644 --- a/content/posts/kate-lsp-status-july-21/index.md +++ b/content/posts/kate-lsp-status-july-21/index.md @@ -28,7 +28,7 @@ The most thing are internal cleanups and minor improvements. Feature wise, the hover implementation works now more like in other editors or IDEs, you get some nice tool tip after some delay: -{{< image src="/posts/kate-lsp-status-july-21/images/kate-hover.png" alt="Hover" >}} +{{< image src="images/kate-hover.png" alt="Hover" >}} Never try to guess again what some *auto* means ;=) diff --git a/content/posts/kate-on-all-platforms-2024/index.md b/content/posts/kate-on-all-platforms-2024/index.md index 615d796..2af19d3 100644 --- a/content/posts/kate-on-all-platforms-2024/index.md +++ b/content/posts/kate-on-all-platforms-2024/index.md @@ -4,7 +4,7 @@ date: 2024-04-14T19:32:02+02:00 draft: false categories: [kde] tags: [kde] -url: /posts/kate-on-all-platforms-2024/ +url: author: "Christoph Cullmann" --- @@ -25,7 +25,7 @@ If that is not the case for your system, please help to upstream them. Below the current state of the master branch compiled on NixOS unstable with Wayland. -{{< image src="/posts/kate-on-all-platforms-2024/images/2024-kate-linux-wayland.png" alt="Unix like systems with X11 or Wayland" >}} +{{< image src="images/2024-kate-linux-wayland.png" alt="Unix like systems with X11 or Wayland" >}} How to compile Kate on your own on a Unix like system and start to help to develop it can be found out [here](https://kate-editor.org/build-it/). @@ -41,7 +41,7 @@ With reasonable effort you can develop Kate on Windows with [Craft](https://comm Below the current state of the master branch running on Windows 11 inside VirtualBox. -{{< image src="/posts/kate-on-all-platforms-2024/images/2024-kate-windows.png" alt="Windows" >}} +{{< image src="images/2024-kate-windows.png" alt="Windows" >}} If you like to try that, use the nighly installer linked on the [Kate website](https://kate-editor.org/get-it/). @@ -53,7 +53,7 @@ We have nighly build available for that and you can, like on Windows, develop Ka Below the current state of the master branch running native on my M2 ARM Mac Mini. -{{< image src="/posts/kate-on-all-platforms-2024/images/2024-kate-macos.png" alt="macOS" >}} +{{< image src="images/2024-kate-macos.png" alt="macOS" >}} Same as for Windows, if you like to try that, use the nighly installer for either ARM or Intel Macs linked on the [Kate website](https://kate-editor.org/get-it/). diff --git a/content/posts/kde-applications-and-icons/index.md b/content/posts/kde-applications-and-icons/index.md index 97210a8..e6e11b4 100644 --- a/content/posts/kde-applications-and-icons/index.md +++ b/content/posts/kde-applications-and-icons/index.md @@ -4,7 +4,7 @@ date: 2024-05-11T20:30:01+02:00 draft: false categories: [kde] tags: [kde] -url: /posts/kde-applications-and-icons/ +url: author: "Christoph Cullmann" --- @@ -41,7 +41,7 @@ The KDE project did their job, at least for Kate I never did have any issues wit Below a screenshot of Kate 24.02 running on Plasma 6. All icons are there, they are properly re-colored for the dark theme, too, including not just the used Breeze icons but for example the small Git icons in the left sidebar that Kate has bundled. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-linux-wayland.png" alt="KDE Plasma on Linux/BSD with Wayland/X11" >}} +{{< image src="images/2024-kate-linux-wayland.png" alt="KDE Plasma on Linux/BSD with Wayland/X11" >}} This is the vanilla state each user will get if Kate is installed on Plasma (and the dark theme is used). There are no patches done during building to achieve that nor is there any extra user configuration necessary. @@ -52,7 +52,7 @@ If you run Kate on Windows, the icon situation is good, too, if you use our Wind See below what the current nightly of Kate looks like in some Windows 11 VM (I just started it from the unpacked ZIP, no setup needed). -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-windows.png" alt="Microsoft Windows" >}} +{{< image src="images/2024-kate-windows.png" alt="Microsoft Windows" >}} In the Craft build descriptions we do some patches to ensure the Breeze icons are bundled as library and the application links with that. In addition we ensure with some more patching that our own icon engine is used to allow for the proper recoloring. @@ -65,7 +65,7 @@ The situation on macOS is the same as on Windows. If you go with a Craft build of Kate, you will end up with something like below. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-macos.png" alt="Apple's macOS" >}} +{{< image src="images/2024-kate-macos.png" alt="Apple's macOS" >}} All icons are there and even application provided icons like our Git one are properly recolored. @@ -75,7 +75,7 @@ Without the Craft patches Kate has more or less no icons like on Windows. After covering Plasma and the two large closed-source desktop operating systems, as a small excursion, look how Kate (the KF5 based version) looks if installed on [Haiku](https://www.haiku-os.org/) with the package they provide. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-haiku.png" alt="Haiku" >}} +{{< image src="images/2024-kate-haiku.png" alt="Haiku" >}} Kate looks ok, system icons intermixed with Breeze as fallback icons. @@ -85,18 +85,18 @@ For testing this, I installed the latest Fedora Workstation in a VM. I have done no user configuration beside what the installer and initial setup wizard asked and then just installed the Kate package. The shell was even helpful to ask to do that after you just tried to start the not installed Kate. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-fedora-gnome.png" alt="Kate on GNOME" >}} +{{< image src="images/2024-kate-fedora-gnome.png" alt="Kate on GNOME" >}} Most icons not there, not that nice. For details about that read [this post](/posts/kate-and-icons/), we don't need to re-iterate this again. If you think: that is just Kate, let us just try Okular. -{{< image src="/posts/kde-applications-and-icons/images/2024-okular-fedora-gnome.png" alt="Okular on GNOME" >}} +{{< image src="images/2024-okular-fedora-gnome.png" alt="Okular on GNOME" >}} One thing that can be at least solved easily is that the icons are gone, we just install the Breeze icon set as package. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-and-okular-with-breeze-fedora-gnome.png" alt="Kate and Okular with Breeze on GNOME" >}} +{{< image src="images/2024-kate-and-okular-with-breeze-fedora-gnome.png" alt="Kate and Okular with Breeze on GNOME" >}} Looks ok, system icons intermixed with Breeze as fallback icons just like on Haiku. Not stylish but usable. @@ -107,7 +107,7 @@ I was unable to trigger Kate or Okular to adjust to the dark mode GNOME provides Kate and Dolphin 24.02 on MATE with dark mode on NixOS, normal system packages, Breeze icons is installed. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-and-dolphin-mate.png" alt="MATE" >}} +{{< image src="images/2024-kate-and-dolphin-mate.png" alt="MATE" >}} System icons intermixed with Breeze as fallback icons, looks not that nice. Breeze icons not readable, as recoloring is not working. @@ -116,7 +116,7 @@ Breeze icons not readable, as recoloring is not working. Kate and Dolphin 24.02 on Xfce with dark mode on NixOS, normal system packages, Breeze icons is installed. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-and-dolphin-xfce.png" alt="Xfce" >}} +{{< image src="images/2024-kate-and-dolphin-xfce.png" alt="Xfce" >}} Same mix and unreadable state as on MATE. @@ -124,7 +124,7 @@ Same mix and unreadable state as on MATE. Kate 24.02 on Enlightenment with dark mode on NixOS, normal system packages, Breeze icons is installed. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-enlightenment.png" alt="Enlightenment" >}} +{{< image src="images/2024-kate-enlightenment.png" alt="Enlightenment" >}} Just unreadable icons, beside out own Git icon and the few colored ones. @@ -172,7 +172,7 @@ All is not perfect, we will need to get some Qt API to fully do that, but the cu Here a comparison with the state as we have it now in our released software compared to with the state in the current master branch on an Cinnamon desktop. -{{< image src="/posts/kde-applications-and-icons/images/2024-kate-fixed-cinnamon.png" alt="Cinnamon" >}} +{{< image src="images/2024-kate-fixed-cinnamon.png" alt="Cinnamon" >}} The left side is the current Kate 24.02, the right side the current master build of Kate with master Frameworks. diff --git a/content/posts/kde-applications-on-windows/index.md b/content/posts/kde-applications-on-windows/index.md index e761d94..e6b54b9 100644 --- a/content/posts/kde-applications-on-windows/index.md +++ b/content/posts/kde-applications-on-windows/index.md @@ -4,7 +4,7 @@ date: 2019-09-21T23:13:00+02:00 draft: false categories: [kde, development] tags: [kde] -url: /posts/kde-applications-on-windows/ +url: author: "Christoph Cullmann" --- @@ -53,15 +53,15 @@ Direct links to the store entries can be found below (the screenshots are in Ger * [Okular - more than a reader](https://www.microsoft.com/store/apps/9N41MSQ1WNM8) -{{< image src="/posts/kde-applications-on-windows/images/okular-on-windows.png" alt="Okular - more than a reader" >}} +{{< image src="images/okular-on-windows.png" alt="Okular - more than a reader" >}} * [Kate - Advanced Text Editor](https://www.microsoft.com/store/apps/9NWMW7BB59HW) -{{< image src="/posts/kde-applications-on-windows/images/kate-on-windows.png" alt="Kate - Advanced Text Editor" >}} +{{< image src="images/kate-on-windows.png" alt="Kate - Advanced Text Editor" >}} * [KStars - Astronomy Software](https://www.microsoft.com/store/apps/9PPRZ2QHLXTG) -{{< image src="/posts/kde-applications-on-windows/images/kstars-on-windows.png" alt="KStars - Astronomy Software" >}} +{{< image src="images/kstars-on-windows.png" alt="KStars - Astronomy Software" >}} #### Help Wanted! diff --git a/content/posts/kde-qt-highdpi-scaling/index.md b/content/posts/kde-qt-highdpi-scaling/index.md index 8267db5..55e3a4e 100644 --- a/content/posts/kde-qt-highdpi-scaling/index.md +++ b/content/posts/kde-qt-highdpi-scaling/index.md @@ -4,7 +4,7 @@ date: 2019-10-03T18:40:00+02:00 draft: false categories: [kde, qt, development] tags: [kde, qt] -url: /posts/kde-qt-highdpi-scaling/ +url: author: "Christoph Cullmann" --- @@ -53,7 +53,7 @@ I used PNG to avoid that some JPEG artifacts make the real rendering artifacts u Let's show the current state with [Kate](https://kate-editor.org) & [Konsole](https://konsole.kde.org), here how Kate 19.08.1 looks if you start it on the second screen with default configuration with COPYING.LIB of ktexteditor.git as file: -{{< image src="/posts/kde-qt-highdpi-scaling/images/kate-19.08.1-hidpi-second-screen.png" alt="Experiments on Kate & Konsole" >}} +{{< image src="images/kate-19.08.1-hidpi-second-screen.png" alt="Experiments on Kate & Konsole" >}} This looks kind of strange. What you see is actually no split screen, even that is a pure rendering artifacts, actually, the whole Kate windows is more or less one artifacts. @@ -67,7 +67,7 @@ This is now fixed and backported to the 19.08 branch. This means, with 19.08.2, you will have the following experience: -{{< image src="/posts/kde-qt-highdpi-scaling/images/kate-19.08.2-hidpi-second-screen.png" alt="Experiments on Kate & Konsole with 19.08.2" >}} +{{< image src="images/kate-19.08.2-hidpi-second-screen.png" alt="Experiments on Kate & Konsole with 19.08.2" >}} This somehow looks more like an actual working application. @@ -76,7 +76,7 @@ For people not able to update, a workaround is to disable both project and termi Is now all fine with Kate? Unfortunately not, lets change my font size a bit and select things: -{{< image src="/posts/kde-qt-highdpi-scaling/images/kate-19.08.2-hidpi-selection.png" alt="Experiments on Kate & Konsole with 19.08.2 with selection" >}} +{{< image src="images/kate-19.08.2-hidpi-selection.png" alt="Experiments on Kate & Konsole with 19.08.2 with selection" >}} I selected both in the text view (KTextEditor) and in the KonsolePart to show the issue is not just a plain "we are too dumb to render things" in KTextEditor. You get equal artifacts with most of our software :( @@ -123,7 +123,7 @@ This leads to this current state of the rendering in the master branch. I did select + deselect a bit text in the terminal to trigger the paintEvent related clipping failure, you can see a few small one pixel high selection leftovers below the selection area. You need to play a bit with the scaling factor and font size, too, to trigger the effects, as like all rounding errors, you need specific values to trigger them. -{{< image src="/posts/kde-qt-highdpi-scaling/images/kate-master-hidpi.png" alt="Experiments on Kate master" >}} +{{< image src="images/kate-master-hidpi.png" alt="Experiments on Kate master" >}} I hope the Qt bugs linked above can be fixed in the near future, as I doubt we can add workaround to all the applications affected (nor do we want to) and the clipping issue of the paintEvent, if it really is the reason for the last remaining Konsole artifacts, seems not to be really fixable at all in the application code, beside going away from fine grained repaints. diff --git a/content/posts/keyboard-fun/index.md b/content/posts/keyboard-fun/index.md index ca980fb..caffc9c 100644 --- a/content/posts/keyboard-fun/index.md +++ b/content/posts/keyboard-fun/index.md @@ -4,7 +4,7 @@ date: 2021-12-12T14:10:00+03:00 draft: false categories: [keyboard] tags: [keyboard] -url: /posts/keyboard-fun/ +url: author: "Christoph Cullmann" --- @@ -37,13 +37,13 @@ I did take some look at the internals of the keyboard to see if some more dampen See the disassembly and later playing around with stuff and tape below. -{{< image src="/posts/keyboard-fun/images/varmilo-moonlight-disass-1.jpg" alt="Removing the ping?" >}} +{{< image src="images/varmilo-moonlight-disass-1.jpg" alt="Removing the ping?" >}} -{{< image src="/posts/keyboard-fun/images/varmilo-moonlight-disass-2.jpg" alt="Removing the ping?" >}} +{{< image src="images/varmilo-moonlight-disass-2.jpg" alt="Removing the ping?" >}} -{{< image src="/posts/keyboard-fun/images/varmilo-moonlight-disass-3.jpg" alt="Removing the ping?" >}} +{{< image src="images/varmilo-moonlight-disass-3.jpg" alt="Removing the ping?" >}} -{{< image src="/posts/keyboard-fun/images/varmilo-moonlight-disass-4.jpg" alt="Removing the ping?" >}} +{{< image src="images/varmilo-moonlight-disass-4.jpg" alt="Removing the ping?" >}} Short answer: it didn't help. You can even stuff the lower parts totally with "anything", given you screw all things together later it will still ping. Even alone the upper plate does ping if you tick it without any extra parts. @@ -62,17 +62,17 @@ Solution? Create one out of both. Given the red switches and the typing on the Xtrfy board was nice, why not just use the Varmilo keycaps for it? -{{< image src="/posts/keyboard-fun/images/xtrfy-varmilo-moonlight-transfer-1.jpg" alt="The solution?" >}} +{{< image src="images/xtrfy-varmilo-moonlight-transfer-1.jpg" alt="The solution?" >}} -{{< image src="/posts/keyboard-fun/images/xtrfy-varmilo-moonlight-transfer-2.jpg" alt="The solution?" >}} +{{< image src="images/xtrfy-varmilo-moonlight-transfer-2.jpg" alt="The solution?" >}} -{{< image src="/posts/keyboard-fun/images/xtrfy-varmilo-moonlight-transfer-3.jpg" alt="The solution?" >}} +{{< image src="images/xtrfy-varmilo-moonlight-transfer-3.jpg" alt="The solution?" >}} Varmilo was nice enough to include a keycaps puller anyways, already used for the total disassembly above. ## End result -{{< image src="/posts/keyboard-fun/images/xtrfy-varmilo-moonlight.jpg" alt="End result" >}} +{{< image src="images/xtrfy-varmilo-moonlight.jpg" alt="End result" >}} I think the final "product" looks nice. The RGB back-lighting still works, though the new keycaps are not shine-through. diff --git a/content/posts/keyboards-and-open-source/index.md b/content/posts/keyboards-and-open-source/index.md index cb8386c..1aa7d56 100644 --- a/content/posts/keyboards-and-open-source/index.md +++ b/content/posts/keyboards-and-open-source/index.md @@ -4,7 +4,7 @@ date: 2022-01-23T21:25:00+03:00 draft: false categories: [keyboard] tags: [keyboard] -url: /posts/keyboards-and-open-source/ +url: author: "Christoph Cullmann" --- @@ -40,7 +40,7 @@ Here [VIA](https://caniusevia.com/) comes into the picture. For sure, it is an Electron based monster, but it provides a cross-platform UI for QMK based keyboards that allow on the fly configuration of at least the common things, like keymaps. And it provides trivial things like testing all your keys, which is not that unneeded, given I was too dumb to properly install all my hot-swap switches ;) -{{< image src="/posts/keyboards-and-open-source/images/keyboard-via.png" alt="VIA UI" >}} +{{< image src="images/keyboard-via.png" alt="VIA UI" >}} ## Actual Keyboard? @@ -71,14 +71,14 @@ At work I now have some [SA profile](https://www.keycaps.info/) set from Signatu Funny enough, shipping from US did take 4 weeks, even with air express, USPS seems to be not the fasted variant of travel. If others play with the idea to buy there, I must confess the quality is really good, but they are expensive, if you don't require exotic layouts like German, I would rather go with some cheaper sets, for US ANSI even the cheapest I tried out were ok, without obvious faults. -{{< image src="/posts/keyboards-and-open-source/images/keyboard-q1-work.jpg" alt="Keychron Q1 Ice Cap Keycaps" >}} +{{< image src="images/keyboard-q1-work.jpg" alt="Keychron Q1 Ice Cap Keycaps" >}} If you look a bit more around on the picture you will see I have still my good old Nokia rubber ducky, a sole survivor from the time Nokia owned Qt :P And no, I don't use a Mac, that is just one we use for our compile farm. At home I went with some [MT3 profile](https://matt3o.com/about-mt3-profile-and-devtty-set/) set without any legends, that is really cheap and funny enough did take only 4 days from US to Germany with standard UPS. -{{< image src="/posts/keyboards-and-open-source/images/keyboard-q1-home.jpg" alt="Keychron Q1 MT3 /dev/tty Keycaps" >}} +{{< image src="images/keyboard-q1-home.jpg" alt="Keychron Q1 MT3 /dev/tty Keycaps" >}} :=) And no, no second Nokia ducky at home. diff --git a/content/posts/over-20-years-of-bug-squashing/index.md b/content/posts/over-20-years-of-bug-squashing/index.md index 0b440d6..8bc25f5 100644 --- a/content/posts/over-20-years-of-bug-squashing/index.md +++ b/content/posts/over-20-years-of-bug-squashing/index.md @@ -14,7 +14,7 @@ This means I look at user bug reports for over 20 years now. The statistics tell me our team got more than 9000 bugs since around 2001 (just for Kate, this excludes the libraries like KTextEditor that we maintain, too). -{{< image src="/posts/over-20-years-of-bug-squashing/images/kate-bug-statistics.png" alt="Kate Bug Statistics" >}} +{{< image src="images/kate-bug-statistics.png" alt="Kate Bug Statistics" >}} That is a bit more than one bug per day for over two decades. diff --git a/content/posts/planck-and-qmk/index.md b/content/posts/planck-and-qmk/index.md index 379e7b6..1a04f5c 100644 --- a/content/posts/planck-and-qmk/index.md +++ b/content/posts/planck-and-qmk/index.md @@ -4,7 +4,7 @@ date: 2022-10-08T18:35:00+03:00 draft: false categories: [keyboard] tags: [keyboard] -url: /posts/planck-and-qmk/ +url: author: "Christoph Cullmann" --- @@ -27,7 +27,7 @@ Unlike for my tries with the Q1, this time I just went the plain QMK route, with The Planck board offers a nice platform for experiments, given the plain grid layer that allows really to freely shuffle all your keys and experiment with extreme layouts. -{{< image src="/posts/planck-and-qmk/images/planck-building.webp" alt="Building the Planck keyboard" >}} +{{< image src="images/planck-building.webp" alt="Building the Planck keyboard" >}} ## Install QMK on NixOS @@ -87,7 +87,7 @@ Below the state of a finalized Planck board with some more or less standard firs It even plays a nice startup sound on powering up. -{{< image src="/posts/planck-and-qmk/images/planck-final.webp" alt="Finalized Planck keyboard" >}} +{{< image src="images/planck-final.webp" alt="Finalized Planck keyboard" >}} My current keymap can be found [here](https://git.babylon2k.com/cullmann/qmk). diff --git a/content/posts/plasma-kate-wayland-2021/index.md b/content/posts/plasma-kate-wayland-2021/index.md index f96aa0d..8407ea8 100644 --- a/content/posts/plasma-kate-wayland-2021/index.md +++ b/content/posts/plasma-kate-wayland-2021/index.md @@ -57,7 +57,7 @@ Let's continue to improve that in the next years even more! Even [Wine](https://www.winehq.org/) based gaming in parallel to coding is possible, awesome! -{{< image src="/posts/plasma-kate-wayland-2021/images/plasma-kate-diablo-wayland.webp" alt="My current KDE Plasma on Wayland session ;=)" >}} +{{< image src="images/plasma-kate-diablo-wayland.webp" alt="My current KDE Plasma on Wayland session ;=)" >}} ## Try it out! diff --git a/layouts/shortcodes/image.html b/layouts/shortcodes/image.html index 182ba27..96cb3dd 100644 --- a/layouts/shortcodes/image.html +++ b/layouts/shortcodes/image.html @@ -1,5 +1,7 @@
- - {{ .Get +{{ $original := .Page.Resources.GetMatch (.Get "src") }} +{{ $preview := $original.Resize "660x" }} + + {{ .Get
diff --git a/layouts/shortcodes/video.html b/layouts/shortcodes/video.html index cca83be..5f805e9 100644 --- a/layouts/shortcodes/video.html +++ b/layouts/shortcodes/video.html @@ -1,5 +1,5 @@
-