Hello Thunkers. I am working with vocabulary lists to learn a language, and I decided to create different pages, according to the theme they had: let’s say general vocabulary, medical vocabulary… and so on, . But the truth is that most pages contain the same blocks, buttons and pictures, and I’m sure there is a more efficient way to do that than repeating the same pattern. Anyone have any suggestions how to improve it?
2 Likes
Yes, this can be done with a single screen. One way is to have a row index variable. You set it to the starting row number for each category.
So your data is arranged in rows like this:
- general
- general
- general
- medical
- medical
- medical
- medical
- next topic
- next topic
Or, you arrange the categories in columns:
1 2 3
general medical etc
general medical etc
general medical etc
Or, you use Firebase and arrange the data in separate keys and retrieve it when needed.
1 Like
Hi thanks, Tatiang. You are always of great help. The fact is that the structure of each topic is about 4 columns, with about a thousand rows…
Do you know of any example for this?
Do I have to make the blocks directly in the Menú page, but should I need a few variables or what? I have the idea, but I don´t really know how to
Check this out
https://x.thunkable.com/projectPage/5edc557fe6f39247cef3f190
Here’s one way to do it.
Ama
Thank you Jared, I’ll have a look at it
1 Like
It’s outdated. I may need to fix it up. Lemme know if anything doesn’t make sense!
I think it is a bit too much for me, although I am trying to understand it. It will take a while, and it’s a shame if it’s not up to date
Thanks a lot.
1 Like
I’ll put out a new one tomorrow at some point!
G
Great
1 Like
It might be the most straightforward to simply use multiple data source blocks. You would add a data source for each category which means each one needs to be on a separate Google Sheet or Airtable view. It’s more coding (more blocks) but it can work.
Hi, Thunkers
I already have a data source for each category, on separate files on Thunkable data source. And it’s working, very very slouly in the phone, and making it a heavy App, but working. And It’s not really more coding (more blocks), because these blocks are just the same, only with different variable names, and poingting to different files. But I was thinking if I really need all of these repetitions.
Accessing stored variables can be a little slow. You can set an app variable to a stored variable’s value, use the app variable in most of your functions, and then update the stored variable only when needed to save that value to the device.
Thanks Tatiang:
How do I do that?. I just want to know what is the next word I have to see in the list
You just set app variable name to stored variable name. Then use app variable name throughout your code. When you need to change the value of the variable, use the stored variable instead of the app variable. But when you are just referencing/using the value, use the app variable.
Hi Tatiang.
Thanks, but I do not know very well which of the blocks should remain as a stored variable, and which as an app variable,
When you set a variable vaue that needs to be saved on the device, use a stored variable and then set the app variable to that stored variable. Any other time, use an app variable. If that still doesn’t make sense, I wouldn’t worry about it for now. It’s probably not going to speed up your app all that much.
Hi, trying to understand, I’ve made a series of combinations with the blocks I showed to you, but any of them worked fine. Thanks
Hi, Tatiang,
Could you point me in the blocks that I have sent you, which are the ones that could be put as you suggest me "When you set a variable value that needs to be saved on the device, use a stored variable and then set the app variable to that stored variable. Any other time, use an app variable. If that still doesn’t make sense, I wouldn’t worry about it for now. It’s probably not going to speed up your app all that much. " I’m pretty desperate trying to find a solution. Thank you
