Channels ▼
RSS

Web Development

Windows Mobile Components



Mike Riley is a Dr. Dobb's contributing editor. You can contact Mike at mike@mikeriley.com and follow him on Twitter @mriley.

Windows Mobile applications can encapsulate controls that accelerate the creation of user interface enhancements and programmatic functionality, turning development time from a matter of months to a matter of weeks -- or even less. For example, instead of spending time on programming a flexible grid display, a commercial component may already deliver the required capabilities. What's more, the drudgery of debugging such an enhancement is all but eliminated as a result of the vendor's commitment to the stable functionality of their hosted components. Enterprise developers already supporting a large customer base of Windows Mobile 5.0 users will especially appreciate the expansive platform of Windows Mobile editions that these controls can support.

Resco Mobile Forms Toolkit

Resco's Mobile Forms Toolkit, for instance, is a suite of 24 .NET Compact Framework controls ranging from audio playback and zip file manipulation to calendar, list, and tree UI components.

Figure 1: The Resco Mobile Forms Toolkit SmartGrid Designer Layout Tool

The controls I've found particularly useful and easy to implement in my development efforts are the SmartGrid for tabular data (its XML Template runtime design made this control particularly flexible), CustomKeyboard (for its slick skinning and key collection layout abilities), and DetailView (for its built-in error checking and XML Templated layout design support).

Figure 2: A Windows Mobile application demonstrating the Resco Audio for .NET CF control

Unlike some component publishers, Resco also develops commercial Windows Mobile applications. Consequently, its component suite reflects a developer-centric understanding of what effectively works in the Windows Mobile application construction process. The controls are polished, well-documented, and work effortlessly in the Visual Studio Windows Mobile emulation environment. They also are easily packaged and deployed with the target applications they are incorporated into. And they are very well designed, both graphically and programmatically. The Resco controls work well within the screen real estate boundaries that constrain many other UI components. The visual controls also support the higher VGA resolutions available on more recent Windows Mobile devices, giving developers even broader target device support.

Sapphire Suite

The Sapphire Suite from Sapphire Solutions is a collection of 10 DLL and .NET and Visual Studio 2005 and 2008 compatible components, several that dive deep into collecting device hardware data.

Figure 3: The Sapphire SIM control can read and write data to the phone's SIM card.

For example, the IrDA component allows applications to interact with infrared devices (assuming the Windows Mobile host is equipped with an IR port). The IMEI and SIM utilities provide access to the device's International Mobile Equipment Identifier (IEMI, Subscriber Information Module (SIM) details, and a battery utility that can be used to poll the device's battery charge level.

Figure 4: Sapphire's IrDA control can be used to transmit data to another IrDA-enabled device

Other components in the suite include a flexible Remote Access Server (RAS) control, encryption, email, FTP and GZip utilities, and a button utility that allows applications to closely monitor and change the state of on-screen button names and actions. Of all the controls I tested, the most compelling were the IrDA, SIM, and Mail components. Unfortunately, IR is becoming a less frequent hardware option in newer Windows Mobile consumer devices, so this control may have more limited appeal for developers with specific IR needs. The SIM control made it easy for me to create, modify, and delete contact data to my phone's SIM card, and the Mail component provided access to easily create mailboxes and send and receive email with attachments.

ComponentOne Studio Mobile

ComponentOne has created a suite of components specifically designed for the Windows Mobile platform. While not as comprehensive as its Windows desktop counterpart, the ComponentOne Studio Mobile suite consists of four useful components, two of which are mobile editions of their desktop components.

Figure 5: The ComponentOne FlexGrid control is one of the most option rich layout controls available to Windows Mobile developers.

The Chart component can render numerous chart types, from the standard line, bar, and pie types to radar and plots that can be stacked for greater visualization within the constrained screen real estate of a Windows Mobile device. The FlexGrid component offers a plethora of options from built-in sorting and highly customizable per-cell visual attributes (like background fills and images) to effortless calculations of sums, averages, etc. for a range of cells. FlexGrid also provides rapid, case-insensitive searches for cell contents, data binding to ADO.NET sources, and more. Even with all these features, the component is relatively lightweight so as not to add too much bulk to deployed applications using it.

