Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add strategies palette to make use of vocabulary strategies for finding symbols #24

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

klown
Copy link
Contributor

@klown klown commented Sep 30, 2024

WIP

This adds a "Strategies" palette and its sub-layers for selecting among various ways to help the user find a specific Bliss symbol.

A new type of cell is introduced here, namely the LabelCell (a Preact component). Its purpose is to label the palette that it is part of. In terms of HTML, the component is rendered as a <label> element, but it is unlikely that this right way to provide the label.

To Do:

  • Complete the strategies functionality.
    • Create a new type of cell, similar to a toggle button, to allow the user to set the strategy mode when they reach the strategy they want to use. Currently the leaf strategy cells are ActionBmwCodeCell components, but they should cause the strategy to "work".
  • Address the labeling relationship between the LabelCell and the palette it labels, e.g., by adding an aria-labelledby or aria-label to the appropriate place,
  • Improve the styling of the LabelCell,

Note that this PR includes the changes from #23.

This PR replaces a previous PR that was not based on the main branch. The code has been appropriately re-based and this new PR issued.

klown added 11 commits July 31, 2024 17:10
Pushing to the navigation stack includes the html element wherein
the palette was rendered so that when going back to it, it is rendered
in the same place.  This allows different areas of the adaptive-palette
to navigate to different palettes.
This move is to match the move of all of the `src` files to the `client`
folder as part of the express server work (`feat/setup-server-src`).
- Not needed: aria-controls was used for the id of the element
  wherein to render the go-back palette, but that id is now stored
  with the go-back palette,
- Confusing: if the code continued to use aria-controls, then its
  value would change depending on which go-back render element is
  currently relevant. But, changing that value is likely confusing
  to an AT user.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant