Requirements:
- The card size is changed using (-) 100% (+) scalefactor in percent. It is done. The customer loves it. Unfortunately, the screen flickers no matter what -- setting "lock screen" to true or not. The whole window is zoomed which for my app it is good and bad at the same time.
- Only the content area is zoomed using (-) 100% (+). Looking for solutions or developing my own. This kind of zooming does not affect the window, side bars, navigation bars, etc., but only the actual content with text sizes also changing. Looking for a solution... or developing it myself. I assume a huge amount of time...
- The layout automatically adjusts to the screen size on desktop and for mobile (eventually defining break points).
For the layout flexibility, my idea is a FlexBox model as used in Flutter (originally from Google). There, all is a widget and all is adjusting according to this model. I am thinking of putting all objects into groups (boxes) and groups within groups. So, defined boxes resize relative to each-other and to the overall geometry model. For example, they can appear on desktop in two or more columns, or they can adjust themselves below each-other in just one column. All will be boxes (groups). On mobile, they also would automatically adjust to the screen sizes, some list views will not appear side-by-side with details views, but go to another window, etc.. I think, we all understand how mobile phone apps are working by now...
https://www.w3schools.com/css/css3_flexbox.asp
For this, inner and outer spaces (padding, margins) are defined for each box with standard defaults, and relative to the window size, boxes adjust in rows and columns within specified areas.
Does anybody have experience using the NativeGeometry from NativeSoft? It is published on GitHub, but last commits are quite some time ago. https://github.com/dagirard/NativeGeometry. Nevertheless, it looks mature and promising. It just reminds me that developer tools in LiveCode seem to not be paying as the target group seems to be too small. But at least, we can exchange and share...
I think, it makes no sense re-inventing the wheel. Maybe others have thought about it more deeply? Or, we can put work together? Or someone is currently working on such a model?
For now, I am using the resizeStack handler on the card and stack level and already my groups are adjusting correctly. But it is not a "model" that could be used outside of such application.
Input is highly appreciated ...
Roland (golife)