Android Question Abstract Designer - support for 1920 by 1080

[tdocs2]

Greetings, all.

I am working with a large Android 4.3 tablet 1920 by 1080 scale = 1 (according to the Title Bar on the Abstract Designer on the PC connected to the device, it shows 1920 by 1034 scale = 1). However, the Abstract Designer on the PC only allows me to access around 1390 by 940...

On the device itself, I can move any controls, Imageview, Label, edit box, beyond the "boundaries" of the Abstract Designer, but they "disappear" from the Abstract Designer.

I am connected via the B4A-Bridge and not ADB via USB.

The same problem happens if I disconnect from the device and add a variant 1920 by 1080 scale =1.

Any help would be appreciated.

Thank you.

 

[NJDude]

You don't really need to have the exact screen size to create your layouts, just use the designer scripts, if it looks good then it will be ok on any screen size.

 

[tdocs2]

You don't really need to have the exact screen size to create your layouts, just use the designer scripts, if it looks good then it will be ok on any screen size.

Thank you, NJ.

I understand the value and flexibility that the designer scripts (and anchors) offer as well as the devices found in the UI. Great work has been done in this area in recent months. I like the idea proposed in the Designer UI:

Build a robust layout in 3 steps:

• Anchor - Set the views anchors in the designer
• Scale - Call AutoScaleAll keyword to scale the views based on the device physical size
• Fine tune - Use the designer script to fine tune the layout

I think this premise is based on designing for the smallest res (assume scale=1). I have to experiment some more.

I still find the abstract designer a great feedback tool for stepwise refinement of screen design and wished it reflected a more accurate representation specially for the larger tablets/res.

And I assure, NJ, that I am in awe at the capabilities and power already built in the Abstract Designer and in all of B4A as well as the strength, generosity, and creativity of the B4A community.

Best regards.

 

[Erel]

I think this premise is based on designing for the smallest res (assume scale=1). I have to experiment some more.

I recommend to start with a single "standard" phone variant (320x480, scale=1). You can later add another one or two variants. However don't add many variants. They are not needed and are very difficult to maintain.

 

[tdocs2]

I recommend to start with a single "standard" phone variant (320x480, scale=1). You can later add another one or two variants. However don't add many variants. They are not needed and are very difficult to maintain.

Thank you, Erel.

I found out the difficulty of maintaining multiple variants when I developed and published Bibliis (pre anchor days and I did not fully understand designer scripts). Of course, I can see that the ideal for screen design is to provide a WYSIWYG tool and then let it be scaled to the device res and density. Thank you, once more for the great work done in this area in recent months related to anchors and scripts.

The app I am currently scoping and designing requires a lot more real estate than the minimum variant. I do not know what that minimum variant will be yet, but in the design, I want to achieve what I stated in my reply to NJ (quoting from the B4A UI):

Build a robust layout in 3 steps:

• Anchor - Set the views anchors in the designer
• Scale - Call AutoScaleAll keyword to scale the views based on the device physical size
• Fine tune - Use the designer script to fine tune the layout

Thank you, Erel, for sharing your creativity and great effort in creating the B4A (and B4J) development tool, and for your guidance related to its use.

Shalom,

Sandy