<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>🐔哥真爱粉聚集地</title><description>晓游の博客</description><link>https://www.xychr.com/</link><language>zh</language><item><title>在 Android 设备上部署 PySide6 程序</title><link>https://www.xychr.com/posts/pyside6_on_android/pyside6_on_android/</link><guid isPermaLink="true">https://www.xychr.com/posts/pyside6_on_android/pyside6_on_android/</guid><description>本文记录了我在 Android 设备上部署 PySide6 程序的过程，涵盖了环境搭建、代码编写和运行结果等方面的内容。</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Tip: For the things that are not mentioned in this guide, you may find the answers in the &lt;a href=&quot;https://docs.astro.build/&quot;&gt;Astro Docs&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;Front-matter of Posts&lt;/h2&gt;
&lt;pre&gt;&lt;code&gt;---
title: My First Blog Post
published: 2020-02-02
description: This is the first post of my new Astro blog.
cover: ./cover.jpg
coverInContent: false
tags: []
category: Guides
comment: true
draft: false
---
&lt;/code&gt;&lt;/pre&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Attribute&lt;/th&gt;
&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;title&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The title of the post.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;published&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The date the post was published.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;pinned&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Whether this post is pinned to the top of the post list.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;description&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;A short description of the post. Displayed on index page.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cover&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The cover image path of the post. &amp;lt;br/&amp;gt;1. Start with &lt;code&gt;http://&lt;/code&gt; or &lt;code&gt;https://&lt;/code&gt;: For web image &amp;lt;br/&amp;gt;2. Start with &lt;code&gt;/&lt;/code&gt;: For image in &lt;code&gt;public&lt;/code&gt; dir &amp;lt;br/&amp;gt;3. With none of the prefixes: Relative to the markdown file&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;coverInContent&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Whether to show the cover image in the post content.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;tags&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The tags of the post.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;category&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The category of the post &amp;lt;br/&amp;gt;1. Single category: &lt;code&gt;category: Guides&lt;/code&gt; &amp;lt;br/&amp;gt;2. Multi-category: &lt;code&gt;category: [Guides, Getting Started]&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;licenseName&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The license name for the post content.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;author&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The author of the post.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;sourceLink&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The source link or reference for the post content.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;comment&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Whether to enable comment for this post. Default is &lt;code&gt;true&lt;/code&gt;.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;draft&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;If this post is still a draft, which won&apos;t be displayed.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2&gt;Where to Place the Post Files&lt;/h2&gt;
&lt;p&gt;Your post files should be placed in &lt;code&gt;src/content/posts/&lt;/code&gt; directory. You can also create sub-directories to better organize your posts and assets.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;src/content/posts/
├── post-1.md
└── post-2/
    ├── cover.jpg
    └── index.md
