Windows Mobile 2003 Second Edition for Smartphone - screens

[Guest Paul [MVP]]

Below are a few screen grabs from Second Edition Smartphone in standard resolution and the new QVGA (320x240) resolution.

What a difference it will make when devices start to appear, particularly to Pocket Internet Explorer!

P

[Guest smeg36]

The difference in PIE will be almost as big as when I got my e800! Any idea when a smartphone with a 320x240 screen is coming out?

[Guest Crispy]

Ok Orange, now you have a second chance of bringing a decent 2003 update to all the romhungry SPV/E100 users out here ...

Plz :cry:

Also, QVGA res looks neet :)

[Guest carvas]

it will be possible to upgrade my Qtek 8080 with WM2003 to the Second Edition?

Regards!

[Guest superkingdave]

looks good! whens the e300 out?

[Guest g4mb17]

For those who want to know these are screen shots from the "Ozone" beta emulator. my emulator file is dated 4/11/03, and the screen is the same. Although i've only had it installed since 26/2/04.

For those programmers out there:

Layout

UI elements whose positions and sizes are specified in pixel coordinates that assume 96-DPI will be incorrect on high-DPI devices. In general, all UI elements should be laid out using scaled positions and sizes, or relative to controls, fonts, or system metrics.

The GetDeviceCaps Windows CE function can be used to obtain a display’s DPI by passing in either LOGPIXELSX or LOGPIXELSY as the second parameter. The CrosswordSample sample demonstrates how you can define SCALEX and SCALEY macros to apply a scaling factor based on information from GetDeviceCaps.

You can continue to work in pixels but remove assumptions about the DPI by using the following techniques:

· Using the SCALEX and SCALEY macros or using GetSystemMetrics(SM_CXSCREEN) and GetSystemMetrics(SM_CYSCREEN) to scale 96-DPI pixel coordinates.

· Expressing sizes or positions relative to other controls.

· Expressing sizes or positions relative to a font.

Dialog boxes already use font sizes to determine their layout, so typically they need no special modification to work on high-DPI devices.

Following is an example of positioning a window with DPI-awareness, where x, y, dx, and dy are pixel coordinates in 96-DPI:

SetWindowPos(hwnd, NULL, SCALEX(x), SCALEY(y), SCALEX(dx), SCALEY(dy), SWP_NOZORDER);

If you choose to scale 96-DPI pixel metrics, be aware of rounding problems when using integers. For example, SCALEX(a + :) may not equal (SCALEX(a) + SCALEX(:lol:) because of rounding issues.

System Metrics

To be DPI-aware, an application can make no assumptions about the pixel sizes of various screen elements, such as icon sizes or border widths. Windows Mobile-based Smartphones and Pocket PCs provide a number of system metrics to provide information about the user’s system. For example, the following information can be queried via the GetSystemMetrics Windows CE function.

· Screen size dimensions should be obtained by using GetSystemMetrics(SM_CXSCREEN) or GetSystemMetrics(SM_CXSCREEN).

· Border dimensions should be obtained by using GetSystemMetrics(SM_CXBORDER) or GetSystemMetrics(SM_CYBORDER).

· Large and small icon sizes should be obtained by using GetSystemMetrics(SM_CXICON) or GetSystemMetrics(SM_CXSMICON).

riki

[Guest idavid]

wow! that resolution on a smartphone will kill of the pda market. cant wait. maybe the reason moto didnt release info on mpx220 is because theyve decided to put in a high res screen. :wink:

[Guest t3dluke]

I still think Smartphone and PDA will merge rather than one destroying the other. I'm not sure how much better PIE will look though, unless they actually increase the screen size like on the MPx. Think about an E200 with a 240x320 screen, the text would be unbelievably small!

[Guest idavid]

also i suppose you have to look at what you would pick given the choice of a pocket pc phone edition phone and a smartphone phone with the same sized screens and resolution. you could argue that the pocket pc version would eclipse the smartphone everytime and then maybe smartphone would disappear [shudders....]

[Guest orangewinger]

Looks as if the Mpx100 will in fact have a hires screen from what I've seen so far.

http://www.mobilegadgetnews.com/modules.ph...rticle&sid=1050

Also the new dev stuff including emulators is up on the microsoft site too.

To be able to use the higher resolutions your device needs to have that size screen, so all current Smartphones won't get a lot of advantages from 2003 SE even if anyone does release an upgrade.

Dave

[Guest [email protected]]

idavid: Right on! That's the assumption I live by.

t3dluke: I think it's more the sharpness, rather than size, that makes text readable. I've got the Sharp GX30 with that resolution and it's comfortable to read even the smallest fontsize.

[Guest Paul [MVP]]

The MPx100 will not feature the new higher resolution as far as i'm aware.

Also, pre-production models don't feature Second Edition.

P

Posted from my SmartPhone!

[Guest [email protected]]

Funny though, when you've got roughly twice the screen realestate, why not add more than one menu item to the start menu? Do they have to be numbered 1 through 0?

[Guest midnight]

malte, yes, cos you press the number as a shortcut rather than scrolling through, but, theres always the * and # keys :)

[Guest Pagemakers]

SE will feature QVGA (320x240) resolution. What is the current res?

[Guest orangewinger]

176 x 220

[Guest mattscholey]

Won't this turn our (already too big) SPV's into XDA sized bricks?

Matt

[Guest [email protected]]

mattscholey: The pictures are a little missleading. The screensize will most likely stay the same but have roughly twice the number of pixels. Smaller pixels.