PalmSource Releases Developer Suite v1.1 & Installer

PalmSource has just released the Palm OS Developer Suite v1.1. The PODS suite is designed to enable the development of next generation multimedia and wireless applications for ARM- and 68K-based Palm Powered devices. The new release includes support for Palm OS Cobalt 6.1 creating PalmSource Installer packages and eclipse updates.

This release of Palm OS Developer Suite includes the following new features:

The upgrade of the underlying Eclipse platform onto Eclipse 3.0.1 and CDT 2.0.2 brings significant improvements and enhancements in the core functionality of the IDE. Registered Palm OS developers can also download Palm OS Developer Suite 1.0 free of charge from the Developer Zone on PalmSource.com. You should completely uninstall previous versions of the Palm OS Developer Suite before installing this new version.

The new Palm OS Developer Suite includes an open-source Integrated Development Environment (IDE) based on Eclipse, originally developed by IBM. Eclipse is a commercial-quality, best-in-class IDE with several hundred plug-in tools that support major software languages including C, C++, Java, and COBOL. The introduction of Palm OS Developer Suite enables developers to create mobile applications that run natively on ARM-based smartphones and mobile devices running Palm OS Cobalt.

Although 68K applications have the advantage of running on a wide variety of Palm Powered devices, only Palm OS Protein applications-ARM-native applications written using the new Palm OS Protein APIs-can take advantage of the many new features introduced in Palm OS Cobalt. Palm OS Developer Suite is currently the only free toolchain available for the development of ARM-native, Palm OS Protein applications.

"Palm OS Developer Suite represents PalmSource's commitment to the 300,000-plus registered developers to provide best-in-class tools to create next-generation wireless applications for ARM-based Palm Powered smartphones and wireless mobile devices," said Larry Berkin, director of developer marketing at PalmSource. "We believe that the suite simplifies the development process and allows for the creation of native applications that leverage the more than 100 new APIs in the new Palm OS Cobalt SDK."

PalmSource Installer is designed to allow developers to bundle their Palm OS software application, support files and desktop components into a single, compressed software package that a user can download and install with a single touch of a button, whether via a HotSync™ connection to the PC or while on the go, via OTA delivery. PalmSource Installer is automatically downloaded whenever an end user downloads a PalmSource Installer enabled application package. In addition, PalmSource Installer is designed to leverage the ease-of-use of Palm Powered smart mobile devices to intelligently detect a user’s device requirements, including memory, screen resolution and default languages to automatically install the appropriate files tailored to the device. The software applications optimized for online and OTA delivery to Palm Powered mobile devices draw from the more than 20,000 Palm OS software titles available today.

Thanks to Ben Combee for the tip.

Article Comments

 (55 comments)

The following comments are owned by whoever posted them. PalmInfocenter is not responsible for them in any way.
Please Login or register here to add your comments.

Comments Closed Comments Closed
This article is no longer accepting new comments.

Down View Full Comment Thread

Great! Now we just need the Mac OS X version.

pmjoe @ 11/29/2004 9:33:08 PM #
Then we can get some real development work done.
RE: Great! Now we just need the Mac OS X version.
pmjoe @ 11/29/2004 10:52:22 PM #
Oh, and some OS 6.1 devices to test on.
RE: Great! Now we just need the Mac OS X version.
Calroth @ 11/29/2004 11:18:36 PM #
Therein lies the problem. A Mac OS X version of the Palm OS Simulator will require true emulation code (the Windows version uses the existing CPU, which is easier).
RE: Great! Now we just need the Mac OS X version.
bcombee @ 11/30/2004 12:30:17 AM #
We are working on the Mac OS X port for sometime in 2005. A lot of this effort depends on how quickly the Mac OS X version of the Eclipse C/C++ Development Tools stabilizes. The Palm OS Simulators aren't going to be rebuilt for Mac OS X, however, so you'll have to debug to a real device, the Palm OS Emulator (68K), or across the network to a Win32 box running a version of the Palm OS simulator.

--
Ben Combee
http://palmos.combee.net - PDA programmer weblog
RE: Great! Now we just need the Mac OS X version.
CarlJ @ 11/30/2004 1:45:36 PM #
>>> A Mac OS X version of the Palm OS Simulator will require true emulation code (the Windows version uses the existing CPU, which is easier).

