From 3262dd2648ac3ec64ca2405ec94fe6a77fa9bd7d Mon Sep 17 00:00:00 2001 From: Matt Kosarek Date: Mon, 29 Dec 2025 13:03:38 -0500 Subject: Cleanup a whole lot of things + introduce a new blog post --- posts/dec_29_2025.html | 122 ++++++++++++++++++++++++++++++++++ posts/feed.xml | 10 ++- posts/hello.html | 74 ++++++++++----------- posts/jul_28_2025.html | 6 +- posts/june_08_2025.html | 6 +- posts/may_06_2025.html | 6 +- posts/post.css | 58 ----------------- posts/post.js | 38 ++++++----- posts/sitemap.css | 169 ++++++++++++++++++++++++++++++++++++++++++++++++ posts/sitemap.html | 58 ++++++++++++++--- 10 files changed, 413 insertions(+), 134 deletions(-) create mode 100644 posts/dec_29_2025.html create mode 100644 posts/sitemap.css (limited to 'posts') diff --git a/posts/dec_29_2025.html b/posts/dec_29_2025.html new file mode 100644 index 0000000..9e4ee07 --- /dev/null +++ b/posts/dec_29_2025.html @@ -0,0 +1,122 @@ + + + + + + +Update December 29, 2025 + + + + + + + + +
+ UP + HOME +
+ +
+

Update December 29, 2025

+ Last modified: 2025-12-29 Mon 10:27 + RSS Feed +
+
+
+
+

What have I been up to?

+
+

+2025 has been one busy year for me! I feel as though I've been working on a dozen things at once and have spent much of my working (and personal) days productively. Miracle finally feels like it's getting somewhere fast, the Flutter multi-window work is landing at a solid pace, and Mir is feeling like a truly solid option for Wayland compositor development. I will refrain from speaking too much on the Flutter and Mir work in this post, as those are best left in the hands of Canonical. +

+
+
+
+

Miracle Update

+
+

+Miracle has come a long way this past year. I now feel entirely confident using it as my daily driver, minus a few hiccups that I encounter in-between releases. A lot of great things are cooking for 2026 too, +

+ +

+One of the major upcoming features in Miracle is a plugin system. Having a plugin system in Miracle will empower 3rd party authors to extend the compositor in ways that I haven't currently imagined while also providing me with the flexibility to iterate quickly on designs. Many compositors already have plugin systems. For example, GNOME does this via JavaScript and Hyprland does this by dynamically loading shared libraries at runtime (note: this is my understanding as of writing this). Both of these solutions are reasonable, but they come with a few downsides. +

+ +

+The "true" scripting language solution comes with the overhead of shipping a complicated interpreter inside of the compositor. In addition to this, plugin developers are forced to use a particular language, perhaps one that they are unfamiliar with. While you get increased programming flexibility from using a scripting language, you have to balance this with the introduced complexity of that language. +

+ +

+The shared library approach also has its downsides. While dynamically loading a shared library at runtime is lightweight, it prevents users of the compositor from safely running plugins unless they first trust the plugin author. The shared library will be running inside of the same process as your very priveleged compositor. This increases the attack surface to an extent that I would feel uncomfortable shipping to users. +

+ +

+For these reasons, I decided that Miracle plugins will be written in WebAssembly with the help of WasmEdge. The benefits of this approach are: +

+ +
    +
  1. WebAssembly runs in a lightweight bytecode engine
    2. +
  2. Many languages can compile down to WebAssembly (Rust will have first-class support to start)
    3. +
  3. WebAssembly plugins will only be able to access APIs that we provide (reducing the requirement of "trusting" the plugin author)
    4. +
+ +

+The WebAssembly modules will implement certain functions by signature. Miracle will search for a particular signature in the module. If that signature is found, Miracle will delegate the function call defined by that signature to the WebAssembly module instead of Miracle's internal implementation. In this way, the WASM plugin will only have the data that it needs to perform an action. It is perfectly isolated from the rest of the process while also running quickly in the bytecode engine. Here is an example of an animation plugin that will linearlly fade in a window: +

