Re: supporting multiple mobile device resolutions

ctor Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Bob Sneidar Sent: Tuesday, February 14, 2012 12:28 PM To: How to use LiveCode Subject: Re: supporting mul

RE: supporting multiple mobile device resolutions

, 2012 12:28 PM To: How to use LiveCode Subject: Re: supporting multiple mobile device resolutions I think you have touched on why a single card/custom geometry solution can be inadequate at a certain point. I had suggested (although I do not myself know how to do it) that conceptually you could have

Re: supporting multiple mobile device resolutions

iMola > IT Director > Evergreen Information Services > rdim...@evergreeninfo.net > > > -Original Message- > From: use-livecode-boun...@lists.runrev.com > [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield > Sent: Monday, February 13, 2012 4:10 PM

RE: supporting multiple mobile device resolutions

4:10 PM To: How to use LiveCode Subject: Re: supporting multiple mobile device resolutions Thanks for all the responses everyone. It sounds like the consensus is to use a single stack with resizing/repositioning code in order to make it compatible with any device/resolution. Not what I want to do

RE: supporting multiple mobile device resolutions

...@evergreeninfo.net -Original Message- From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Monday, February 13, 2012 4:10 PM To: How to use LiveCode Subject: Re: supporting multiple mobile device resolutions Thanks for all the

Re: supporting multiple mobile device resolutions

Thanks for all the responses everyone. It sounds like the consensus is to use a single stack with resizing/repositioning code in order to make it compatible with any device/resolution. Not what I want to do, but probably worth it in the long term. Does anyone know if NativeGeometry is compatible

Re: supporting multiple mobile device resolutions

On 2/12/12 5:52 PM, Ralph DiMola wrote: Try # 2I created a handler to place and size control(s) based on the card size and relative to other controls. The routine is generic and is not app or layout specific. Every control moves and resizes as needed. Images maintain their aspect ratios. For

RE: supporting multiple mobile device resolutions

Chris, I was in your boat a few months ago. I thank all the folks for their advice back then. I am creating only Android and iOS apps. My goal was one card for all resolutions, aspect ratios and both orientations. After starting in epub land and making 2 layouts one for each orientation, one card

Re: supporting multiple mobile device resolutions

On Feb 11, 2012, at 6:01 PM, Ralph DiMola wrote: > I know this topic has come up before. About a year or so ago Tom McGrath > posted some very useful info. So now that some time has passed, I'm curious > as to how most of you are developing apps when you need to support multiple > device resolutio

RE: supporting multiple mobile device resolutions

Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode-boun...@lists.runrev.com [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Friday, February 10, 2012 4:32 PM To: How to use LiveCode Sub

Re: supporting multiple mobile device resolutions

Speaking of resolution support: Apple Now Requiring iPhone Developers to Submit Retina Screenshots -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworld

Re: supporting multiple mobile device resolutions

On 2/10/12 3:31 PM, Chris Sheffield wrote: What's the best method? Two separate stacks, one for each resolution? Or a single stack with code to handle positioning of controls? Definitely a single stack with resizing code. That will automatically adjust to whatever resolution happens to be rel