Uh, what? One of us is confused, and I'm not sure which. Since when does a Windows machine have either a 68k or a ARM-based CPU at its disposal? The CPU emulation ought to be a simple recompile; the GUI front-end, on the other hand, would be considerable effort to port.

RE: Great! Now we just need the Mac OS X version.
hotpaw4 @ 11/30/2004 3:38:51 PM #
> Since when does a Windows machine have either a 68k or a ARM-based CPU at its disposal?

Both OS6 and the simulator include a 68k CPU emulator. But the simulator simulates a fictitious x86/ia32 native CPU PalmOS device, rather than ARM-based hardware. This at least matches the endianess of the host CPU (little), which means that OS data structure access doesn't need to be emulated. This can't be done with a Mac/PPC/G5 since it's big-endian.

RE: Great! Now we just need the Mac OS X version.
grg @ 11/30/2004 8:03:02 PM #
Well ARM V6 has switchable little and big-endian modes (mixed-endian support) that enables developers to handle bi-endian systems seamlessly but most PDA manufacturers work with V5 (XScale) or even V5. Since Palm made the (compulsory ?) decision to sleep with the enemy it might be too late to consider another change.
Nevertheless, at least could we have an ARM Palm OS Emulator ? And how about a Linux version of the Developer suite ? Unless PalmSource believes Cygwin is better than the real thing.


T5 Wifi Drivers Released

Gekko @ 11/29/2004 10:39:00 PM #

Wi-Fi® Card by palmOne™ installer:
You must be installing on either a Tungsten T3, Tungsten T5, or a Zire 72. The Wi-Fi Card does not support other handhelds.

http://www.palmone.com/us/support/downloads/wifi_card.html



RE: T5 Wifi Drivers Released
hkklife @ 11/30/2004 12:18:00 AM #
Also new PhoneLink updater software. Many more GSM phones & carriers supported. I wish they'd go ahead and start listing CDMA providers & their equipment (Verizon & V710, Sprint & Treo 650)!

P1's been busy cranking out the patches and updates lately. At least you can give 'em that!

RE: T5 Wifi Drivers Released
Foo Fighter @ 11/30/2004 12:45:59 AM #
Whoopee! A $130 WiFi SD card combined with the $400 T5, for a total value of "just" $530. What an incredible bargain! Especially when compared to the far less expensive HP model that features both Bluetooth and WiFi for under $350. How does PalmOne do it? I wish this comment system had emoticons so I could place a giant rolleyes in my post! =8^)

-------------------------------
Editor, http://Pocketfactory.com
Contributing Editor, http://digitalmediathoughts.com
RE: T5 Wifi Drivers Released
mikecane @ 11/30/2004 8:03:08 AM #
How ironic that *Gekko* posts this news, especially after raking me over the coals for mentioning it'd be seen in beta recently!

I'm sure he's now waiting to pounce on all the bug reports...

RE: T5 Wifi Drivers Released
hkklife @ 11/30/2004 1:48:51 PM #
Mike;

Totally OT but weren't you nearly done with your T|E user review like a month or two ago? I was looking forward to that one. Are you still planning on submitting that one to Ryan? I actually have some time now for another review or two but there's....simply nothing compelling on the market Tungsten-wise to talk about short of re-flogging the T5 pig.

RE: T5 Wifi Drivers Released
mikecane @ 12/1/2004 6:00:48 PM #
It's coming, it's coming... (read that as bored, not excited).

Lack of devices = lack of development?

just_little_me @ 11/30/2004 1:09:25 AM #
This new release of PODS is great and all... but it's interesting to note that the Protein Developer Forum has had about a half-dozen postings *all* month... that includes a post about PODS 1.1... are developers getting tired of waiting too...?

I'll buy the first Cobalt device in a heart-beat, and would never go back to PPC... but I'm an atypical consumer...!

Other licensees are still doing cool things apart from palmOne though... I just received a pre-release device from another licensee and it rocks...! Sorry, can't mention any more yet! :)


JLM.

RE: Lack of devices = lack of development?
ardiri @ 11/30/2004 1:58:14 AM #
even with new devices that run cobalt; it doesn't mean developers need to start using the functionality of cobalt.

cobalt will run all OS5 based applications; so, as a developer, only if you need to use the new functionality of cobalt; you wont need even get involved with the new set of API's :) most of the features implemented; some developers have ended up writing themselves over the years..

