Skip to content

Some option lists should have a different configuration UI #977

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

Open
rmunn opened this issue Jun 10, 2021 · 0 comments
Open

Some option lists should have a different configuration UI #977

rmunn opened this issue Jun 10, 2021 · 0 comments

Comments

@rmunn
Copy link
Collaborator

rmunn commented Jun 10, 2021

There are some option lists, such as Semantic Domains and Grammatical Categories, that need to have a different UI for editing them in the Language Forge project configuration UI. Grammatical Categories (which our UI usually calls "parts of speech") in particular are tricky, because there are canonical GUIDs that FieldWorks expects grammatical categories to have. A noun, for example, is expected to have the GUID a8e41fd3-e343-4c7c-aa05-01ea3dd5cfb5 no matter what name or abbreviation it may have. If Language Forge allows users to create new entries in the grammatical categories list, then we need UI to let them choose from the canonical list of grammatical categories, and make it kind of hard to create a custom one. (Maybe it takes two or three clicks, one click on "Advanced" and a second click on "Create Custom", and then if the name you typed matches one of the canonical categories, you get given the canonical one anyway instead of creating a custom one).

At the moment, there's a commented-out section of code in LfMerge to sync custom list entries between LF and FieldWorks. The reason it's commented out is given in a comment that says "Once we allow LanguageForge to create optionlist items with "canonical" values (parts of speech, semantic domains, etc.), uncomment this block". My recent tests with Send/Receive of custom lists failed to transfer the new list entries from LF to FieldWorks, and on finding that commented-out block, now I know why. If I allowed send/receive of new list entries created in LF, there's a strong chance that many projects would get their FW data into a weird, inconsistent state where there were two identical entries for "pronoun", etc., in the parts-of-speech list, and then there would be much user confusion over which pronoun entry was the right one.

I'd like to allow optionlists edited in LF to be transferred via Send/Receive. But before that can happen, we have to figure out the UI for editing grammatical categories (and any other lists with specific canonical values in FW).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant