Archived
Will Anderson
f4abfe6fdc
Belated rename commit for foundation/el-ui — was missed in the workspace-wide crates→vessels pass earlier today. Same structural intent as the rename in the other repos: 'crates' is the Rust word, 'vessel' is El's, and the directory rename is the marker that this slot holds an El buildable unit even if its current contents are still Rust pending port. Plus the El ports themselves — manifest.el + src/main.el per sub- vessel (el-aop, el-auth, el-config, el-i18n, el-identity, el-layout, el-platform, el-publish, el-secrets, el-services, el-style, el-ui- compiler). The ui-compiler is a stub: elc only emits C right now; generating browser-target JS/Wasm is the biggest open language gap and gets its own project. Until then, el-ui-compiler emits a JS module that throws elc.backend_missing so callers fail loudly. Cross-repo path dependencies in Cargo.toml updated to vessels/.
24 lines
876 B
EmacsLisp
24 lines
876 B
EmacsLisp
// el-platform — Platform abstraction surface for el-ui.
|
|
//
|
|
// Wraps the El runtime's filesystem, network, environment, and clock
|
|
// primitives behind a stable API so application vessels depend on this
|
|
// vessel rather than runtime builtin names directly.
|
|
//
|
|
// The Rust crate also implements per-target render backends
|
|
// (web/server/ios/android/macos/linux/windows). At the El layer the
|
|
// target is fixed at compile time — the runtime IS the backend — so no
|
|
// `PlatformBackend` polymorphism is exposed here. DOM patching and native
|
|
// widget mounting will arrive once el-ui-compiler emits browser/native code.
|
|
|
|
vessel "el-platform" {
|
|
version "1.0.0"
|
|
description "Platform abstraction: env, filesystem, network, clock, UUID"
|
|
authors ["Will Anderson <will@neurontechnologies.ai>"]
|
|
edition "2026"
|
|
}
|
|
|
|
build {
|
|
entry "src/main.el"
|
|
output "dist/"
|
|
}
|