One Rect For All specificaiton

Sannyasin Brahmanathaswami brahma at hindu.org
Sun Jan 3 23:18:28 EST 2016


HA @ colin:  “Almost all of the things I’ve done have been ‘showAll’ "

and here I was thinking you were recommending  “noBorder” as the optimum development strategy.

But the whole exercise is still very useful. I think it is still the case that if you want to have someone (and need to provide specs and instructions) doing illustrations / or story boards for you—regardless of the LiveCode card size one choses to working—we *still* need to use — for instructions:

1400 X 900  (as a ratio on paper, it could be bigger in inches decimal) as the “you must fill this canvas wall to wall”

with 1200 X 788 (as a ratio, on paper it wouldbe an area “inside” the canvas) as the “Be careful that all your important elements fall inside this ‘safeZone’.

My current experiment in “noBorder” has the useful result that I can actually visualize the entire canvas on the card. Whereas with “showAll”  if you work in iPhone 6+ (16 X9)  then you can’t tell what is “lost” on the iPad and you can also get yourself in trouble by adding elements top and bottom (or left and right) that will not appear on the iPad. Since we are talking about 2D animation with illustration rich background content… it’s not something we can “fudge” at all.

But…with if you create a set of bottom tab controls for a landscape app in iPhone 6+(16 X9) and place these in the “safe zone” then use “no border” they will float above the bottom on the iPad (in landscape) where as if you build those to be at the bottom of the screen/card, “showAll” will be sure to place them there on iPad… at least I think… will have to test.

Colin wrote: "You could use the 1024x768 iPad preset and then have extra content that extends out to 171 pixels either side of the card, that you don’t normally se while working on the stack.”

But then wouldn’t you have the issue of losing the top and bottom if you run the same app in iPhone 6+ landscape?

So, now I’m back to choice paralysis on which way to go.

I did work out the 14 X 9 and 1200 X 788 with a young designer here and we transferred this to US Letter and made a template for him to work in storyboards into… and it seems to work pretty well. I will have to import his work into a 16 X 9 stack and try “showAll” and see what happens.

BR
On January 3, 2016 at 6:32:50 AM, Colin Holgate (colinholgate at gmail.com<mailto:colinholgate at gmail.com>) wrote:
A key difference between showAll and noBorder is that with noBorder all of the content you will ever see has to lie within the card area. With showAll only the content that everyone will see is in the card area, there remember is off the edges of the card, and will get revealed to users with either wider or taller devices.

Almost all of the things I’ve done have been showAll, where either it’s a book like experience, where I want to be sure everyone sees the full height of the page (and there is extra sideline content that will appear), or it’s a game, where a bit more ground and sky appears on taller devices.

The one time I did use noBorder it was for a game that had interesting items in all directions, and so I used the 14:9 trick to compromise between 16:9 and 4:3 screens.


More information about the Use-livecode mailing list