Windows Phone Thoughts - Daily News, Views, Rants and Raves

Check out the hottest Windows Mobile devices at our Expansys store!


Digital Home Thoughts

Loading feed...

Laptop Thoughts

Loading feed...

Android Thoughts

Loading feed...




Go Back   Thoughts Media Forums > WINDOWS PHONE THOUGHTS > Windows Phone Talk

Reply
 
Thread Tools Display Modes
  #1  
Old 02-18-2003, 05:30 PM
Jason Dunn
Executive Editor
Jason Dunn's Avatar
Join Date: Aug 2006
Posts: 29,160
Default Pocket PC Screen Resolution

There are some very interesting discussions going on in response to Andy's post, but I wanted to bring the issue of Pocket PC screen resolution front and center and have a discussion about it. One user comment seemed to be typical of most I've seen on this issue:

"There MUST NOT be a fixed screen size/orientation with the next PocketPC OS! Windows CE is written to handle any screen size, and with v4 handles on the fly screen size/orientation changes. Why remove such a large portion of Windows CE functionality for PocketPC users?"

It's not as simple as flipping a switch, having the resolution double and everything working as nicely as before. I know that Windows CE .Net supports different resolutions, including landscape mode, but unless I'm mistaken, it's not a truly resolution-independent OS. That's the real key: in a resolution independent OS, when you change the resolution, every other piece of the user interface will dynamically change as well. That's not what we have, so let's talk about what we do have.

The Reality
Let's say you double the Pocket PC resolution from 320x240 to 640x480 - you'd think that would be a very simple switch to make right? It might be, but unless you were to adjust the font size upwards, text at 640x480 would be too small for many people (just imagine the entire UI on your device with everything 50% smaller - text, icons, etc.). This pain would exist on a pure Windows CE .Net device as well - you can bet that any OEM deploying Windows CE .Net devices will lock down the resolution or perhaps pick one alternative resolution and do the work to make it look good.

Have you ever tried to adjust the system font size on a Pocket PC using a registry hacker, either up or down? It's just as nasty as it is on the desktop - dialogue boxes and menus get ugly (overflowing/underflowing text), and the UI simply breaks. It's no longer a good user experience. I loved having a smaller text size for cramming more info on the screen at once, but I cringed every time a dialogue box (say, an appointment) popped up - it was so ugly! It's not something I'd want to show other people as an example of what the Pocket PC OS looks like. Now throw multi-lingual support in there - did you know any dialogue box written in German requires about 30% more text? And what about landscape mode? That's a whole new set of factors.

And let's think about performance for a second. At 320x240 the OS is tossing around 76,800 pixels. At 640x480 that number quadruples to 307,200 pixels. I already seen too much sluggishness with screen redraws right now - and you want to take the same hardware and try to hurl 400% more pixels down the pipe? Let's say the next generation of hardware with the Intel PXA255 is up to the task for 2D tasks - what about games? How many engines can dish up 300% more pixels and still give acceptable performance? Remember these developers put a lot of work into having a great user experience at 320x240.

The Real Issue
The real root problem is that Microsoft didn't create the Pocket PC OS (or Windows XP for that matter) to be truly resolution independent - most of it is hard-coded for a fixed resolution (or several resolutions). On the desktop you can go into advanced display settings to adjust the screen DPI upwards to make everything bigger, but we don't have that option on a Pocket PC. It helps on those 15" screen laptops that are native at 1600 x 1200 resolution, but it's an ugly kludge that defeats the purpose of running at the higher resolution.

Platform unification is critical to getting developers on board - just ask any developer who's trying to code J2ME games how frustrating it is that every phone has a different resolution. It's very difficult to get the same experience across multiple resolutions - you need a lot of overhead code to compensate for all the variables. Microsoft cares more about the platform than any single piece - which is the same reason why they haven't created an "XScale version" of their OS.

Where We Go From Here
The bottom line is that Microsoft wants to see this happen - we heard this from several people during the MVP Summit. They don't like seeing Sony devices trump the Pocket PC in resolution any more than we do, but they need to do a lot of work to make it happen in the right way. And that takes time...more time than most of us are willing to wait for, but I'd much rather see Microsoft do this from a low level and have it work the way it should.
 
Reply With Quote
  #2  
Old 02-18-2003, 05:48 PM
Foo Fighter
Pontificator
Foo Fighter's Avatar
Join Date: Jul 2003
Posts: 1,466
Send a message via MSN to Foo Fighter

I'm not so sure that locking the PPC UI down to 320x240 is such a calamity. By limiting this spec, developers have a standard base from which to develop. Right now the PalmOS development environment is become horribly fragmented; 106x160, 320x320, 320x240, 320x480....it's a mess. And there is a trade off with higher resolutions; improved image quality/sharpness at the price of power consumption. Sony's NX series offers dismal battery life, thanks largely in part by that big beautiful screen. Then there is the text viewing experience. Have you seen hi-res text on the Tungsten T and Sony models? It appears microscopic in size.