---
Aaron Ardiri
PalmOS Certified Developer
aaron_ardiri@mobilewizardry.com
http://www.mobilewizardry.com/members/aaron_ardiri.php

RE: Lack of devices = lack of development?
bcombee @ 11/30/2004 2:52:28 AM #
We are aware of this; belive me, PalmSource would like devices that run Palm OS Cobalt to be on the market as soon as possible. However, you have to understand that the Palm OS deployment model is a bit different from that of other OS vendors. Since we support a diversity of hardware, there can be a bit of lag between when we finish a release of the OS and provide it to our licensees and when they complete their customizations for their particular hardware platforms. Our licensees also have tended to bundle a number of third-party applications, and those take time to customize for the new devices and OS releases as well. Now, with an emphasis on smartphones, you also have the lagtime of operator certification.

It's a long process, but it helps ensure that Palm OS devices take full advantage of their hardware and provide lots of functionality out of the box with a high level of usability.

Aaron is correct; unless you have a specific opportunity around Palm OS Cobalt, it's probably not time to port your applications to the Protein API. However, it is time to verify that your 68K applications work well in the Palm OS Cobalt simulators, and it is time to start thinking about what kinds of architectural changes would be appropriate when moving to the new OS.

--
Ben Combee
http://palmos.combee.net - PDA programmer weblog

RE: Lack of devices = lack of development?
mikecane @ 11/30/2004 9:06:49 AM #
>>>I just received a pre-release device from another licensee and it rocks...! Sorry, can't mention any more yet! :)

Well, bloody hell. Throw us a bone at least. Can you say if it's a *PDA* or (I have NO interest in this -->) smartphone?

I mean, the T3 is being closed out at Staples... and if there's something better to *wait* for, I'll wait.

RE: Lack of devices = lack of development?
pmjoe @ 11/30/2004 10:02:27 AM #
> are developers getting tired of waiting too...?

I think at least for the independent/hobbyist developers, the answer to this is yes. At least from personal experience, Palm has been off the radar for at least a couple years now. I've mostly been doing stuff with the Sharp Zaurus lately, because Palm is just so far behind in having a fun device for developers. Now with Sharp gone from the market, I've even more eager to get back to Palm OS.

From someone with a software techinical perspective, Palm OS 5 is a lame duck OS. It is a go between, just like OS 9 was for Mac, and I suppose Windows ME was like for Windows. It's fine for users if it gets the job done for them, but if I'm doing this for my own personal experience and fun, why would I consider consider a device that isn't the latest and greatest. It doesn't help that PalmOne now seems to have a track record of not providing OS updates. If I could buy a T5 today and know that I could get 6.x for it in the future, it would be a lot easier to do.

The hardware is also the other side of the letdown. I mean various Pocket PC companies have devices with both Bluetooth and WiFi built-in for reasonable prices. There isn't one Palm device with this, even for an unreasonable price (and there's no way I'm using external wireless cards again). The other half of the reason I bailed on the Zaurus was because Sharp refused to sell a dual Bluetooth/WiFi built-in Zaurus in the US. I have a very nice iPaq sitting on my desk which I'm not using with all the bells and whistles that I got for free from work. That said, the temptation to start working on it is growing day by day.

On a final note, Palm is so far behind in supporting Java (not that MIDP junk) on the platform it isn't even funny.

At one point in time, there were plenty of hobbyist developers out there, who had fun developing neat apps for the Palm OS because Palm had fun devices, with an easy to use OS, for a good price, with free OS updates, a highly motivated developer community, etc. The thrill is almost gone, and I wish they'd get it back.

RE: Lack of devices = lack of development?
rsc1000 @ 11/30/2004 12:05:37 PM #
Well - i for one have been really looking forward to this OS:

1. I think the new media server (called the 'video server'?) is the bee's knees. I played around with this for a bit and it really seems like the days of only having a (buggy) mmplayer (that you have to pay for) as the only serious video player option for Palm will be over - IF Cobolt sees the light of day. Not to slag mmplayer - they've done a good job making a player that uses standard codecs for an OS (OS5) that really isn't designed for this sort of thing.

