docs: improvement requests from the Eclipse Dirigible integration#43
Open
delchev wants to merge 2 commits into
Open
docs: improvement requests from the Eclipse Dirigible integration#43delchev wants to merge 2 commits into
delchev wants to merge 2 commits into
Conversation
Captures the framework gaps hit while migrating Eclipse Dirigible from Harmonia 1.24.2 to 2.1.0, each with the workaround used and a concrete proposal: - Charts: add polarArea + radar types (blocks dropping Chart.js in Dirigible). - Charts: an export/print API (DOM/CSS charts have no canvas to snapshot). - Lucide: react to a changing :data-lucide (currently read once; toggled icons must be split into x-show pairs). - Pickers: a first-class read-only/display mode (only disabled input works today). - Built-in icons: add inbox, eye (and an upload alias of import). Also records why harmonia-i18next was not adopted (a platform catalog-model fit issue, not a Harmonia gap) so it is not re-investigated. Co-Authored-By: Claude Opus 4.8 <[email protected]>
…er), not a Dirigible-only ask Add a 'Who it helps' angle to every item so the reusable, framework-wide value is explicit; keep the Dirigible use case as the concrete example only. Co-Authored-By: Claude Opus 4.8 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A prioritized list of Harmonia framework gaps found while migrating Eclipse Dirigible (its application shells + code-generation templates) from Harmonia 1.24.2 → 2.1.0. Each item has the workaround Dirigible used and a concrete proposal, so Harmonia can absorb them and the workarounds can be dropped.
Doc:
docs/dirigible-integration-feedback.mdRequests (by impact)
polarArea+radar— Dirigible's report/intent DSL allowsbar|line|pie|doughnut|polarArea|radar; the last two have nox-h-chart-*equivalent, which blocks dropping Chart.js.<canvas>), so the platform'scanvas.toDataURLprint path can't be reproduced. AtoImage()/print()helper would unblock it.:data-lucide— the name is read once, so runtime-toggled icons (chart/table, play/pause, sun/moon) had to be split into two<svg x-h-lucide>+x-show. Matchx-h-icon's reactivedata-icon.disabledon the inner input works today (greys the control); a value-display read-only mode would suit preview forms.inbox,eye(and anuploadalias ofimport) — common app chrome that currently falls back to Lucide.Also records why
harmonia-i18nextwas not adopted by Dirigible — a fit issue with the platform's registry-driven catalog model, not a Harmonia gap — so it isn't re-investigated.No code changes; documentation only.
🤖 Generated with Claude Code