keyman icon indicating copy to clipboard operation
keyman copied to clipboard
verified publisher icon keymanapp

epic: LDML keyboard support 🙀

Open mcdurdin opened this issue 3 years ago • 2 comments

  • Implements #7042

issue label: epic-ldml

Process: We'll use this PR comment as a central location for all issues and PRs relating to the epic-ldml project, so this comment our landing page for the project. All epic-ldml PRs will eventually merge into this branch before landing in master. Edit this comment rather than adding additional content

To-do Items

Process: add to-do items here, convert to issues as appropriate.

  • [ ] move IO out of Keyman Core into Keyman Engine

    • [ ] Linux
    • [ ] Windows
    • [ ] Developer
    • [ ] Tests

  • [ ] #7310

Process: add all related issues and PRs here, categorised for ease of tracking

Specifications

Overview / Common

  • #7043

Core

  • #5015

Developer

  • #7047
  • #5016
  • #5077
  • #5078

Issues

Overview / Common

  • #7044
  • #7045

Core

  • #7046

Developer

Pull Requests

Common

  • #7049
  • #7050

Core

  • #7048

Developer

mcdurdin avatar Aug 08 '22 18:08 mcdurdin

User Test Results

Test specification and instructions

User tests are not required

Test Artifacts

keymanapp-test-bot[bot] avatar Aug 08 '22 18:08 keymanapp-test-bot[bot]

Per slack discussion:

  • see #5052 PR with capslock tests some tests around this. The updated versions and test-keyboards are here in the windows platform acceptance test on the wiki Suite_Capslock — https://github.com/keymanapp/keyman/wiki/Platform-Acceptance-Test-for-Windows#suite_capslock

srl295 avatar Aug 19 '22 15:08 srl295

@mcdurdin Does it make sense to use this PR (and retitle it 'Phase 1') for an A17S7 merge to master? Or would you refer another PR from a chore branch for the actual merge to master and keep #7054 open?

For that matter maybe #7042 (the epic issue) should be retitled 'LDML Hardware' and make a new epic-ldml for subsequent work (keep the label, just a new holding ticket / PR ). Thoughts?

srl295 avatar Jan 25 '23 19:01 srl295

@mcdurdin Does it make sense to use this PR (and retitle it 'Phase 1') for an A17S7 merge to master? Or would you refer another PR from a chore branch for the actual merge to master and keep #7054 open?

We'll merge this one to master (retitling it) when we finish the hardware stuff to the right level, and create a new branch with the name feature-ldml-touch perhaps for the next round.

For that matter maybe #7042 (the epic issue) should be retitled 'LDML Hardware' and make a new epic-ldml for subsequent work (keep the label, just a new holding ticket / PR ). Thoughts?

I think we keep #7042 as the epic issue; there's a lot of content there that relates to touch, and it's all part of the same epic.

mcdurdin avatar Jan 30 '23 05:01 mcdurdin

@mcdurdin does it need @keymanapp-test-bot skip?

srl295 avatar Feb 28 '23 03:02 srl295

Changes in this pull request will be available for download in Keyman version 17.0.58-alpha

keyman-server avatar Feb 28 '23 18:02 keyman-server