2. Multi-tasking. Though some have slagged Cobolt as not 'true' multi-tasking, I don't think they understand the model. Cobolts implementation gets the job done, maintains compatibility, and is a lot more efficient than just leaving 15 programs running at once chewing cpu time and hogging memory (ie: PPC). I want this now: I recently was in the position (in my job as a project manager) of having to explain to management in my company why it was that the Palm version of our app couldn't multi-task (you couldn't leave the app, check yr email , then come back to where u were). I felt embarrassed for the platform (even BlackBerrys can do this!).

3. The drawing / graphics APIs and font system promise to bring things into the modern age. A lot of cool things should be possible with the 2d APIs - but the openGL ES implementation will really have things rocking when it comes. Any word on OpenGL Ben? What version of the OS?

Cobolt - bring it!


RE: Lack of devices = lack of development?
rsc1000 @ 11/30/2004 12:17:02 PM #
>>On a final note, Palm is so far behind in supporting Java (not that MIDP junk) on the platform it isn't even funny.

I'd actually settle for an update of MIDP - I just hope they maintain this and fix a couple of issues it has.

RE: Lack of devices = lack of development?
palmato @ 11/30/2004 12:46:29 PM #
>On a final note, Palm is so far behind in supporting Java (not
>that MIDP junk) on the platform it isn't even funny.

You're so right on this. And PalmSource should get most of the blame for dropping the java ball.
Anyway MIDP is not that bad: after all it was designed for phones not pda's. If only manufactures would provide the additional libraries for BT and PIM (defined ages ago) it would be much better :-/
Anyway, PDA should get personal java instead, which is much closer to standard desktop java than MIDP.

Unfortunately the PPC platform is more or less in the same mess, as on sun forums periodically somebody asks whether a suitable version exists... There are some options but they not for the small developer.

Right now the only alternative is superwaba: not really great looking but works reasonably well.


------------------------
Tired of PPC? Get a TT!

RE: Lack of devices = lack of development?
pmjoe @ 11/30/2004 1:14:52 PM #
> Unfortunately the PPC platform is more or less in the same mess

There are relatively cheap (Personal Java) runtimes you can buy for the Pocket PC platform. IBM's WebSphere has a J2ME CDC Personal Profile runtime for Pocket PC as well, but I'm not sure on the pricing. There are both Personal Java and J2ME CDC Personal Profile runtimes on the Zaurus.

Available on other platforms vs. not for Palm is hardly the same mess. If PalmSource was on top of this, they'd pull an Apple and set the standard for integrating Java with their OS and development tools.

At one point, I'd read a post somewhere that it was OS 5 and previous versions that was holding them back from better Java support (for example, J2ME CDC Personal Profile requires a full AWT implementation that would've been difficult under previous OS versions). If that's the case and we're waiting for OS 6, unless there's some serious work going on behind the curtains, it'll be 2006 before we see anything useful.

I just don't get the impression there is that much of a driving force behind Java at PalmOne or PalmSource. How many years have they been working on that PIM Java API?

RE: Lack of devices = lack of development?
pmjoe @ 11/30/2004 1:37:20 PM #
> I'd actually settle for an update of MIDP - I just hope they maintain
> this and fix a couple of issues it has.

I'd guess the current MIDP is tied pretty closely to IBM's Websphere Device Developer Edition. Knowing IBM, I'm sure they'll stick with it for some time for their enterprise customers.

Whether or not those updates get out to the public is another story though. I'd assume PalmOne paid IBM a licensing fee to get the version that's available for the Tungsten devices. What's next probably depends on the licensing arrangement (if it includes a certain level of support) and/or what PalmOne is willing to pay.

RE: Lack of devices = lack of development?
Tamog @ 11/30/2004 2:23:36 PM #
I personally think that the Palm OS can recreate an effect of multitasking-if the developer only knows how. Save the state of the app when the user leaves it, and return into this state when launched next time. I do not want to sound snobbish or anything, but PalmSource even tells you to do this...

Find out more about the Palm OS in my blog:
http://tamspalm.blogspot.com
RE: Lack of devices = lack of development?
just_little_me @ 11/30/2004 5:15:00 PM #
Ben, I understand more than you might think... it's been a long time since 6.0 was released, but that was obviously too buggy for any licensee to take seriously... hopefully with 6.1 things will start moving quicker. We all have a vested interest in this being true.

Mike, it's NOT a smartphone, it runs Palm OS, but I wouldn't call it a PDA either... it's a combined device, but with a rather different bent to what we've seen before... expecting a release/announcement early next year (like January!) They've done some neat things from a programmers point of view.


JLM.

