Windows CE Development
-
I haven't done any serious CE for a while. .NET will be ported to the devices - eventually - and there is also eMbedded XP coming out. No idea what subset (if any) of GDI+ will make it, but GDI itself is crippled in CE. CE3.0 has a browser (pocket IE) and CE 2002 is (I think) going to have a IE5.5 included, so you may be able to grab an XML interface somewhere. OR just grab one of the many XML parsers here (see www.codeproject.com/soap) Working with CE is an exercise in sifting through the docs. You pick up a bit here, and a bit there, and eventually you have enough to realise that you need more docs ;) cheers, Chris Maunder (CodeProject)
-
You should take a look at the forums at http://www.pocketprojects.com/site/ I have done a lot of development for the Pocket PC (and older versions of CE) but I have never used COM with CE... What level is the IE browser at At the Pocket PC? Version 4.0. I don't think GDI+ is supported, on the Pocket PC you use GAPI (Game API) for fast graphics. - Anders Money talks, but all mine ever says is "Goodbye!"
-
Thanks Chris for the info. Just out of interest how much of GDI is crippled?, the applications I'm porting relies heavily on GDI calls.
Just out of interest how much of GDI is crippled? Personally I have not noticed that GDI is crippled... There's a lot of old functions, which is included in Windows for backward compatibility, that's not supported. You can only use the newest functions, but I have not missed anything. - Anders Money talks, but all mine ever says is "Goodbye!"
-
I don't know whether you can use #import or not, but I guess that many of the XML parser classes here on CP is working under CE. I have spent most of my time, with CE, doing GDI stuff using plain API calls, so I guess I'm not the right person to talk about COM and XML under CE... - Anders Money talks, but all mine ever says is "Goodbye!"
-
I don't know whether you can use #import or not, but I guess that many of the XML parser classes here on CP is working under CE. I have spent most of my time, with CE, doing GDI stuff using plain API calls, so I guess I'm not the right person to talk about COM and XML under CE... - Anders Money talks, but all mine ever says is "Goodbye!"
-
Anders With the Embedded Tools 3.0 how do whats the target CPU for a HP Jordana 720 - (SA-1110 206 MHz Intel) Cheers Norm
To compile for Jornada 720 you first need to download the HPC 2000 SDK After you install the SDK you need to reboot to use it, the installer just forgets to tell you that... The Jornada uses an Intel ARM/StrongArm CPU, just compile for that, and the HPC 2000 platform, then it should work. :) - Anders Money talks, but all mine ever says is "Goodbye!"
-
Anders With the Embedded Tools 3.0 how do whats the target CPU for a HP Jordana 720 - (SA-1110 206 MHz Intel) Cheers Norm
Its the ARM Target. Intel have a licensing deal with ARM to market the chip. John
-
Its the ARM Target. Intel have a licensing deal with ARM to market the chip. John
Intel have a licensing deal with ARM to market the ship AFAIK Intel owns ARM... - Anders Money talks, but all mine ever says is "Goodbye!"
-
I don't know if this is the *right* place to put this, so before you guys go a flaming me... sorry! :-O I'm about to embark on Windows CE development (porting a application). I loaded MS Embedded Tools and *tried* the first compilation - without succes. There seems to be things like IUknownPtr missing declaration so I typedef typedef CComPtr IUnknownPtr etc, etc. #import also throws some wierd stuff Questions ~~~~~~~~~ How much of Native Com extensions are supported in Windows CE platform? Is XML supported? Is GDI+ Supported? What level is the IE browser at and can you import the type lib using the browser control in my WCE app. Also is there a good place to find Windows CE development information. Thanks In Advance. :cool:Norm Almond:cool:
Well, the problem with COM is that nobody includes DCOM in their Windows CE OSes (which becomes very apparent when you compile or link). Thus, only INPROC servers are support. That includes normal COM and Automation. However, if you can handle just having INPROC servers, then most all of COM is supported. (But remember you will probably be working with older versions of some toolkits. In many platforms some of the advanced ATL features are missing.) Also, WCE only supports multithreaded appartments. I have been able to port WTL to WCE without much problem. Tim Smith Descartes Systems Sciences, Inc.
-
Thanks Chris for the info. Just out of interest how much of GDI is crippled?, the applications I'm porting relies heavily on GDI calls.
Brush and pen support isn't all there (you only get a subset), and there are no DIBs, so you must use DDBs or DIBSections (hence the reason I wrote my DIBSection class!) I've also found some weirdness with WM_PAINT and WM_ERASEBKGND messages. I often had backgrounds simply not being drawn properly, so I had to add extra refresh calls. Oh - and owner drawn controls? Forget it! (at least in CE 2.11-). Also, there is no printing in early versions of CE. ooh-oooh! And mouse handling is also a little different - mainly because there is no mouse. cheers, Chris Maunder (CodeProject)
-
Brush and pen support isn't all there (you only get a subset), and there are no DIBs, so you must use DDBs or DIBSections (hence the reason I wrote my DIBSection class!) I've also found some weirdness with WM_PAINT and WM_ERASEBKGND messages. I often had backgrounds simply not being drawn properly, so I had to add extra refresh calls. Oh - and owner drawn controls? Forget it! (at least in CE 2.11-). Also, there is no printing in early versions of CE. ooh-oooh! And mouse handling is also a little different - mainly because there is no mouse. cheers, Chris Maunder (CodeProject)
But apart from that. What has CE ever done for us ? ;) Appologies to Monty Python
-
Brush and pen support isn't all there (you only get a subset), and there are no DIBs, so you must use DDBs or DIBSections (hence the reason I wrote my DIBSection class!) I've also found some weirdness with WM_PAINT and WM_ERASEBKGND messages. I often had backgrounds simply not being drawn properly, so I had to add extra refresh calls. Oh - and owner drawn controls? Forget it! (at least in CE 2.11-). Also, there is no printing in early versions of CE. ooh-oooh! And mouse handling is also a little different - mainly because there is no mouse. cheers, Chris Maunder (CodeProject)
ooh-oooh! And mouse handling is also a little different - mainly because there is no mouse. Yea, that's really one of the more funny things with CE :) Except if you make programs for HP Jornada 820, there *is* a mouse. Ohhh, it's never easy to be a programmer... :-D - Anders Money talks, but all mine ever says is "Goodbye!"