Define a dialog library
Nobody has claimed this yet.
- Dominant language
- Assembly
- Stars
- 322
- Forks
- 29
- Avg merge
- 24m
- Merged PRs (30d)
- 3
Description
There are hints of this in the common dialogs in DeskTop (used for file copy/delete and selector entry add/edit), but it could be formalized.
Introduce a declarative format like the following:
dialog_resource := num_controls controls...
control := rect | label | push_button | check_box | radio_button | text_input
rect := pen_mode, left, top, right, bottom
label := left, top, string
push_button := id, left, top, right, bottom, string
check_button := id, state, left, top
radio_button := id, state, left, top
text_input := id, max_length, left, top, right, bottom
A handful of calls would be needed:
- GetTextInputString(id, pbuffer)
- SetTextInputString(id, str)
- GetButtonState(id, pstate)
- SetButtonState(id, pstate)
... and a custom event loop that provides for clicks on buttons (reporting ids) and keys (Enter, Escape, Apple-x).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the common dialogs in DeskTop used for file copy/delete and selector entry add/edit. Trace how those dialogs currently represent controls and process clicks and keys, then compare that behavior with the proposed declarative format and calls. Done means the library design, accessors, and event-loop behavior are specified consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100