What do you guys think about a text file that store/read all of the text from the components.
Each component with text like Texbox, Label or something else should be stored there and we should be able to download the text file and add different languages and upload the file again.
If you like my idea then vote for it.
I don‘t know if this is possible to integrate but it will be very useful
Yes. I know. I do that for now but this to much work, because I have to add every new component and I have to add the component to the blocks…
This is only an idea
It would be also nice if an
@ExtensionDevelopers try to create an Extension like this.
I don‘t have the programming skills for that
Nobody of the Developers give a postiv or negativ answer so I think this idea fall down the stream and disappears somewhere in the community storage like the other topics
Good idea,currently you can use this extension
I stopped my work on my Wolfram|Alpha extension to work on an annoying problem in Thunkable: Localization is really chaotic when doing it with lots of lists. Therefore I made an extension to make this easier. Simply upload a json file with a...
Reading time: 1 mins 🕑
Likes: 17 ❤
Use a procedural block for all the strings, with an extension that detects the language of the device. Call it when you start a Screen or when the user selects another language …
Your example is very bad, because you have to update the app every single time even if you want to change only one letter… Btw it’s to large you can reduce it with the “any component” feature.
And I said also in one of my posts above that I already use the blocks to do this (and a file that contains all supportable languages). I don’t know if you read the first post, but this is an suggestion for another feature at Kodular where we can use only an text file to translate the app…
Yes, I know, it’s frustrating … I just discover it and I’ll be implementing it in my next projects.
Another point would be that not every app has so few buttons and labels…
It wasn’t the same thing that I described in my first post, but you can also use it like this and it’ll be a solution for that.
In this guide I will show you how to use the new resource utilities component which can be found in the “Utilieties” category.
The component is really easy to use. Create your own json file with all your strings. Upload it… DONE.
Okay… Maybe that’s a bit too fast.
The image below will show you all steps you need to do for a “perfect” solution.
strings.json (238 Bytes)
ResourceGuide.aia (2,6 KB)
The JSON file must have a valid format, like the following one