Simulate different screen sizes with built-in Emulator

[GoogleCodeExporter]

Would love to be able to simulate different phone screen sizes with the built 
in emulator AI uses. Does not necessarily have to include every screen size 
available, but at least 3-4 of the most common.

Original issue reported on code.google.com by jonsap...@gmail.com on 17 Jun 2011 at 4:11

[GoogleCodeExporter]

It should be possible to do this already if you download the SDK and create an 
assortment of emulators at pre-set resultions and launch the required emulator 
first from the SDK, check its running from an adb devices command, then open 
the blocks editor and look for the emulator in the devices list.

One of the main issues with different screen resolutions it is that the 
component viewer bears no relationship to the layout you get on the device and 
lacks the ability to scroll a physically large layout.

Ive just posted a feature request for objects to be directly positionable at 
x/y co-ordinates from the properties list to help overcome this issue, though 
ultimately proper support for various screen sizes would be the ideal option.

Incidentally, here Ive been experimenting with setting up androidX86 in a 
Virtual machine enviro using VirtualBox (see screenshot). That is very easy to 
set at different screen resolutions and can be booted from a VM snapshot in 
about 10 seconds - much faster than the emulator :)   (the downside is 
complexity of setting up and CPU use)

I will do a full writeup eventually  :)

Original comment by chrisw.g...@gmail.com on 17 Jun 2011 at 1:37

Attachments:

• Screenshot-2.png

[GoogleCodeExporter]

I see.  Before I posted this I had thought AI used its own built-in emulator 
for some reason.  I guess this issue should be cancelled, I just can't figure 
out how to do it on my end :)

Original comment by jonsap...@gmail.com on 17 Jun 2011 at 5:50

[GoogleCodeExporter]

Yes AI does use its own emulator, but its the same one used for java 
development with eclipse - the Android SDK.

http://developer.android.com/sdk/installing.html gives you some pointers for 
installing and using the ADB.

There is a bit of a steep learning curve involved. It took me a few days of 
searching to work out  exactly what was needed.  Ive got to write up a howto 
for both the SDK and using the X86 version in VirtualBox shortly, so I will 
drop a link back to my blog site on here once its up and running.

Your feature request is certainly still valid however as the idea  behind AI is 
to make android development accessible to those who would not normally be using 
more complex development methods like the SDK and eclipse.  

Original comment by chrisw.g...@gmail.com on 17 Jun 2011 at 6:55

[GoogleCodeExporter]

True.  Or if AI must use the SDK emulators than maybe it can have the option of 
installing the various sized screens to the SDK automatically, and when in 
blocks editor if you click on emulator a dialog should pop up asking which 
screen size you would like to launch...

Original comment by jonsap...@gmail.com on 17 Jun 2011 at 11:19

[GoogleCodeExporter]

Original comment by weihuali...@gmail.com on 17 Mar 2012 at 1:59

• Changed state: Noted