Guidance: building a CarPlay-style launcher on the Tab5 (fork of pocket-shell) with installable applets and background services

未关闭
#668 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript
领域
embedded-iot

调研方向

Start with docs/LAUNCHER.md and docs/APPLETS.md, then inspect the PR #616 host at programs/m5stack-tab5 and the shells/3ds/shell launcher. The issue asks for architectural decisions on concurrent guests, device services, and auxiliary surface sizing rather than specifying a change; clarify which direction maintainers support before proposing work. Done would require an agreed, scoped proposal or implementation target.

由索引模型根据 Issue 内容生成。

描述

Hi, I'm building a standalone bicycle head unit on the M5Stack Tab5 with PocketJS, and I'd like advice on the architecture before going too far in the wrong direction.

Setup

  • M5Stack Tab5: ESP32-P4 rev v1.3, ST7121 panel (BSP reports board version 3), 32 MB PSRAM
  • ESP-IDF v6.0.2, PocketJS v0.16.0 (submodule), my own board program built from platforms/esp-idf components
  • Landscape 640x360 logical at raster density 2, animation: repaint, 30 Hz
  • PR #616's programs/m5stack-tab5 (head df0d434a) runs on this unit: the Clear demo at 30.2 fps with no skipped frames

Goal

Fork pocket-shell's launcher (shells/3ds/shell), redesign it as a CarPlay-style UI (status bar, side dock, dashboard cards), and keep installing Pocket Applets: map navigation, music player, BLE bike-light remote.

Questions

  1. Tab5 host base. pocket-shell says the Tab5 firmware is pocket-m5's programs/m5stack-tab5, but github.com/pocket-nexus/pocket-m5 returns 404 for me. Will it become public, and under which license? Until then, is PR #616's programs/m5stack-tab5 (with pocket_system, the home ball and the launcher ops) a reasonable base for a third-party Tab5 launcher host?

  2. More than one guest at a time. docs/LAUNCHER.md says each program runs one guest at a time, and the #616 host destroys the running guest before booting the next. pocket_runtime_create looks instance-based (the global state I found in runtime-cabi is behind legacy-ui). Is running two pocket_runtime instances concurrently on ESP-IDF (for example the launcher's dashboard plus one applet, each in its own screen region) supported or planned? Are there known singletons in pocket_guest_quickjs, the PPA lanes or pocket_display_esp_dpi that rule it out? Related: #429 (GC on ESP-IDF).

  3. Device services for applets. The applet allowlist in docs/APPLETS.md has no GNSS or BLE. My plan is to keep music playback, route tracking and the BLE light connection in firmware services that outlive any applet, and expose them to applets as companion services: the host answers https://companion.pocket/<service>/… locally instead of forwarding to the Mac. Is that an intended use of services, or would you prefer new capabilities (for example location.gnss) added upstream? Would you accept a proposal for either?

  4. Applet surface on a landscape launcher. With a side dock, applets would get roughly 560x360 (adaptive, containing 320x240). Is anything in the tab5-home contract or the admission rules that assumes the auxiliary surface is the whole 640x360 picture?

Thanks for PocketJS. Happy to report hardware results back (the ST7121 v1.3 bring-up notes are already written up).

主要语言
TypeScript
星标
1.6k
派生
88
PR 合并指标
30 天内没有已合并 PR

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pocket-stack/pocketjs 的其他 Issue

查看 pocket-stack/pocketjs 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。