So take heed, higher res isn't always a pixel utopia.
__________________
Kent Pribbernow
Elitist Snob, Contributing writer for Wired's Cult of Mac
 
Reply With Quote
  #3  
Old 02-18-2003, 05:59 PM
dgallina
Neophyte
Join Date: Feb 2003
Posts: 2

Unless the GUI becomes vector-based and Microsoft adds a user-accessible font DPI adjustment the multple-resolution problem will remain.

The short-term solution is relatively simple IMHO:

Pick a new standard resolution and re-do the GUI artwork and fonts (DPI) for that new resolution.

One high-resolution portrait and another high-resolution landscape mode would be sufficient for me personally.

LCD panels look much better at their native resolutions anyways, so why bother pixel halving / doubling / scaling to other crappy-looking resolutions in the first place?

Diego
 
Reply With Quote
  #4  
Old 02-18-2003, 06:04 PM
hrianto
Pupil
Join Date: Mar 2002
Posts: 24

Quote:
Jason:
Where We Go From Here
The bottom line is that Microsoft wants to see this happen - we heard this from several people during the MVP Summit. They don't like seeing Sony devices trump the Pocket PC in resolution any more than we do, but they need to do a lot of work to make it happen in the right way. And that takes time...more time than most of us are willing to wait for, but I'd much rather see Microsoft do this from a low level and have it work the way it should.

In the mean time for those who CAN NOT WAIT.... feel free to experience the PALM devices. :twisted:
 
Reply With Quote
  #5  
Old 02-18-2003, 06:06 PM
Foo Fighter
Pontificator
Foo Fighter's Avatar
Join Date: Jul 2003
Posts: 1,466
Send a message via MSN to Foo Fighter

I doubt a vector based a GUI is even possible on a mobile device. If MacOS X is any indication, a vector based composition engine requires a lot of horsepower which current mobile chips just don't have. And the memory requirement would be outrageous.
__________________
Kent Pribbernow
Elitist Snob, Contributing writer for Wired's Cult of Mac
 
Reply With Quote
  #6  
Old 02-18-2003, 06:16 PM
suhit
Ponderer
Join Date: Jul 2003
Posts: 95
Default SVG

Umm, what about SVG? It is a W3C standard, and there are some good screenshots available at PocketSVG.

I don't know about the memory requirements but it certainly is possible.
 
Reply With Quote
  #7  
Old 02-18-2003, 06:21 PM
Paragon
Magi
Join Date: Sep 2005
Posts: 2,341

I have one question......Why is 320x240 such a bad thing?

Dave
 
Reply With Quote
  #8  
Old 02-18-2003, 06:21 PM
Foo Fighter
Pontificator
Foo Fighter's Avatar
Join Date: Jul 2003
Posts: 1,466
Send a message via MSN to Foo Fighter
Default Re: SVG

Quote:
Originally Posted by suhit
Umm, what about SVG? It is a W3C standard, and there are some good screenshots available at PocketSVG.

I don't know about the memory requirements but it certainly is possible.
Not the same thing, suhit. SVG is for vector based graphics/presentation application. This is a FAR cry from a Vector composition engine layer built into an operating system. Too much caching and drawing going on. Sure you can display vector graphics on a PDA...Macromedia has already done this with its mobile Flash player.
 
Reply With Quote
  #9  
Old 02-18-2003, 06:26 PM
Foo Fighter
Pontificator
Foo Fighter's Avatar
Join Date: Jul 2003
Posts: 1,466
Send a message via MSN to Foo Fighter

Quote:
Originally Posted by Paragon
I have one question......Why is 320x240 such a bad thing?
You wouldn't be asking that question if you had looked at the Clie NX70. :lol:
__________________
Kent Pribbernow
Elitist Snob, Contributing writer for Wired's Cult of Mac
 
Reply With Quote
  #10  
Old 02-18-2003, 06:32 PM
Paragon
Magi
Join Date: Sep 2005
Posts: 2,341

Quote:
Originally Posted by Foo Fighter
Quote:
Originally Posted by Paragon
I have one question......Why is 320x240 such a bad thing?
You wouldn't be asking that question if you had looked at the Clie NX70. :lol:


Yes but most of the applications I bought 3 years ago for my 3600 Ipaq still work on my Dell. It's a handheld computer, not a high resolution media editor. For me I see pretty much what I want on it at a quality level I find exceptable. I would only want to see that improve if I did NOT have to give up anything to get there.

Dave
 
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 09:48 PM.