RE: Lack of devices = lack of development?
palmato @ 11/30/2004 5:20:49 PM #
>There are relatively cheap (Personal Java) runtimes you can buy
>for the Pocket PC platform.

Actually I would love to see one. Because on the resources I found, there are many listed but most of them have prohibitive costs unless you're in the embedded systems business.

The only exceptions I saw are IBM J9 (only MIDP however), Sun reference implementation (not maintained anymore) and JVLite2 (but only with Netfront and unclear whether it's just for applets)

So not a huge difference from the PalmOs camp.


------------------------
Tired of PPC? Get a TT!

RE: Lack of devices = lack of development?
pmjoe @ 11/30/2004 6:57:38 PM #
> Actually I would love to see one.

WebSphere Everyplace Micro Environment Personal Profile 1.0 for Windows Mobile 2003 for $5.99:
http://www.handango.com/PlatformProductDetail.jsp?productId=140997

It's J2MC Connected Device Configuration (CDC 1.0_01) with Foundation Profile and Personal Profile.

Here's a good website with some info:
http://www.berka.name/stan/jvm-ppc/java_for_pda.html

RE: Lack of devices = lack of development?
grg @ 11/30/2004 7:21:14 PM #
Unfortunately, the big heads at JSR75 decided that a PDA profile for J2ME is not interesting enough. Too bad. And Palmsource is lame enough not to understand that Java PIM apps on the desktop could be huge for PDAs and solve many problems.

RE: Lack of devices = lack of development?
pmjoe @ 11/30/2004 8:09:15 PM #
I'm not sure what that blurb about JSR-75 on the PalmOS.com site is supposed to mean. JSR-75 went final in June.

http://www.jcp.org/en/jsr/detail?id=75
http://www.palmos.com/dev/tech/java/

So, in theory someone could implement it. I thought IBM was considering this for their MIDP for Palm OS, but maybe I'm wrong. I'd have to imagine some phone makers would want to support this as well.

RE: Lack of devices = lack of development?
mikecane @ 12/1/2004 8:40:38 AM #
>>>Mike, it's NOT a smartphone, it runs Palm OS, but I wouldn't call it a PDA either... it's a combined device, but with a rather different bent to what we've seen before... expecting a release/announcement early next year (like January!) They've done some neat things from a programmers point of view.

Oh geez. Is it at least POCKETABLE? I mean, I don't want something the size of a frigging -- oh, I don't know at this point. As long as it'll fit in my shirt pocket. Oh, and as long as I don't have to bloody **subscribe to a service** to buy it at a reasonable price.

RE: Lack of devices = lack of development?
EricGiguere @ 12/1/2004 12:02:14 PM #
Originally, JSR-75 was going to be a completely new J2ME profile, but that fell down the wayside due to politics and JSR-75 just ended up defining a couple of new optional packages. That's what the poster was referring to. The PDA Profile was going to "supercharge" MIDP for PDA-class devices.

Eric
http://www.ericgiguere.com/j2me/index.html

RE: Lack of devices = lack of development?
pmjoe @ 12/1/2004 12:13:25 PM #
My only complaint about JSR-75 is that, IMHO, it ought to be specified as optional packages for both J2ME CDC and CLDC (instead of just CLDC). I agree with their conclusion that a profile just for PDAs wasn't that interesting.

RE: Lack of devices = lack of development?
EricGiguere @ 12/1/2004 2:28:11 PM #
Not sure what you mean. The CDC is a superset of the CLDC, so any optional package that is CLDC-client will run on any J2ME platform. Whether or not individual platforms support a specific optional package is up to them, of course. So there's nothing preventing JSR-75 from being implemented on any PDA that supports a J2ME profile, whether it's the MIDP or the Personal Profile.

Eric

RE: Lack of devices = lack of development?
The_Voice_of_Reason @ 12/2/2004 3:41:36 AM #
We are aware of this; belive me, PalmSource would like devices that run Palm OS Cobalt to be on the market as soon as possible.

Of course you would. Especially since PalmOS is essentially your only source of revenue.

However, you have to understand that the Palm OS deployment model is a bit different from that of other OS vendors. Since we support a diversity of hardware, there can be a bit of lag between when we finish a release of the OS and provide it to our licensees and when they complete their customizations for their particular hardware platforms.

I'm disappointed to hear you parrotting the standard PalmSource company response, Ben. Cobalt is toast right now because:
1) It was late. VERY late.
2) It doesn't offer features compelling enough to force licencees to gamble on testing the water with a brand new (likely buggy) OS.
3) Major licencees have already invested a lot of time hacking PalmOS 5 into being able to do what they want an OS to do. Why change to a new OS if PalmOS 5 already works fine? Why on earth would Tapwave switch to Cobalt? Or Garmin? Or Palm, for that matter. And is the telephony part of Cobalt even finalized yet?
4) It has no "killer apps".
5) Now that Sony's gone there is no longer any incentive to "push the envelope".