&lt;/code&gt;&lt;/pre&gt;
</content:encoded><category>Development / Python</category><category>Python</category><category>Qt</category><category>Android</category></item><item><title>Rust + Slint + ESP32-S3 快速上手初体验</title><link>https://www.xychr.com/posts/rust_slint_esp32s3/rust_slint_esp32s3/</link><guid isPermaLink="true">https://www.xychr.com/posts/rust_slint_esp32s3/rust_slint_esp32s3/</guid><description>本文记录了我在 ESP32-S3-BOX 上使用 Rust 和 Slint 进行开发的初体验，涵盖了环境搭建、代码编写和运行结果等方面的内容。</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;This guide covers advanced customization options and features available in the Twilight template, from global configurations to specialized Markdown extensions.&lt;/p&gt;
&lt;h2&gt;Global Configuration&lt;/h2&gt;
&lt;p&gt;The &lt;code&gt;twilight.config.yaml&lt;/code&gt; file is the heart of your blog&apos;s configuration. Here are some advanced settings you can tweak:&lt;/p&gt;
&lt;h3&gt;Site &amp;amp; Localization&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Language &amp;amp; Translation&lt;/strong&gt;: Enable client-side translation using &lt;code&gt;site.translate.enable&lt;/code&gt;. You can choose different services and configure auto-detection.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Custom Fonts&lt;/strong&gt;: Add your own fonts by providing a CSS link or file path under &lt;code&gt;site.font&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Visual Effects&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Theme Color&lt;/strong&gt;: Change the primary color of your blog by adjusting the &lt;code&gt;site.themeColor.hue&lt;/code&gt; (0-360).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Wallpaper Modes&lt;/strong&gt;: Choose between &lt;code&gt;banner&lt;/code&gt;, &lt;code&gt;fullscreen&lt;/code&gt;, or &lt;code&gt;none&lt;/code&gt;. You can also enable a &lt;code&gt;carousel&lt;/code&gt; for multiple wallpapers with the &lt;code&gt;kenBurns&lt;/code&gt; effect.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Waves Effect&lt;/strong&gt;: Toggle the animated water ripple effect on the banner using &lt;code&gt;site.wallpaper.banner.waves.enable&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Particle Effects&lt;/strong&gt;: Enable floating particles in the background with &lt;code&gt;particle.enable&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;UI&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Navbar Transparency&lt;/strong&gt;: Adjust &lt;code&gt;site.wallpaper.banner.navbar.transparentMode&lt;/code&gt; between &lt;code&gt;semi&lt;/code&gt;, &lt;code&gt;full&lt;/code&gt;, or &lt;code&gt;semifull&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sidebar Widgets&lt;/strong&gt;: Reorder or toggle sidebar components like &lt;code&gt;profile&lt;/code&gt;, &lt;code&gt;announcement&lt;/code&gt;, &lt;code&gt;categories&lt;/code&gt;, &lt;code&gt;tags&lt;/code&gt;, &lt;code&gt;toc&lt;/code&gt;, and &lt;code&gt;statistics&lt;/code&gt; in &lt;code&gt;sidebar.components&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Markdown Extensions&lt;/h2&gt;
&lt;h3&gt;GitHub Repository Cards&lt;/h3&gt;
&lt;p&gt;You can add dynamic cards that link to GitHub repositories, on page load, the repository information is pulled from the GitHub API.&lt;/p&gt;
&lt;p&gt;::github{repo=&quot;Spr-Aachen/Twilight&quot;}&lt;/p&gt;
&lt;p&gt;Create a GitHub repository card with the code &lt;code&gt;::github{repo=&quot;Spr-Aachen/Twilight&quot;}&lt;/code&gt;.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;::github{repo=&quot;Spr-Aachen/Twilight&quot;}
&lt;/code&gt;&lt;/pre&gt;
&lt;h3&gt;Music Cards&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Online
::music{meting=&quot;https://api.i-meto.com/meting/api?server=netease&amp;amp;type=song&amp;amp;id=1390882521&quot;}&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;::music{meting=&quot;https://api.i-meto.com/meting/api?server=netease&amp;amp;type=song&amp;amp;id=1390882521&quot;}
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;Local
::music{title=&quot;深海之息&quot; artist=&quot;Youzee Music&quot; cover=&quot;https://p1.music.126.net/PhKOqFtljgHDDpKYM2ADUA==/109951169858309716.jpg&quot; audio=&quot;assets/music/深海之息.m4a&quot; lrc=&quot;assets/music/深海之息.lrc&quot;}&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;::music{title=&quot;深海之息&quot; artist=&quot;Youzee Music&quot; cover=&quot;https://p1.music.126.net/PhKOqFtljgHDDpKYM2ADUA==/109951169858309716.jpg&quot; audio=&quot;assets/music/深海之息.m4a&quot; lrc=&quot;assets/music/深海之息.lrc&quot;}
&lt;/code&gt;&lt;/pre&gt;
&lt;h3&gt;Admonitions&lt;/h3&gt;
&lt;p&gt;Following types of admonitions are supported: &lt;code&gt;note&lt;/code&gt; &lt;code&gt;tip&lt;/code&gt; &lt;code&gt;important&lt;/code&gt; &lt;code&gt;warning&lt;/code&gt; &lt;code&gt;caution&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;:::note
Highlights information that users should take into account, even when skimming.
:::&lt;/p&gt;
&lt;p&gt;:::tip
Optional information to help a user be more successful.
:::&lt;/p&gt;
&lt;p&gt;:::important
Crucial information necessary for users to succeed.
:::&lt;/p&gt;
&lt;p&gt;:::warning
Critical content demanding immediate user attention due to potential risks.
:::&lt;/p&gt;
&lt;p&gt;:::caution
Negative potential consequences of an action.
:::&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Basic Syntax&lt;/strong&gt;&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;:::note
Highlights information that users should take into account, even when skimming.
:::

:::tip
Optional information to help a user be more successful.
:::
&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Custom Titles&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The title of the admonition can be customized.
:::note[MY CUSTOM TITLE]
This is a note with a custom title.
:::&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;:::note[MY CUSTOM TITLE]
This is a note with a custom title.
:::
&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;GitHub Syntax&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;[!TIP]
&lt;a href=&quot;https://github.com/orgs/community/discussions/16925&quot;&gt;The GitHub syntax&lt;/a&gt; is also supported.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;pre&gt;&lt;code&gt;&amp;gt; [!TIP]
&amp;gt; The GitHub syntax is also supported.
&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Spoiler&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;You can add spoilers to your text. The text also supports &lt;strong&gt;Markdown&lt;/strong&gt; syntax.&lt;/p&gt;
&lt;p&gt;The content :spoiler[is hidden &lt;strong&gt;ayyy&lt;/strong&gt;]!&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;The content :spoiler[is hidden **ayyy**]!
&lt;/code&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;p&gt;For more details, check the &lt;a href=&quot;https://docs.twilight.spr-aachen.com&quot;&gt;Documentation&lt;/a&gt;.&lt;/p&gt;
</content:encoded><category>Development / Rust</category><category>Rust</category><category>Slint</category><category>ESP32-S3</category></item></channel></rss>