+ +
+
#[unsafe(no_mangle)]
+pub extern "C" fn animate(
+    data: MiracleAnimationFrameData,
+) -> MiracleAnimationFrameResult {
+
+    let progress = data.runtime_seconds / data.duration_seconds;
+    let opacity = data.opacity_start + (data.opacity_end - data.opacity_start) * progress;
+    MiracleAnimationFrameResult {
+        completed: 0,
+        has_area: 1,
+        area: [data.destination[0], data.destination[1], data.destination[2], data.destination[3]],
+        has_transform: 0,
+        transform: [0.0; 16],
+        has_opacity: 1,
+        opacity,
+    }
+} 
+
+
+ +

+While this is still in a prototype phase, the types defined here will be provided by a Rust crate in the future. The system should be very easy to use from Rust. +

+ +

+In parallel with this work, I have been working on improving the shell authoring experience in Miracle. The beginning of this has been the initial implementation of a background on floating containers, but work is proceeding to things like built-in context menus, workspace overview modes, and much more. The idea is to have simple, built-in versions for many shell components while allowing users to provide their own custom clients for each shell element. To this end, I have been working on miracle.dart, which is a Dart API that should enable users to easily interact with Miracle in Flutter and provide Flutter apps as shell elements. This API is still in early stages, however. +

+ +

+At the same time, I have been working on improving the floating window management in Miracle. Miracle should be a competent floating window manager for those who need it. +

+ +

+v0.9.0 of Miracle will probably be a long time in the making. My estimate is that early spring will see it released. However, it should be the penultimate release before I am ready to make v1.0.0 the first, official stable release. And who knows - maybe we'll even have a shell to go along with it! +

+
+
+
+

Conclusion

+
+

+2025 has been a whirlwind of a year, and I'm sure that 2026 won't slow down at all for me. A lot of the long term projects that I've been working on are finally coming together, and I feel as though I am on the cusp of making software that I'm truly proud of. On top of that, I am engaged! What a time to be alive :) I hope you all have a lovely New Year with your friends, family, cats, dogs, and everything else. +

+ +

+Keep on making great stuff ✌️ +

+
+
+
+ + diff --git a/posts/feed.xml b/posts/feed.xml index a5769fa..affbb37 100644 --- a/posts/feed.xml +++ b/posts/feed.xml @@ -5,7 +5,15 @@ https://matthewkosarek.xyz/ The RSS feed for Matthew Kosarek's Blog en-us - Mon, 28 July 2025 17:30:00 -0400 + Mon, 29 December 2025 13:03:00 -0400 + + + Update December 29, 2025 + https://matthewkosarek.xyz/posts/dec_29_2025.html + https://matthewkosarek.xyz/posts/dec_29_2025.html + Mon, 29 December 2025 10:27:00 -0400 + Update December 29, 2025 + Update July 28, 2025 diff --git a/posts/hello.html b/posts/hello.html index 0017e02..992e0c7 100644 --- a/posts/hello.html +++ b/posts/hello.html @@ -26,9 +26,9 @@
-
-

TLDR

-
+
+

TLDR

+
-
-

Introduction

-
+
+

Introduction

+

I've recently fallen in love with org-mode, specifically when I use it with org-roam. I find the whole workflow of creating, tagging, and - later on - searching for information on my computer to be very elegant. On top of that, now that I have the time, I want to begin writing blog posts to better work out my thoughts. With both of these things in mind, I am again turning to the universal tool for human prospering: org-mode. This time, I want to see how it can help me turn a simple org file into a blog post on my website. My requirements are:

@@ -67,9 +67,9 @@ And that's pretty much it for now. Without further ado, let's jump into getting

-
-

Basic HTML File

-
+
+

Basic HTML File

+

As a pilot, we are going to use this org file that I am currently writing (hello.org) as our guinea pig. The goal is to have this org file be our very first blog post.

@@ -109,9 +109,9 @@ We then do a chmod +x publish.sh to make it an executable and run i

-
-

Disabling features that we don't want

-
+
+

Disabling features that we don't want

+

The next thing will be to remove some of the generated items that I didn't ask for, namely the table of contents, author, section numbers, creation time stamp, and the validation link.

