Skip to content
New issue

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

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

Already on GitHub? # to your account

Review paradigm styling #862

Open
6 tasks
eddieantonio opened this issue Jun 16, 2021 · 3 comments
Open
6 tasks

Review paradigm styling #862

eddieantonio opened this issue Jun 16, 2021 · 3 comments
Labels
Improvement Expansion or improvement of a current functionality that does already work and meets previous specs

Comments

@eddieantonio
Copy link
Member

eddieantonio commented Jun 16, 2021

I think it's time to reconsider how the paradigms are presented. This includes the presentation of:

I gather most of this will be CSS tweaks, however, I think there might be some HTML tweaks as well. If we decide to use slashes to separate multiple possible realizations, I think a whole lot of Python code would need to be deleted too 😈

@eddieantonio eddieantonio added the Improvement Expansion or improvement of a current functionality that does already work and meets previous specs label Jun 16, 2021
@aarppe
Copy link
Contributor

aarppe commented Jun 17, 2021

Concerning how to distinguish linguistic content (the cells that the FST generates) from the row and column labels, #568 has a relevant observation/suggestion, based on old NDS, as illustrated in the image below:

image

I suppose the blue color was motivated by the labels in question having pop-ups with alternative relabelings.

@aarppe
Copy link
Contributor

aarppe commented Jun 17, 2021

Beyond the above, there are some elements in #505, namely:

  • showing optionally morpheme boundaries (option b.)
  • showing the English phrase translations as pop-ups to the Cree wordforms in the individual cells.

We might consider the rest, i.e. presenting in a pop-up the full range of additional information for each cell with Cree word-forms, separate of this issue.

@eddieantonio
Copy link
Member Author

See: #864 (comment)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Improvement Expansion or improvement of a current functionality that does already work and meets previous specs
Projects
None yet
Development

No branches or pull requests

2 participants