Default dictionary

[willwade]

Asterics AAC doesnt default load a dictionary. Why? Because a. It's only relevant for those who need prediction and b. It blows up the server storage as it gets added to the online backup per user. The problem though is that for many people trying it out they expect prediction to work.

Idea 1 (@klues idea):

There should be a question popup if someone without a dictionary imports a gridset with prediction elements to ask if a dictionary should be imported.

This is sound and should be done... But just as I have to get it out of my head - whats the alternative?

Idea 2:

Diff changes to the cloud storage. If you dont ever change your dictionary dont upload it. Then auto load with no warning a dictionary for your locale. Cons: if you dont actually use your locale this is going to get messy.

idea 3:

Overhaul prediction. Only put changes/local frequency changes in a localdb which gets synced. This feels fragile though..

Yes - Idea 1 is the answer I think :)

[RonaldRonnie]

Idea 1 strikes a good balance—it’s user-friendly and respects the needs of users who don’t require prediction. @willwade @klues , Would it be possible and a good implementation to design the popup so that it intelligently suggests a locale-appropriate dictionary, while still allowing users to skip or manually select a dictionary?

This might help avoid the complications mentioned in Idea 2 and keep things straightforward for new users.

[willwade]

Ok - I've done this is as neatly as possible in the #635 PR..

If someone could try it out for me that would be great :)

[arasaac-dga]

We have tried but, for example, for this spanish model the suggestion have no sense, it's not the Online Spanish Dictionary that must suggest.

If you press in More dictionaries and select an online (must be the default option) spanish dictionary it's ok

[willwade]

OK I've done a bit more work on this @arasaac-dga - try again on https://gridbeta-github.asterics-foundation.org/willwade/feature-prompt-for-dictionary/pr and let me know (turns out this is a bit trickier than I hoped!)

[arasaac-dga]

Tested on Spanish and English and now offer online dictionary as expected and on the language selected for the model. So, it seems to work as expected. Great!!!

[ms-mialingvo]

Working for me too.

It would be good to also have a sentence along the lines of "this grid set also uses languages x, y, z, so consider importing dictionaries for these languages too".

[arasaac-dga]

We have tested and work with some models but with others no:

1. Single language Spanish -> Works
2. Single language English - > ARASAAC models (both) -> fail (don't offer online dictionaries) :-(

3. Multilang models -> Fail too :-(

[ms-mialingvo]

I've tested on those and it's working fine for me. Maybe the 'Grid content language' in the language tab in the settings is not set correctly? But also in the screenshot it's showing an English grid set and suggesting English dictionary so that's correct.

[arasaac-dga]

To test I always, reset the account and select a new model filtering by language. It's a natural way to proceed. It's interesting that @willwade try to reply the issue because other users can suffer it.

[ms-mialingvo]

If you mean the reset to default configuration I do that too. I still don't understand what the issue in the screenshots is.

[klues]

thanks @willwade for working on this.
My imagination always was this from the UI side after importing something which could need prediction:

• Import [Lang]: imports a suggested (most likely) language (e.g. current content language), directly imports it, maybe just with a success notification afterwards
• Import other opens this already existing modal from the dictionary management:

I'm not a fan of the quite intrusive UI with a modal where people are forced to react. I like the notification better, which automatically disappears after some time.

Code for this Popup - of course needs translations of the labels etc.:

MainVue.setTooltip("Do you want to import a dictionary for word predictions for this configuration?", {
                actionLink: 'Import German',
                actionLink2: 'Import other',
                actionLinkFn: () => log.warn("test"),
                actionLinkFn2: () => log.warn("test2"),
                timeout: 20000
            })

[willwade]

Great points @klues. I’ll give that a go later in the week

[arasaac-dga]

It would be good to also have a sentence along the lines of "this grid set also uses languages x, y, z, so consider importing dictionaries for these languages too".

Yes. We agree. The system must offer the possibility of import all the dictionaries in multilang models.

If you mean the reset to default configuration I do that too. I still don't understand what the issue in the screenshots is.

The problem is the name of the dictionaries that offer as option that are confuse.

In this case offer a dictionary named "Asterics Grid default board on English" (Tablero predeterminado de Asterics Grid en Inglés) which is confuse. In other cases offer the correct online dictionary on English (Inglés (hermitdave@github.com) ) and Spanish (Español (hermitdave@github.com)).