AW: Best practise approach for artwork for iOS and Android?

Tiemo Hollmann TB toolbook at
Tue Jun 12 03:01:27 EDT 2018

Hi Jacque,

I thought the dpi only reflects at print, because any screen has it's fixed
pixels. I think an image 800x600 with 144 dpi looks identical on any screen,
as an image 800x600 with 72 dpi because in both cases 800x600 screen pixels
are being used and there is nothing between the pixels. Or don't I see
anything here?

But perhaps I really hould try to start the project with the old 800x600
images, as you and also Kee Nethery pointed out. In this case I am not sure
what would give the better quality in point-of-view resolution. Importing
the original old 800x600 images into LiveCode and let the LiveCode engine
stretch (not distore) the images to a full screen size (with white space on
some edges at some disply sizes), or would photoshop make a better job in
interpolating pixels, if I would enlarge all images in photoshop to lets say
2732x2014 (or even 3200x2400) and let the LiveCode engine shrink the images
to fit each screen.


-----Ursprüngliche Nachricht-----
Von: use-livecode [mailto:use-livecode-bounces at] Im Auftrag
von J. Landman Gay via use-livecode
Gesendet: Montag, 11. Juni 2018 21:58
An: How to use LiveCode <use-livecode at>
Cc: J. Landman Gay <jacque at>
Betreff: Re: Best practise approach for artwork for iOS and Android?

I would bulk-convert all the images to a higher resolution, perhaps 144dpi.
On Mac, Graphic Converter can batch process these in seconds, and I am sure
there are other programs that do the same on both Mac and Windows. Use these
higher-resolution images in your project.

On mobile, use fullScreenMode "showAll", which will automatically adjust the
display to fit any resolution and screen size on both iOS and Android.
Depending on the original card size, some edges will either be cropped or
empty space will be added. There are ways around this, mainly by displaying
an image at a larger size than the (original) card size.

There was a bug in the showAll fullscreenmode when navigating cards, but
that has just been fixed and will be in the next 9.0 release. There are also
workarounds for this right now if you don't want to wait.

This is a quick process that doesn't take much time because you won't have
to adjust every image.

On 6/11/18 3:54 AM, Tiemo Hollmann TB via use-livecode wrote:
> Hi,
> I have three old windows program (going back to the 90th), designed 
> for children, which are based on "full window" image backgrounds 
> (douzends of cards, each with another background image) and lots of small
detail images.
> Up to now I have only developed LiveCode for Windows and MacOS, no 
> experience yet with iOS and Android development. I try to evaluate the 
> work load to redevelop those old windows programs for mobile and one 
> general question before I start is the art work. Since the old art 
> work has a size about 800x600 by 72dpi, I obviously would need to let 
> redesign all art work for the todays resolutions, which would be a 
> pretty costly part of the project and probably the go or nogo for the
whole project.
> Since there are so many different screen sizes, resolutions and aspect 
> ratios on iOS and Android, I wonder how to cover all those variants 
> technically in LiveCode and basically from the art work side. E.g. 
> which size and ratio I would have to let create the "master" images by 
> the artist (to be also on the safe side for the next years)?
> Since I can't let design for each ratio a different master image for 
> each card, I probably would have to distort the "master" image to each 
> different screen size (app only for tablets in landscape mode)? Could 
> I let make the OS the distortion of one background image per card in 
> LiveCode, or would I need to import and assign different images (which 
> I have distored in photoshop before) for each screen size in each 
> card? Additionally I would need to create douzends of polygons as 
> clickable objects, above each image for small parts of it, where I am 
> not sure, if they would keep their exact target area, when the background
image will be distort - probably not.
> Up to now it looks to me as a never ending story, but perhaps I don't 
> see a good approach
> Any experience or pointers to a how to are very welcome.

Jacqueline Landman Gay         |     jacque at
HyperActive Software           |

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription

More information about the Use-livecode mailing list