Re: The Screen Density Conundrum

2012-07-31 Thread Pierre Sahores
My tough too ;) Le 31 juil. 2012 à 18:12, Bob Sneidar a écrit : > I have to think that the devs at RR have been mulling over how to address > this for the future. The problem will only get worse. It doesn't make sense > for them to leave this in the hands of the end developers to deal with. >

Re: The Screen Density Conundrum

2012-07-31 Thread Bob Sneidar
I have to think that the devs at RR have been mulling over how to address this for the future. The problem will only get worse. It doesn't make sense for them to leave this in the hands of the end developers to deal with. I think that a coordinate system that is independent of density or resolu

Re: The Screen Density Conundrum

2012-07-31 Thread Roger Eller
On Tue, Jul 31, 2012 at 3:26 AM, Monte Goulding wrote: (shortened to express my idea) > So we know the density we are running at and now we have the choice of the > following: > - scale things > - create multiple substacks > - same as above but using stackfiles > - creating multiple stack

Re: The Screen Density Conundrum

2012-07-31 Thread Alejandro Tejada
Ideally, we should be able to use scalable vectors for the Interface. Icons, backgrounds, Text... A vector graphics interface created with all the excellent capabilities of vector graphics in this platform, would be a real delight to watch... In a quick test of scaling polygons with a gradient f

Re: The Screen Density Conundrum

2012-07-31 Thread Monte Goulding
> If your 'main' stack was an external stack that was loaded at runtime, the > first time the app ran you could do a blanket resize (if necessary) of > objects and controls so that they at least matched the required pixel density > and device form factor (e.g. std phone, HD tablet) and then sav

Re: The Screen Density Conundrum

2012-07-31 Thread Terry Judd
On 31/07/2012, at 05:39 PM, Monte Goulding wrote: > I tend to agree. I can't help wondering if the first card could be scaled and > then kick off some non blocking process to do other cards. If your 'main' stack was an external stack that was loaded at runtime, the first time the app ran you c

Re: The Screen Density Conundrum

2012-07-31 Thread Ken Corey
I'll vote for scaling upon first load. We've forgotten something here. When we get away from being tied to pixels, we can give our users more choice. My 72 year old father will want the chrome of an application (as well as the content) visually much larger on the screen (pixel density and sc

Re: The Screen Density Conundrum

2012-07-31 Thread Monte Goulding
I tend to agree. I can't help wondering if the first card could be scaled and then kick off some non blocking process to do other cards. -- M E R Goulding Software development services mergExt - There's an external for that! On 31/07/2012, at 5:30 PM, Chipp Walters wrote: > I vote for scale o

Re: The Screen Density Conundrum

2012-07-31 Thread Chipp Walters
I vote for scale on launch. Just too much work building multiple interfaces for each screensize. The tool should allow for "setting" the control size and position based on density and/or pixel resolution. -- Chipp Walters CEO, Altuit, Inc. ___ use-liv