feat(developer): New Project Parameters dialog in web/svelte#14692
Draft
feat(developer): New Project Parameters dialog in web/svelte#14692
Conversation
This is a prototype of the New Project Parameters dialog rewritten in svelte, and hosted as a web page within the existing TfrmNewProjectParameters form in Keyman Developer IDE (TIKE). The intent of this prototype is to explore ways of incrementally moving UX out of Delphi and into cross-platform web-based systems. Thus, this is not complete (e.g. Targets is unlinked, no bcp 47 picker, issues with the Browse-for-folder dialog), and the choice of UI framework (Bootstrap/Sveltestrap) and even of Svelte itself is all up for discussion. The Svelte project is also currently running only in dev-mode, and would need to be integrated into the existing Keyman Developer Server. This is all well understood (there are adapters to link between Svelte and Express, which is our backend http server in KMDevServer). In my opinion, this looks like a viable way forward to incrementally rewrite parts of Keyman Developer. I look forward to other peoples' thoughts on this broad-brushstroke design and concept. This also comes out of the discussion we had on #14657, where validation messages were added to the New Project Parameters Delphi form, and for implementation cost reasons, were put into a much expanded form, resulting in a lot of wasted space on the form -- the web paradigm should serve us much better for this kind of thing. Build-bot: skip Test-bot: skip See-also: #14657
User Test ResultsTest specification and instructions User tests are not required |
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
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.
This is a prototype of the New Project Parameters dialog rewritten in svelte, and hosted as a web page within the existing TfrmNewProjectParameters form in Keyman Developer IDE (TIKE). The intent of this prototype is to explore ways of incrementally moving UX out of Delphi and into cross-platform web-based systems. Thus, this is not complete (e.g. Targets is unlinked, no bcp 47 picker, issues with the Browse-for-folder dialog), and the choice of UI framework (Bootstrap/Sveltestrap) and even of Svelte itself is all up for discussion.
The Svelte project is also currently running only in dev-mode, and would need to be integrated into the existing Keyman Developer Server. This is all well understood (there are adapters to link between Svelte and Express, which is our backend http server in KMDevServer).
In my opinion, this looks like a viable way forward to incrementally rewrite parts of Keyman Developer. I look forward to other peoples' thoughts on this broad-brushstroke design and concept.
This also comes out of the discussion we had on #14657, where validation messages were added to the New Project Parameters Delphi form, and for implementation cost reasons, were put into a much expanded form, resulting in a lot of wasted space on the form -- the web paradigm should serve us much better for this kind of thing.
Build-bot: skip
Test-bot: skip
See-also: #14657