Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

.NET

Windows CE Win32 API Programming


Windows CE 1.0 versus Windows CE 2.0

Dr. Dobb's Journal April 1998

Windows CE 1.0 versus Windows CE 2.0


The major differences between Windows CE 1.0 and Windows 2.0 include the following:

  • Version 1.0 only supported raster fonts. Version 2.0 supports TrueType fonts.
  • Version 1.0 did not support any of the OLE Win32 API functions (CoInitializeEx, for instance). Version 2.0 supports the OLE API. The Visual C++ Toolkit for CE will also include the Active Template Library for OLE development.
  • Printing is also new for Version 2.0. However, there is no print manager and there is no spooling of print jobs. Hence, only one application can print at a time. Also, multiple print jobs are not allowed.
  • Version 1.0 only supports 2 bpp color. Version 2.0 supports 1, 2, 4, 8, 16, 24, and 32 bpp. This covers the same range of support as the other Win32 platforms.
  • Custom palettes are supported in 2.0.
  • Support for Java has been announced, although the details remain elusive.

The CE Embedded Toolkit

The CE Embedded Toolkit for Visual C++ 5.0 has been announced to enable embedded developers to customize the CE kernel. This enables a specialized version of CE using a minimum set of software modules to support the platform's requirements (in order to minimize the memory footprint and maximize performance of the operating system).

For example, you could build a version of the OS that contains the kernel and a selected set of communications modules but which does not provide a graphical user interface. In addition, Visual Basic 5.0 and Visual J++ have add-on packages to support CE as one of their target platforms. A Visual Basic run-time interpreter and Java virtual machine are part of these add-on packages.

-- B.R.


Copyright © 1998, Dr. Dobb's Journal


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.