On 09/11/2011 17:08, Andre Garzia wrote:
Scripting resizeStack is a good exercise but we really should aim to some form of resolution independence here. Mobile apps tend to use more images as decoration than desktop apps, with all those different resolutions, you need to carry a lot of images of different sizes in your app or loose time resizing them at runtime. Asus Eee Prime Pad is just one among the different Android Tablets our there, each running a different resolution and screwing my resizes.
So long as we don't have proper resolution independence, should we instead try for re-sizing at installation time (or, failing that, perhaps "resize on first use").
I know almost nothing about mobile - but I suspect that in most cases the resolution is 'fixed' for any particular installation of an app, so resizing either as the last step of installation or when the image is first displayed would avoid repeated time lost to resizing. You might need a "meta-resize" to determine for any particular screen resolution what size each of your images needs to be. Then, if mobile installation allows it, you could do a one-time resize of the images; if not then it might need to happen on first use. Would users prefer to see a message ("New installation being completed") on first starting up an app (maybe combined with registration or other first-time actions)? Or would it be better to simply hide that cost during usage ?
-- Alex. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