@@ -140,9 +140,9 @@ The next thing will be to remove some of the generated items that I didn't ask f
-
-

Styling & Code Highlighting

-
+
+

Styling & Code Highlighting

+

Next thing on our list is custom styling. This can be achieved by first installing the htmlize package from melpa / elpa. The EmacsWiki describes this as "a package for exporting the contents of an Emacs buffer to HTML while respecting display properties such as colors, fonts, underlining, invisibility, etc" (reference). If used "out-of-the-box", the buffer will be exported to HTML with all of the styles inlined (e.g. if you underline something in your org file, you will generate a <span style="text-decoration: underline">...</span>). However, we are more interested in styling everything by ourselves: we don't want htmlize making assumptions about what underlining means to us! Luckily, htmlize gives us the option to export with class names instead of inline styles so that we can specify each style for ourselves.

@@ -312,9 +312,9 @@ If we run the publish again, we can see that we have full styling on our code sn

-
-

Images

-
+
+

Images

+

Our first two criteria have been met! Next on the list is solving images. As an example, let's use this squirrel image that I found online with an open source license. The ideal situation would be:

@@ -359,16 +359,16 @@ So what's the fix here? Well, we have two options, but I am going to go with the That's all there is to it! There are simpler ways as well, but that should do it:

-
+

squirrel.jpg

Figure 1: A Cute Squirrel

-
-

Creation Date

-
+
+

Creation Date

+

Let's add the creation date below the title next. To start, we will modify the publish command to remove the title (:with-title nil) and, in its place, show a preamble bit of HTML that contains a formatted div with the title and the "last modified" span.z

@@ -427,9 +427,9 @@ Note that the downside of this is that the created date will change whenever you

-
-

Generating the Directory

-
+
+

Generating the Directory

+

For every org file in my _posts folder, I would like to create a link to the generated HTML file at the /posts.html page of my website. You can think of this as the "directory" of all posts. My criteria is:

@@ -489,9 +489,9 @@ If you open the sitemap.html file in your browser, you will see a b From here, you may customize it however you like. The following are my customizations.

-
-

Sitemap Title

-
+
+

Sitemap Title

+

I changed the title to "Matthew's Blog Posts".

@@ -513,9 +513,9 @@ I changed the title to "Matthew's Blog Posts".
-
-

Format blog entries in the list

-
+
+

Format blog entries in the list

+

I like to include the creation date on the blog posts. To do this, we can use org-publish-find-property to find the date property of the org file. Afterward, we can format a string that includes our formatted timestamp and the org-publish-sitemap-default-entry, which is just a link with the title of the post.

@@ -536,9 +536,9 @@ I like to include the creation date on the blog posts. To do this, we can use
-
-

Tags & Filtering

-
+
+

Tags & Filtering

+

I use Org-roam for all of my note-taking and, in the next blog post, I plan to demonstrate how I will hook up my Org-roam note-taking workflow to my blogging. In the meantime, just know that we can add tags to the top of our org files like this:

@@ -758,9 +758,9 @@ Finally, let's append the following to posts/posts.css so that our
-
-

Conclusion

-
+
+

Conclusion

+

There are many more customizations that I plan to do on this system in the future, but I plan to leave this for now so that I can actually get to some blogging. I will proofread and fix my mistakes as time goes on, but this should be a good jumping off point for anyone interested in using org for their own blogging system.

diff --git a/posts/jul_28_2025.html b/posts/jul_28_2025.html index 41fdbf5..304d202 100644 --- a/posts/jul_28_2025.html +++ b/posts/jul_28_2025.html @@ -26,9 +26,9 @@
-
-

What have I been up to?

-
+
+

What have I been up to?

+

Whoops! I missed this month's update by a long shot, but I still want to get it out there before the end of the month.

diff --git a/posts/june_08_2025.html b/posts/june_08_2025.html index f73ac59..4a69b4c 100644 --- a/posts/june_08_2025.html +++ b/posts/june_08_2025.html @@ -26,9 +26,9 @@
-
-

What have I been up to?

-
+
+

What have I been up to?

+

Another month has gone by, so I guess it's time to see what I've been up to.

