Sonki,
Windows CE (Compact Edition) is a subset version of Windows made to run in limited storage, such as in a handheld unit.
It is source compatible at the Applications Programming Interface level with Win32 interfaces.
Like Windows/NT, it is portable to various architectures. There are, in fact, a number of different microprocessors which are supporting it for handhelds.
There are also versions of Excel and Word that run on it. There are also a substantial number of other applications which have been ported to it. Since it supports the Win32 interfaces, the porting is relatively straightforward (if the application is not too large for the target machine); in many cases, only a recompile is necessary.
Windows CE handhelds are being implemented by many companies, and the handheld products look like they will be a success, i.e., after some additional features the market wants are added.
MSFT is also planning to make Windows CE available in all sorts of low-cost boxes. For example: the WebTV box, other set-top boxes, integrated into TVs, handhelds of all types, mobile PCs, mobile terminals, your car ... you name it. If it has a microprocessor and ROM (or other program storage) and some RAM (for working storage), and a human needs to interface with it, it is a candidate for Windows CE.
It is hardly limited, except by the program storage. It is modular, so that only those functions that are needed for a specific purpose need to be included. Note that, if a handheld is communicating over spread-spectrum communications (as per a previous post), it could page the program code as needed, should such be required (although I don't believe that function is currently provided).
Even the first generation of Windows CE handhelds are available with MSFT's Java Virtual Machine, plus various forms of communication (including wireless).
So, you have a good basis for propagating Windows Everywhere - just as promised.
The import of the Sept 29 push is this: the fact that there is a huge base of Windows applications (in particular Visual Basic) which could be recompiled to the new Universal Virtual Machine (which will presumably also be available at some point on Windows/95 and NT), allows MSFT to make the UVM the de facto standard for portable code (i.e., programs which the developer wishes to run on a variety of microprocessors without recompilation). [The UVM is presumably a superset of the JVM, also allowing access to all Windows APIs, as per other earlier posts.] In addition, since a variety of MSFT language processors will target this interpretive code, the environment will allow the developer to use existing programs, and/or code in the language which best suites the developer. This places Java in its proper place, as just another language to use for code development. So then it will be up to the 100% pure Java advocates to show why developers should deprive themselves of using existing code and MSFT language tools for this multi-language machine-independent Windows environment, so as to code afresh to the Java single-language, somewhat machine-independent, non-Windows environment.
I say, they'd better keep their ears (and/or other parts) well protected.
Best regards,
Arno
P.S. This was written quickly, so I hope I have not forgotten to mention a salient point or two. |