Our licensees also have tended to bundle a number of third-party applications, and those take time to customize for the new devices and OS releases as well. Now, with an emphasis on smartphones, you also have the lagtime of operator certification.

Blaming 3rd party apps? Now that's an exceptionally WEAK excuse. Not even ONE PalmOS 6 device is available. One year after the OS was released. Even the best spin doctors can't make that one disappear. Please.

It's a long process, but it helps ensure that Palm OS devices take full advantage of their hardware and provide lots of functionality out of the box with a high level of usability.

If quality control is so important, why are we seeing so many incompatibilities + bugs coming from Palm these days? Let me guess: "PalmSource and Pa1mone are two separate companies."

Aaron is correct; unless you have a specific opportunity around Palm OS Cobalt, it's probably not time to port your applications to the Protein API.

--
Ben Combee
http://palmos.combee.net - PDA programmer weblog

In other words, no one is going to be developing for Cobalt any time soon.

Delayed OS -> no hardware -> no apps -> no consumer interest -> no sales -> negative feedback loop.




******************************************************************
Sony CLIE UX100: 128 MB real RAM, OLED screen. All the PDA anyone really ever wanted.

Ben Combee: please don't let 'em turn you
The_Voice_of_Reason @ 12/2/2004 10:34:32 AM #
I realize you now work for Palm, but please don't become another apologist.



******************************************************************
Sony CLIE UX100: 128 MB real RAM, OLED screen. All the PDA anyone really ever wanted.

RE: Lack of devices = lack of development?
alanrey @ 12/2/2004 10:54:48 AM #
Bump on RSC1000 post : what about OpenGL ES ? Palm said in March it became a member of Khronos Group, nothing else since. What should we do await for ? JSR 187 under J2ME or native Cobalt OpenGL ES support ? It's REALLY important to know, as things are going really fast on this market (smartphones, GSM, PDA) and choices have to be made (SuperWaba or J2ME Java apps to target Nokia, SE GSM as well as PDA's, or native developments).

RE: Lack of devices = lack of development?
Strider_mt2k @ 12/2/2004 11:08:33 AM #
It apparently works out much better for raising the stock price to simply announce you are on board with lots of stuff, and then make excuses later (after profiting from the stock rise) that it didn't work out, or to simply ignore what was posted initially.



RE: Lack of devices = lack of development?
Gekko @ 12/2/2004 12:43:32 PM #
>"It apparently works out much better for raising the stock price to simply announce you are on board with lots of stuff, and then make excuses later (after profiting from the stock rise) that it didn't work out, or to simply ignore what was posted initially."

Great post. Very true.



Is PalmSource Installer a Palm OS App, or PC App

kpr @ 11/30/2004 4:57:54 PM #
>> "PalmSource Installer is designed to allow developers to bundle their Palm OS software application, support files and desktop components into a single, compressed software package that a user can download and install with a single touch of a button, whether via a HotSync connection to the PC or while on the go, via OTA delivery."

So it sounds like "PalmSource Installer" is an application that runs on your Palm OS Powered device, not on your PC. Is this correct???

Furthermore, does it run under Palm OS 5?

RE: Is PalmSource Installer a Palm OS App, or PC App
cdunphy @ 11/30/2004 5:41:22 PM #
The PalmSource Installer consists of a developer tool for developers to create .PSI packages, a PC conduit for installing from you PC, and an on-device client for OTA downloading.

You can try out the installer yourself - we have a sample page.

From a PC: (note - the demo page is IE only for now)
http://www.palmsource.com/installer/demo

From your wireless handheld:
http://www.palmsource.com/installer/demo/ota

I'd love to get feedback on what you think.

Top View Full Comment Thread
Achtung! Only the first 50 comments are displayed within the article.
    Click here for the full story discussion page...

Account

Register Register | Login Log in
user:
pass: