Back to layout.
I spent about four weeks experimenting with 4K/27" system and 3K/13" tablet and I have some conclusions. Please remember that these conclusions came from a noob point of view in ChromeOS and AI2, almost sure that if a real professional on AI2/ChromeOS can have the same mediums at his disposition, possible it will be other conclusions.
First of all, AI2 Companion on both hardware systems crashes. Why it crashes, I don't know, but the logic behind these crashes that I see, I will write it on continuation.
First of all, I have two .aia, one "static" approach and another "dynamic" approach to generating the layout.
That one is the "dynamic" approach.
USLayout_dynamic.aia (141.3 KB)
That one is the "static" approach.
USLayout_static.aia (209.3 KB)
Please don't criticize the unfinished work from both. It is conceptual experimental work not a finished work.
-
The first conclusion is about the file size, the static approach is almost two times bigger. If I will use that approach in the future, it will be somehow different, because meanwhile, I learn more and more "tips and tricks" about how to approach the static version of the layout.
-
Another conclusion is about crashing. For example, the dynamic approach crashes after 4 Refresh Companion Screen on 4K/27" 32 GB-RAM, and after 15 Refresh Companion Screen on 3K/13" 8GB-RAM tablet. The static approach crashes after about 16 Refresh Companion Screen on 4K/27" 32 GB-RAM and after about 60 Refresh Companion Screen on 3K/13" 8GB-RAM tablet.
That behavior makes the dynamic approach useless on a 4K/27" machine and a nightmare on the 3K/13" tablet. In the static approach until now, can be supportable the crashes on both systems. Anyway, I don't understand how it is possible that in the same amount of refresh, the RAM is full and simply... crashes, no errors... simply crashes and disconnects from AI2. This can be a bug of ChromeOS or AI2 from my point of view as a noob. Any opinions about that are more than welcome.
Now I want to thank again @TIMAI2 for his dynamic aia, it was a huge inspiration source for me as a noob to understand a huge amount of "tips and tricks" about AI2. Not only his .aia, but his .aia open for me a huge fan of reading about what and how it can do some things.
Anyway, last week I spent learning about how can I generate a second dynamic list from a static list and a dynamic index. I can't. Simply I don't know the tools that I can use to achieve that purpose.
So for me at this point the dynamic approach is death. I can't use it. As I write above, my goal is to prove a concept, the concept of displaying data on 128 cells, not how to generate those cells, statically or dynamically.
Anyway, if @TIMAI2 or another professional here in this community, can, want, have time to correct my "dynamic" .aia, I'll be pleased to use the dynamic approach on continuation. If I have in the final of .aia a list with the cells ID, I think that I can use that list for future purposes.
Anyway, if nobody has time, can, want... I will redesignate a new app with the static approach, I will give an ID to 128 arrangements, as I need as order, I will use the canvas text placement facilities to display the labels, and so on... Or... I can use the same as the above approach, in combination with the label plus extension or... any other combination of the static/dynamic approach of alignments.
I want to thank you for reading this thread and if you can, want, or have time to help. Dan