Thursday, August 14, 2008

Which icon sizes should I use in my application?

We've covered icons in the past, but I thought it was a good idea to review this information because I often see applications that use incorrect icon sizes. At a high level, here are the icon sizes Windows Mobile developers need to be aware of:

Windows Mobile Professional and Classic devices (formerly known as "Pocket PC"):

  • Normal DPI: 16x16 (small) and 32x32 (large)
  • High DPI: 32x32 (small) and 64x64 (large)

Windows Mobile Standard devices (formerly known as "Smartphone"):

  • Normal DPI: 16x16 (small) and 32x32 (large)
  • High DPI: 22x22 (small) and 44x44 (large)

So which of these icons should you use and where?

Application icons:

Your application's main icon (the first one embedded inside your .exe) is used in various places such as File Explorer, Task Manager, Start menu shortcuts, 3rd party memory management utilities etc. Since you cannot predict or control whether the user will see this as a large or small icon, you should support the maximum number of sizes for this icon (i.e. both small and large formats).

If you are creating a single .exe that is designed to run on all Windows Mobile devices, use an application icon with these sizes:

  • 16x16
  • 22x22
  • 32x32
  • 44x44
  • 64x64

If your .exe is only designed for "Pocket PC" devices, use an application icon with these sizes:

  • 16x16
  • 32x32
  • 64x64

If your .exe is only designed for "Smartphone" devices, use an application icon with these sizes:

  • 16x16
  • 22x22
  • 32x32
  • 44x44

"Feature" icons:

These are icons used within your own application. As a developer you can control the appearance of common controls such as ListViews and TreeViews used within your application, and hence you can decide which icon formats are most appropriate. For example, if you use a ListView control with the LVS_ICON style, you will need a "large" icon. If you use the LVS_REPORT style instead, you will need a "small" icon. To create applications that look great across all Windows Mobile devices (regardless of "Pocket PC" or "Smartphone"), support all the necessary icon formats - but no more than you really need. For example, if I know that my ListView will only use the LVS_REPORT style, my icon only needs to support the "small" sizes (16x16, 22x22 and 32x32). Similarly if my ListView only uses the LVS_ICON style, I only need the "large" sizes (32x32, 44x44 and 64x64).

Bottomline, treat your application icon and feature icons differently. And strive to support all the icon sizes that are necessary across different types of Windows Mobile devices. I hope this post helps you improve the look and feel of your applications. Please post comments if you need more clarification around icon size issues.

-Mel Sampat (PM, Windows Mobile shell team)

MelSam Thu, 14 Aug 2008 20:38:19 GMT


Source: http://blogs.msdn.com/windowsmobile/archive/2008/08/14/which-icon-sizes-should-i-use-in-my-application.aspx
--
To unsubscribe from this feed, click here
To manage other subscriptions, click here
~
Powered by RssFwd, a service of Blue Sky Factory, Inc

Monday, August 4, 2008

Introducing the Windows Mobile API Usage Tool!

I'm really excited to announce the release of the Windows Mobile API Usage Tool, available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=fc803c7b-e855-475a-b8f3-38c19a007d36&displaylang=en

 The API Usage Tool scans your Windows Mobile applications (in cab, msi, or binary formats), performs static analysis, and reports on the usage of APIs and other system resources.  Our application compatibility team has been using the tool for several months now to ensure that we have good coverage of our public SDK when we do testing with 3rd party applications, as well as to help guide resource allocation and investments toward the most frequently used APIs.

 The tool includes a file-- deprecated.txt-- that has the current list of deprecated APIs for Windows Mobile, and will report on your application's usage of these APIs.  It's a really effective way to evaluate how your application will be affected once these deprecated APIs are removed from Windows Mobile.

 The tool is command-line based, and its output is a SQL Compact Edition database (.sdf file).  When used with the /deprecated option, the tool will also generate a collection of useful reports.

 We're hoping that developers find the tool and reports useful, and we're encouraging developers to send us a copy of their database (or a link to a copy for larger files) at wmaut@microsoft.com.  We'll aggregate the data and incorporate it into our application compatibility planning, and we'll also share findings with the community via this blog.

msaffitz Mon, 04 Aug 2008 00:28:00 GMT


Source: http://blogs.msdn.com/windowsmobile/archive/2008/08/04/introducing-the-windows-mobile-api-usage-tool.aspx
--
To unsubscribe from this feed, click here
To manage other subscriptions, click here
~
Powered by RssFwd, a service of Blue Sky Factory, Inc