As I already specified here, I already found a solution to have a ChromeOS/AI2 Companion native, on a big screen machine with touchscreen (ChromeBox like).
I start with a "static" approach to designing the layout for my app. In the same thread, @TIMAI2 came up with the idea that the dynamic approach is the best approach than static due to the huge amount of info on screen and the limitations of the AI2 designer.
It was right. The .aia that it makes, is so simple to follow from a logical point of view, that even a noob like me that know nothing about programming, can follow and develop in no time (a few hours) an elegant layout on a big screen.
USLayout_1.aia (84.8 KB)
Above it is my .aia made following the TIMAI2 logic.
But... My luck is ended... TIMAI2 uses a timer to display some strings on cells. For the moment I don't want to use timers. So... I want to adapt his logic to what I want. After half a day and a night of trainings...no luck. I'm stuck on some things that I don't find the logic.
1 - I want to display the ID - the number of the cell, but I can't and I don't understand why, I don't find any example or documentation about how I can. I have tried many approaches but without success.
2 - I want to have a button, in the place where the image are... I can't.
Any help/suggestions will be highly appreciated.
Thank you in advance, Dan
PS - The dynamic design is best where things are repetitive, and the static approach is best in places where things are not repetitive. So... A mixed dynamic/static approach must be used.