@moonsand/dsh-ui-optimize 0.9.31 → 0.11.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/README.zh.md +10 -0
- package/client.js +1338 -4
- package/package.json +5 -2
package/README.md
CHANGED
|
@@ -37,6 +37,16 @@ The **More** row keeps its own line. Folding it in was tried and dropped: the sh
|
|
|
37
37
|
|
|
38
38
|
The launcher follows the pattern of the community plugin [dsh-sidebar-shelf](https://github.com/wumouren114/dsh-sidebar-shelf): register a real rail row, hide the rest with one scoped CSS rule, enumerate entries through the slot API, and select a panel through the shell's own API rather than by faking clicks.
|
|
39
39
|
|
|
40
|
+
### Updates
|
|
41
|
+
|
|
42
|
+
The plugin page gets an **Updates** tab. It reads what is installed from the host's own plugin manager and each package's newest release and publish time from the npm registry — no marketplace plugin involved — then updates the whole eligible set with one click through that same host service.
|
|
43
|
+
|
|
44
|
+
Only releases **published at least 24 hours ago** are installed. Anything younger is listed with the time left and skipped: a release published hours ago can still be withdrawn or patched. A release whose publish time cannot be read is skipped too — the rule cannot be confirmed, so it is not claimed. Releases the host marks **incompatible with the running DSH version** (its `engines.dsh` or a DSH peer package is not satisfied) get their own section, state the version they need, and are never picked by *Update all* — so right after a DSH upgrade the tab tells you what is waiting on the plugins instead of failing mid-update.
|
|
45
|
+
|
|
46
|
+
Updates run through the host plugin manager, i.e. the same path the plugin page uses when you update one entry by hand; progress and failure codes come back from it. Reload the page afterwards: the new client half only loads on a fresh page.
|
|
47
|
+
|
|
48
|
+
If the host's plugin manager is unavailable, the tab says so instead of pretending to check.
|
|
49
|
+
|
|
40
50
|
## Known limitations
|
|
41
51
|
|
|
42
52
|
- The theme choice lives in browser `localStorage`; it is lost with the browser profile or site data
|
package/README.zh.md
CHANGED
|
@@ -52,6 +52,16 @@ dsh plugin 或 GUI 插件管理:安装 @moonsand/dsh-ui-optimize
|
|
|
52
52
|
|
|
53
53
|
启动面板的做法参考社区插件 [dsh-sidebar-shelf](https://github.com/wumouren114/dsh-sidebar-shelf):注册一根真实的竖栏行、用一条 scoped CSS 规则隐藏其余行、通过槽位 API 枚举条目,并用宿主自己的接口选中面板,而不是伪造点击。
|
|
54
54
|
|
|
55
|
+
### 更新
|
|
56
|
+
|
|
57
|
+
插件页多一个「更新」页签。已装清单取自宿主自带的插件管理服务,最新版与发布时间直接从 npm registry 读——不依赖任何插件市场——再通过同一个宿主服务一键更新整批够格的版本。
|
|
58
|
+
|
|
59
|
+
只装**发布满 24 小时**的版本;更年轻的会列出剩余时间并跳过——刚发几小时的版本还可能被撤回或补丁。读不到发布时间的同样跳过:规则无法确认,就不假装确认过。宿主判定**与当前 DSH 版本不兼容**的版本(`engines.dsh` 或某个 DSH peer 包不满足)单列一区,写明它要求的版本,并且永远不被「一键更新」带上——刚升级完 DSH 时,页签告诉你是哪些插件还没跟上,而不是等你点下去才失败。
|
|
60
|
+
|
|
61
|
+
更新走宿主插件管理服务,和你手点单个插件的更新是同一条路径;进度与失败码由它回报。更新完刷新页面:新的客户端代码只在重新加载时生效。
|
|
62
|
+
|
|
63
|
+
宿主的插件管理服务拿不到时,页签直接说明查不了,不会假装在检查。
|
|
64
|
+
|
|
55
65
|
## 已知限制
|
|
56
66
|
|
|
57
67
|
- 主题选择保存在浏览器 `localStorage`,换机器或清站点数据会丢失
|