.NET CF for Palm OS

  • Thread starter Thread starter Guest
  • Start date Start date
Charles Tam said:
Does anyone know whether .NET CF support Palm OS?

As a Google search would reveal, a lot of people knows the answer to that
one.
The answer is NO!

The Palm OS (at least the versions that I am aware of) is a single-threaded
environment, where a thing like .NET would have a hard time living. The
processor itself is also somewhat small and slow for a .NET implementation.
Admittedly, the Palm OS is great for what it does, but don't expect miracles
from it.

/Keld Laursen
 
Hi,

No.

However, AppForge (www.appforge.com) does provide a development add-in for
..NET for Palm development.

Also, SuperWaba (Java) is a very interesting open source tool for Pocket PC
and Palm development. It is more limited than .NET in a number of ways,
especially performance (it use a Java VM), but the IDE looks a lot like
..NET, and it seems to be a nice start.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.
 
Keld,

Your comments made for some interesting reading... but aren't entirely
accurate.

It is true that .NET is a multi-threaded language... as Java is, which has
been ported to Palm OS. Threading, although an issue, is not a 'do or die'
issue in moving .NET to the Palm. In regard to the processor - keep in mind
that [most] new Palm's ship with [nearly] the exact same processor that are
in Pocket PC's. Again, not a real issue.

Some of the real issues are: endianness, size of language, politics,
licensure, lack of needed underlying operating system calls, need to extend
Palm OS functionality, total cost of product, and lack of incentive to port
..NET.

I would even have to disagree with your view of what the Palm OS 'does well'
since application development for the Palm platform is terrible... most of
the tools are terrible... and the end products for even the most simple
application is entirely to complex.

Cheers,

Rick Winscot
www.zyche.com
 
Hi, Rick.

Well, I can only concur on most of your points.

I'm sorry that I were a bit wrong in my statement about being
single-threaded. What I ment to say that the Palm OS's I worked with all
were single-process OS's, which meant a heck of a hassle to do stuff like
FTP data transfer with your own program showing i the foreground. You either
put all the nitty-gritty details of FTP into some interrupt routine, or had
to program your own "threads" into your program.

And what I ment with "Admittedly, the Palm OS is great for what it does,..."
was that it did provide you with a nifty PIM, which could even do great
synchronisation with your desktop apps, which is something that I find all
too flaky on PocketPC's.

For programming, we did a little Satellite Forms "programming" and a few
lines of CodeWarrior C. I won't say that I loved the experience. Just too
many occations of bending over backwards to try to accomplish something
fairly simple.

Even the original Psion Organiser weren't quite that bad, programming-wise.
;)

/Keld Laursen
 
Keld,

Right on. Threads can be implemented in hardware or software... and I think
that just hearing that can make a developer ill. I suppose indirectly,
threading is an issue. Not so much that it can't be done... but that it
complicates simple processes.

I should admit... that I was a die hard palm user for some time. That is
until the company I was working for bought me a pocket pc. After doing a
couple projects with SQL CE and getting new units when they came out... I
was hooked. I haven't programmed much for the Palm since (code warrior) but
those AppForge tools sure got me curious!

Amen to the PIM comment...

Cheers,

Rick Winscot
www.zyche.com
 
Back
Top