Figure 6: The ComponentOne C1ChartCF for Mobile control can be used to create a wide variety of charts.

The MaskedTextBo and Zip controls are useful, but not as compelling compared to other suites. I was also a bit disappointed that there were only four controls in the suite. For the price (starting at $800 for the standard edition), when compared to competing suites and even the number of controls in ComponentOne's desktop edition, you'd expect the collection to be double in size. FlexGrid and Chart unquestionably carry the majority of this package's overall value proposition.

While the Windows Mobile platform enjoyed years of success, it's interface has not kept up with the times. Based on the Windows desktop paradigm, it's menu-driven UI makes interacting without a stylus a chore. While users eventually attain a modicum of proficiency, modern interfaces on the iPhone, Android, and Palm Pre platforms have reset user experience expectations. Until Microsoft delivers a modernized interface, developers may conclude that little can be done.

Touch Controls Suite 1.7

While the Windows Mobile platform enjoyed years of success, it’s interface has simply not kept up with the times. Based on the Windows desktop paradigm, it’s menu-driven user interface makes interacting without a stylus a chore. While users eventually attain a modicum of proficiency, modern interfaces on the iPhone, Android and Palm Pre platforms have reset the user experience expectation. Until Microsoft delivers a modernized interface, developers may conclude that little can be done.

Mirabyte saw this shortcoming as an opportunity and created a number of controls optimized for the effortless single touch operation found in Windows Mobile competitors. The latest 1.7 release includes nine .NET Compact Framework controls that convincingly emulate the modern fluid, finger-flicking UIs. The primary control is the TouchListBox that provides smooth scrolling list views and item selections so prevalent in Android and iPhone applications. The GlassDialog control replaces the bland Windows modal dialog boxes with a translucent frame that overlays the primary display. While the control doesn’t emulate Android or iPhone exactly (i.e., there is no blur effect underneath the frame), it’s a convincing and considerably more attractive view compared to the stock alternative.

Figure 7: Designing a Windows Mobile application using the TouchPanel control.

The TouchPictureBox attempts to provide an easier way to scroll over images but feels awkward in execution. This is not the fault of the control, but rather the single-touch limitation of the current Windows Mobile OS. The other components are mainly enlarged button, check, textbox, and title bar controls that make selecting manipulating these onscreen items far less frustrating compared to default Windows Mobile UI objects. Mirabyte has posted a YouTube video that show these controls in action.

Figure 8: Mirabyte's TouchPanel control in action.

Rebex Total Pack for .NET

One aspect of mobile computing that is not as glamorous as attractive user interfaces but more important is security. Secure data transfers ensure integrity, privacy, and trustworthiness. While security is taken seriously on the Windows Mobile platform, easily accessing the features programmatically are not trivial. However, managing various applications of the SSL protocol is no longer a challenge thanks to the Rebex Total Pack for .NET.

Figure 9: Designing a Secure FTP Windows Mobile application using the Rebex SFTP control

While primarily a secure library collection for desktop .NET applications, Rebex has included a counterpart of .NET CF 1.0, 2.0, and 3.5 FTP, FTP/SSL, SFTP, and Time components, and .NET CF 2.0 IMAP/SSL, POP3/SSL, SMTP/SSL, and S/MIME components. These controls turn the ardous task of ensuring secure email and file transfer communications into a quick and easy one.

Figure 10: The SFTP Get demo provides a head start for other Rebex-enabled secure data transfers

Rebex includes several demo applications showing how simple it is to create these secure applications, from an asynchronous SFTP client to a secure IMAP messaging application. I was pleasantly surprised at how quickly I was able to assemble a secure, custom Windows Mobile file transfer agent to copy images taken with my phone's camera to a Unix-hosted website with SSH/SFTP access..

Conclusion

Thanks to the mobile component model that Microsoft has designed, Windows Mobile developers have an advantage when it comes to rapid mobile application development. No other mobile device platform comes with the number of extensible commercial components that the Windows Mobile ecosystem has to offer. Using these controls is as easy as using their counterparts on the Windows desktop. As the Windows Mobile OS continues to mature, the catalog of mobile components will no doubt continue to expand to a broad range of encapsulated functionality that will give developers the tools they need to make their mobile applications successful.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Dr. Dobb's TV