diff --git a/posts/may_06_2025.html b/posts/may_06_2025.html index 43d276b..6e4665e 100644 --- a/posts/may_06_2025.html +++ b/posts/may_06_2025.html @@ -26,9 +26,9 @@
-
-

What have I been up to?

-
+
+

What have I been up to?

+

I've been meaning to do these little blog-post type updates for a while, and I figured now is as good a time as any. So let's start :)

diff --git a/posts/post.css b/posts/post.css index decceaa..1867311 100644 --- a/posts/post.css +++ b/posts/post.css @@ -68,61 +68,3 @@ pre span.org-css-property {color:#00AA00;} display: flex; column-gap: 8px; } - - -/* Sitemap-specific items */ -.sitemap_tag { - display: none; -} - -#tag-filter-container { - display: flex; - flex-direction: row; - column-gap: 8px; - margin-top: 1rem; -} - -.tag-filter-item { - display: flex; - flex-direction: row; - align-items: center; - padding: 0.25rem 0.5rem; - border: 1px solid black; - border-radius: 3px; - justify-content: center; - column-gap: 1rem; - background-color: #fffed8; -} - -.tag-filter-item button { - background: none; - border: none; - outline: none; - margin: 0; - padding: 0; - color: red; - font-size: 1.5rem; -} - -.tag-filter-item button:before { - content: '\00d7'; -} - -.tag-filter-item.disabled button:before { - content: '+'; -} - -.tag-filter-item.disabled { - background-color: #f2f2f2; - color: gray; - border-color: gray; -} - -.tag-filter-item.disabled button { - color: green; -} - -.tag-filter-item button:hover { - cursor: pointer; - opacity: 0.8; -} diff --git a/posts/post.js b/posts/post.js index 0b5a4e4..233739f 100644 --- a/posts/post.js +++ b/posts/post.js @@ -1,7 +1,7 @@ function main() { - // Gather the used set oof tags + // Gather the used set of tags const tagSet = new Set(); const postList = []; const tagContainers = document.getElementsByClassName('sitemap_tag'); @@ -12,8 +12,21 @@ function main() { continue; } - const tagList = pContainer.textContent.split(','); - tagList.forEach(tag => tagSet.add(tag)); + const tagText = pContainer.textContent.trim(); + const tagList = tagText.split(',').map(tag => tag.trim()); + + // Replace the text content with styled tag badges + pContainer.innerHTML = ''; + tagList.forEach(tag => { + if (tag) { + tagSet.add(tag); + const tagBadge = document.createElement('span'); + tagBadge.className = 'post-tag'; + tagBadge.textContent = tag; + pContainer.appendChild(tagBadge); + } + }); + postList.push({ container: container.parentElement, tagList: tagList, @@ -27,31 +40,18 @@ function main() { tagContainer.id = 'tag-filter-container'; contentContainer.before(tagContainer); - let numEnabled = tagSet.size; for (const tag of tagSet) { const tagElement = document.createElement('div'); tagElement.className = "tag-filter-item"; const tagElementLabel = document.createElement('span'); tagElementLabel.innerHTML = tag; - const tagElementButton = document.createElement('button'); - tagElement.append(tagElementLabel, tagElementButton); + tagElement.append(tagElementLabel); tagContainer.append(tagElement); - // Whenever a tag is clicked, execute the filtering behavior - tagElementButton.onclick = function() { - // Handle enable/disable - tagElement.remove(); - + tagElement.onclick = function() { if (tagElement.classList.contains('disabled')) { tagElement.classList.remove('disabled'); - if (numEnabled === 0) { - tagContainer.prepend(tagElement); - } - else { - tagContainer.children[numEnabled - 1].after(tagElement); - } - numEnabled++; // Filter postList.forEach(post => { @@ -66,8 +66,6 @@ function main() { } else { tagElement.classList.add('disabled'); - tagContainer.append(tagElement); - numEnabled--; // Filter postList.forEach(post => { diff --git a/posts/sitemap.css b/posts/sitemap.css new file mode 100644 index 0000000..b2de932 --- /dev/null +++ b/posts/sitemap.css @@ -0,0 +1,169 @@ +/* Sitemap-specific items */ +.sitemap_tag { + display: block; +} + +.sitemap_tag p { + margin: 0; + display: flex; + align-items: center; + flex-wrap: wrap; + gap: 0.5rem; + font-size: 0.85rem; +} + +.sitemap_tag p::before { + content: '🏷️'; + font-size: 1rem; +} + +/* Individual tag badges */ +.post-tag { + display: inline-block; + padding: 0.25rem 0.75rem; + background: linear-gradient(135deg, #e3f2fd 0%, #bbdefb 100%); + color: #1976d2; + border-radius: 12px; + font-size: 0.8rem; + font-weight: 500; + border: 1px solid #90caf9; +} + +.org-ul { + list-style: none; + padding: 0; +} + +.org-ul > li { + background: #f9f9f9; + border: 1px solid #e0e0e0; + border-radius: 8px; + padding: 1.5rem; + margin-bottom: 1rem; + transition: box-shadow 0.2s ease, transform 0.2s ease; + position: relative; + padding-bottom: 2.5rem; +} + +.org-ul > li:hover { + box-shadow: 0 4px 12px rgba(0, 0, 0, 0.1); + transform: translateY(-2px); +} + +.org-ul > li > p { + margin: 0; + font-size: 1.1rem; +} + +.org-ul > li > p > a { + color: #0066cc; + text-decoration: none; + font-weight: 600; + font-size: 1.25rem; +} + +.org-ul > li > p > a:hover { + text-decoration: underline; + color: #004499; +} + +.org-ul > li > p > a:after { + text-decoration: underline; + color: #004499; +} + +.org-article-title { + display: flex; + flex-direction: column; + gap: 0.5rem; + margin-bottom: 2rem; +} + +.org-article-title > span:last-child { + font-size: 0.95rem; +} + +#tag-filter-container { + display: flex; + flex-direction: row; + flex-wrap: wrap; + gap: 0.75rem; + margin-top: 1.5rem; + margin-bottom: 2rem; +} + +.tag-filter-item { + display: flex; + flex-direction: row; + align-items: center; + padding: 0.5rem 1rem; + border-radius: 4px; + justify-content: center; + column-gap: 0.75rem; + background: linear-gradient(135deg, #667eea 0%, darkviolet 100%); + color: white; + font-weight: 600; + font-size: 0.9rem; + letter-spacing: 0.3px; + box-shadow: 0 2px 6px rgba(102, 126, 234, 0.3); + transition: all 0.3s ease; +} + +.tag-filter-item:hover { + box-shadow: 0 4px 12px rgba(102, 126, 234, 0.4); + cursor: pointer; +} + +.tag-filter-item button:before { + content: '\00d7'; + line-height: 1; +} + +.tag-filter-item.disabled { + background: linear-gradient(135deg, #e0e0e0 0%, #c0c0c0 100%); + color: #666; + border-color: #999; + box-shadow: 0 1px 3px rgba(0, 0, 0, 0.1); + opacity: 0.7; +} + +.tag-filter-item.disabled:hover { + opacity: 1; + box-shadow: 0 2px 6px rgba(0, 0, 0, 0.15); +} + +.tag-filter-item.disabled button { + background: rgba(0, 0, 0, 0.1); + color: #666; +} + +.tag-filter-item.disabled button:before { + content: '+'; + font-size: 1.1rem; +} + +.post-date { + position: absolute; + bottom: 0.75rem; + right: 1rem; + font-size: 0.85rem; + color: #666; + font-style: italic; +} + +.sitemap_date { + position: absolute; + bottom: 0.75rem; + right: 1rem; + font-size: 0.85rem; + color: #666; + font-style: italic; +} + +.sitemap_date p { + margin: 0; +} + +.sitemap_date p::before { + content: 'created on '; +} diff --git a/posts/sitemap.html b/posts/sitemap.html index 669f389..00ac911 100644 --- a/posts/sitemap.html +++ b/posts/sitemap.html @@ -12,6 +12,7 @@ +
@@ -21,43 +22,82 @@

Matthew's Blog Posts

- Last modified: 2025-07-28 at 15:19 + Last modified: 2025-12-29 at 13:03 RSS Feed