[quote=346006:@Michel Bujardet]RubberViewsWE brings Auto Layout to Xojo Web already.
Well indeed , it is there, but as well the 200$ for it which it is not much but not for now i guess, if i charge the customer for it i don`t mind but when i have to pay from my pocket for it no .
On the other side XOJO team already has the functionality for the IOS Interface so i guess it can be adapted for Web as well which is more essential actually considering custom screens and layouts.
In iOS, auto layout is largely built into the framework. So I would suppose Xojo took advantage of the framework building blocks.
In Web, there is pretty much nothing, it has to be created from scratch. So it is not as easy as adapting the iOS Auto Layout to Web.
If you are not willing to invest in a third party tool, the best you can do until if ever Xojo implements Auto Layout in Web, is learn how to devise a responsive UI yourself in Xojo. The principles are known. The implementation demands some efforts.
Having been working on a ton a webprojects in recent years - many not with XOJO. I still think AutoLayout is an awful idea for web. There’s a reason why ResponsiveDesign with a column based approach is now the standard on just about every major Web UI Framework.
Now image sets don’t just get a 1x and 2x. They also can get a 1x Compact and 2x Compact. (Not to mention there now exists a 3x)
Explaining SizeClasses, TraitCollections, Horizontal/Vertical - Regular/Compact Interfacing, etc… is both complicated and Apple-centric.
Explaining a column based layout with breakpoints can be done in under 2 minutes. Each container gets its column count for each screensize (i.e. breakpoint). Pick adequate margins and nest containers however you want and everything just looks and works great. And this concept is very cross-platform relatable.
I would much rather tell a control: “6 columns on medium and down, 3 columns on large and up” (i.e. 6md, 3lu)
rather than the complicated relational pins and struts and formulas for each of Horizontal/Vertical - Regular/Compact.
I definitely think the AutoLayout way of being able to tell a control all the rules of its positioning is powerful and helpful, but it should not be the regular case. Dragging and dropping a control and then toggling a few column counts would serve 90% of people’s cases as well be easy to learn and do.
I could see something like for each View/Container, allowing a dropdown list of “LayoutTypes” that could be customized. Let the user pick Autolayout or a ColumnBased configuration with breakpoints.
One of the first controls I make in any WebProject is a subclass of webContainer called ContainerList that allows you to just keep adding/removing containers to it. The control autopositions the containers based on a few settings: Horizontal/Vertical, MarginSize, Wrap/Scroll, AutoResize
It would be nice to see Xojo add something into the base offering such a common and necessary feature.