feat(desktop): 跨平台桌面端 + 电脑↔电脑互传(v0.5.0-m1)
对应 V05_EXECUTION_PLAN 的 P1。核心改动是把「PC 只能当服务端」 这个写死的角色拆开——此前 TcpStream::connect 只出现在测试里, 桌面端根本无法主动连接另一台桌面端,PC↔PC 因此完全不可用。 跨平台 - windows/ → desktop/,crate 更名 qft-desktop - 新增 platform.rs 收敛全部平台差异:配置目录(LOCALAPPDATA / Application Support / XDG)、下载目录(含 Linux 本地化的 ~/下载)、 设备名、Direct AP 能力。约定:其余模块不得再出现 #[cfg(target_os)] - direct_ap.rs 的 Context 导入按平台条件化,非 Windows 上不再告警 - macOS 上已实测编译并链接出可执行文件(65 MB Mach-O arm64), 这是本仓库首次在非 Windows 平台构建成功 电脑 ↔ 电脑 - 新增 client.rs:桌面端发起侧。手写 HTTP,不引入客户端依赖—— 服务端本来就是手写的,两边同一套解析更容易与 Android/iOS 对齐。 含并发分块上传(自适应 4/8/16 MiB、最多 8 worker)与 Range 断点续传 - 新增 discovery.rs:UDP 广播 QFTBROWSE3 浏览局域网节点。 既有的 QFTDISC2 是「已知令牌找机器」,用于扫码之后; PC 没有摄像头,必须先能列出附近有谁 - receiver.rs 新增 POST /qft/pair:用 6 位配对码换会话令牌。 这是唯一不校验令牌的端点。6 位仅约 20 bit 熵,配严格失败计数兜底—— 错 5 次即作废,需重启接收;比较用定长实现,不做短路返回 - 新增「电脑 ↔ 电脑」界面:接收方显示配对码与本机地址; 发送方搜索/手动输入地址 → 输码连接 → 多选文件 → 带进度发送 验证(macOS,Rust 1.97.1) - cargo check 0 错误,cargo test 17/17 通过 - 新增端到端用例:真实起接收服务 → 配对(含错误码必须被拒)→ 9 MB 跨多分块并发上传 → 校验落盘内容逐字节一致且 SHA-256 与 接收端返回值相同。这就是 PC↔PC 的完整链路 - 11 项 Python 自检全部通过 顺带修复 - single_channel_guard_selftest 长期为红:它断言 DEFAULT_CHUNK_SIZE = 450,而代码早已改为 320。改名前即存在, 已用 git stash 验证与本次无关。改为范围检查(128~4096)并在 PASS 信息里打印实际值,既挡住"退回多通道小块"又不会因调参误报 已知限制 - UDP 广播只覆盖同一广播域。跨网段或 AP 隔离的 Wi-Fi 上搜索不到, 需手动输入对方 IP(界面已说明)。mDNS 留待后续 - 本阶段仍走 v2 明文 HTTP,加密随 QFT-Stream v3 一起做(见 P2)
This commit is contained in:
@@ -0,0 +1,56 @@
|
||||
# Windows UI / device identity update — v0.1.3
|
||||
|
||||
## 1. Chinese UI font
|
||||
|
||||
The Windows sender no longer relies on egui's default font for Chinese text.
|
||||
It loads a TrueType font (`.ttf`) at runtime and installs it as the first
|
||||
Proportional and Monospace font fallback.
|
||||
|
||||
Lookup order:
|
||||
|
||||
1. `QFT_FONT_PATH`
|
||||
2. `qft-ui.ttf` next to the executable
|
||||
3. `assets/qft-ui.ttf` next to the executable
|
||||
4. `./assets/qft-ui.ttf` from the current working directory
|
||||
5. common Windows Chinese `.ttf` files
|
||||
|
||||
For development, the most deterministic setup is to put your own Chinese-capable
|
||||
TTF at:
|
||||
|
||||
```text
|
||||
windows/assets/qft-ui.ttf
|
||||
```
|
||||
|
||||
No font file is bundled by this project.
|
||||
|
||||
## 2. Device display
|
||||
|
||||
The Windows sender now displays:
|
||||
|
||||
```text
|
||||
本机设备:DESKTOP-XXXX
|
||||
传输设备:DESKTOP-XXXX → Android 光学接收端 · 正在传输
|
||||
```
|
||||
|
||||
The MANIFEST payload now appends:
|
||||
|
||||
```text
|
||||
sender_device_len: u16
|
||||
sender_device_utf8: bytes
|
||||
```
|
||||
|
||||
The Android app displays both endpoints, for example:
|
||||
|
||||
```text
|
||||
传输设备:DESKTOP-XXXX → Xiaomi 15
|
||||
```
|
||||
|
||||
The field is appended to the end of the old MANIFEST payload, so the new Android
|
||||
parser remains compatible with v0.1/v0.1.2 manifests.
|
||||
|
||||
## Important limitation
|
||||
|
||||
Windows -> Android is intentionally a one-way optical channel. The Android phone
|
||||
does not send any ACK or identity back to Windows, so the Windows sender cannot
|
||||
automatically know the exact receiving phone model. The Android side can show
|
||||
both the sender PC name and its own local device model.
|
||||
Reference in New Issue
Block a user