<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Developers on Kaivalya Editor</title>
    <link>https://kaivalya.eu/projects/editor/en/developers/</link>
    <description>Recent content in Developers on Kaivalya Editor</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <atom:link href="https://kaivalya.eu/projects/editor/en/developers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting started</title>
      <link>https://kaivalya.eu/projects/editor/en/developers/getting-started/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kaivalya.eu/projects/editor/en/developers/getting-started/</guid>
      <description>What you need Kaivalya Editor is a Rust program with a GPU-accelerated UI, so it needs a Rust toolchain and the development files for Wayland, xkbcommon and Vulkan. On Ubuntu 24.04:&#xA;sudo apt install cmake clang mold vulkan-tools libwayland-dev \ libxkbcommon-dev libxkbcommon-x11-dev libvulkan-dev libasound2-dev Install Rust with rustup. The version is pinned by rust-toolchain.toml and rustup will fetch it for you.&#xA;mold is a faster linker, and clang is what invokes it.</description>
    </item>
    <item>
      <title>How-to guides</title>
      <link>https://kaivalya.eu/projects/editor/en/developers/how-to-guides/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kaivalya.eu/projects/editor/en/developers/how-to-guides/</guid>
      <description>Each recipe is a task, start to finish. For what each part is, see the Technical reference; for why, see Understanding the architecture.&#xA;A change is done when the code is written, its tests cover the paths that fail as well as the one that works, its cost is measured where a budget applies, and the documentation says so — in English and in French.&#xA;Add a setting Add the field to Settings in crates/kve-config/src/settings.</description>
    </item>
    <item>
      <title>Building on Windows</title>
      <link>https://kaivalya.eu/projects/editor/en/developers/build-on-windows/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kaivalya.eu/projects/editor/en/developers/build-on-windows/</guid>
      <description>Untested — at your own risk. Nothing on this page has been run on Windows. The editor&amp;rsquo;s libraries were checked to compile for it, from Linux; the window itself has never been built, let alone started, there. Expect it not to work, and expect nobody to have seen why.&#xA;Kaivalya Editor is written on Linux and released for Linux. Windows is not supported: there is no download for it, and nobody tests it there before a release.</description>
    </item>
    <item>
      <title>Technical reference</title>
      <link>https://kaivalya.eu/projects/editor/en/developers/technical/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kaivalya.eu/projects/editor/en/developers/technical/</guid>
      <description>This page describes each part of Kaivalya Editor as it is. To build it for the first time, see Getting started; for a task — adding a setting, a command, a benchmark — see the How-to guides; for why it is built this way, see Understanding the architecture.&#xA;AI authorship. Most of the source code was written by an AI assistant (Claude), directed, reviewed and decided by the human author.</description>
    </item>
    <item>
      <title>Understanding the architecture</title>
      <link>https://kaivalya.eu/projects/editor/en/developers/understanding-the-architecture/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kaivalya.eu/projects/editor/en/developers/understanding-the-architecture/</guid>
      <description>One crate imports the UI framework gpui is pre-1.0 and its API moves. The single most valuable structural decision in this project is that only kve-ui imports it. Everything below is headless and testable without a window, which is what makes the project&amp;rsquo;s definition of done — functional tests including the non-happy paths — affordable rather than aspirational.&#xA;Crate kve-core The rope buffer, cursor positions, edits and undo. No UI. kve-config Settings, the command registry, and the translations.</description>
    </item>
  </channel>
</rss>
