After considering your, Abraham and Ram, solutions and suggestions, I created my table.
I kept my Scroll Arrangement component. It doesn't take up space, it's easy to use for the user, and it's easier for me to manage.
For now I have set 10 rows, but later I will add more.
I made hide the rows/Horizontal Arrangements that don't contain data.
I matched the Namespace TinyDB data with DatePicker.
how can I set the "right arrow" disabled when the date in the DatePicker is set to instant "Now" (after changing days backward and forward)?
I assembled the blocks like this but it doesn't work:
Is this question related to the topic? Else either search in forum or create new topic regarding this. Before that dont forget to hit the properly reply as solutiin which gives you an idea
Hi Spicy, You are right.
So I can correct the topic title in: "How can I create data storage using clock component and display it in a table using calendar?"
They are all related subjects as I explained in my first post. The calendar is just following that thread, until my storing and displaying work together optimally.
Or I can break this thread and create a new topic. However, in this topic there is already the Abraham's suggestion I am working on and I am collecting the questions to ask.
So tell me what you prefer and what is most comfortable for readers
So far I have collected, stored and displayed the first level data. It is for students who have finished the first level of the Self-Pulse Reading technique learning.
Subsequently, the students will access the second level (from Home page) where they will collect the new, more advanced data and will have to display them in the same table.
These second level data must not be mixed with the first level data. So it must be stored separately.
It probably means that the time to dive into the dictionary ocean has come, doesn't it?
Should I further differentiate the names of Namespaces?
Because you are dealing with two separate populations of users, this is a good opportunity to do a Project->SaveAs to lock in your success with your first version and start your expansion in a separate larger project.
This will have the side benefit of giving you a new set of TinyDB storage areas where you can start fresh with new data organizations.
There is a question I have for you regarding second level data:
Is it tied to the same timestamp (tag) used to access your level 1 data?
Will you continue to have only one Submit button but have it now cover both level1 and level2 data?
Also, Can you really fit both levels of data into a single row in your onscreen display table on a phone?
Those need to be answered before data storage design can proceed.
Yes, the tags will be formed the same way as now. Only informations / buttons to click will change.
I could use the same "Save" button, or, if it is necessary, I can replace it with a new "Save" button for level 2.
In the same way I will use the already existing pages, changing their titles, buttons, etc., ...but I will also add the new pages.
I will use the same table structure, but the data will not be mixed. At the time of display, only the data of level 1 will appear (when one is on level 1 of the app) or only the data of level 2 (when one is on level 2 of the app).
Yes ...actually it is
Although for now I use android as a Companion, so theoretically it could be done, but I hope that soon there will be the possibility to build apps for iOS. At what point are you?
Can anyone on the MIT development team answer my question please?
...also, when the build apps for iOS will be available, will the dictionary be included?
