Page 1 of 2

WinCE Programming

PostPosted: Oct 16, 2002 @ 11:24pm
by Cue
Hello all,

Im interested in programming for WinCE. I would also like to get involved with it while writing my final year project.

I had a look at J2ME and PJava, thinking that it should be quite popular, but the Sun site was poorly documented and the forum was dead really.

Is MVT & MFC the most common approach for WinCE Programming?

Any feedback much appreciated.

PostPosted: Oct 17, 2002 @ 6:09am
by Jadam

PostPosted: Oct 17, 2002 @ 3:41pm
by Dan East

PostPosted: Oct 18, 2002 @ 11:17pm
by Guest

PostPosted: Oct 18, 2002 @ 11:22pm
by Cue

PostPosted: Oct 19, 2002 @ 12:02am
by refractor
The best thing to do with Java programming on the PocketPC is "forget it", IMHO. I don't think that there's a widely available JavaVM for the PocketPC (happy to be proved wrong though). Things should take off when the chips with the Java capability come along (like ARM's Jazelle technology).

PostPosted: Oct 22, 2002 @ 2:45am
by Cue

PostPosted: Oct 22, 2002 @ 9:49am
by refractor

PostPosted: Oct 22, 2002 @ 4:01pm
by Cue
:\
and i really dont want to go back to VB...

Ive been programming in JAVA for the last year, and i would like to continue on that.

I dont like changing from one language to another, especially since im a beginner.
:\

...
However if JAVA does prove limited, i guess i have no other option. Although, as i said, its not going to be a heavy application.

PostPosted: Oct 22, 2002 @ 4:19pm
by James S

PostPosted: Oct 22, 2002 @ 4:19pm
by angedelamort

PostPosted: Oct 22, 2002 @ 4:37pm
by refractor

PostPosted: Oct 22, 2002 @ 5:30pm
by James S

PostPosted: Oct 22, 2002 @ 6:02pm
by refractor
Well, so far as I understand it, all of the "managed" languages in .NET (i.e. everything except the "unmanaged" C++, IIRC) are compiled into an intermediary language and thrown into an interpreter (or compiled natively - I can't remember which - it might even be both depending on configuration). The "managed" stuff uses garbage collection, just like Java.

That means that because C#, Managed C++, VB, ASP can all be expressed as the intermediary language, they can all fit together easily; I can write one object in C++, one in VB, one in ASP, and use one from the other with the objects' defined interfaces without even knowing what language they were written in. Unmanaged C++ can be wrapped and used, as a COM+ object, if memory serves.

It should mean that we (talking about my day job here) can create the back end as either managed or unmanaged C++ (it'll depend on how desperate we are for speed and how well the managed stuff performs), knock up a front-end in VB and link the two together almost seamlessly.

I'll tell you if it works out to be as easy as that in a few months ;) I've only been playing with .NET fro a week or so, but I quite like it already (though I've been doing VB, and the "managed C++" is a bit of a culture shock from vanilla C++ I hear).

Cheers,

Ref.

PostPosted: Oct 22, 2002 @ 8:56pm
by Cue