Slashdot Mirror

WinCE still exists on products that are sold right now . PalmOS doesn't. I think WinCE beat it just fine.

Now I'm going to go back to work on this custom barcode scanning application I'm developing for a client that uses some devices running Windows Mobile 6.5 (WinCE 5.2 kernel, pre-Windows Phone 7) and Windows Enhanced Handheld 6.5 (WinCE 5.2 kernel with some userspace enhancements backported from Windows Phone 7). These devices use real barcode imagers, not cameras, so, no, a cheap-o Android phone would not suffice. They're ruggedized handheld computers, and they cost around $2k each. This is the level of hardware that runs WinCE.

Remind me again how WinCE is an also-ran? Oh, yeah, that's right. It's not. It's just not used for anything glamorous. It gets real work done. Isn't that the measure by which Linux is supposedly better than Windows? Sounds like a double-standard to me.

Meanwhile, my iPhone has been abandoned in a box in my closet for 4 years and my Android phone has only three jobs: Cellphone use (calls, texting, etc.), Bejeweled-clone when I'm trying to bore myself to sleep, and sucking power from a USB port. So, yeah, "glamorous" ain't all it's cracked up to be.

I'm out of practice... was "playing" https://developer.palm.com/appredirect/?packageid=de.komola.pi

Try here: https://developer.palm.com/

The source for WebOS is available under an open source license: http://opensource.palm.com/packages.html
WebOS did not fail. Palm failed to successfully market its products for 20 years. Mozilla can make a lot of headway quickly by using WebOS as a base. With Mozilla's community clout and business position I would not be surprised to see devices running Firefox OS in a year or two.

You seem to fail at understanding fail.

The source for WebOS is available under an open source license: http://opensource.palm.com/packages.html WebOS did not fail. Palm failed to successfully market its products for 20 years. Mozilla can make a lot of headway quickly by using WebOS as a base. With Mozilla's community clout and business position I would not be surprised to see devices running Firefox OS in a year or two.

And jumping on board with a platform that is being shoveled out the door by HP, with no future development in sight, is a smart move to make? Who knows, they may adopt some of what's in webOS, maybe merge it into Qt. We don't have visibility into much more than what's been pointed out today.

Actually, the upcoming Open webOS will be based on Qt (QtWebKit to be exact): http://developer.palm.com/blog/2012/02/sams-blog-february-releases-for-open-webos/
The core experience of what webOS actually is, is just written in JavaScript anyway.
If nothing too unexpected happens, Open webOS will just be a bunch of modules that run on QtWebKit which in turn runs on Mer or any other Linux distribution.

Since you're so familiar with the details, care explaining how?

Ok, to start with, simply compare at a high level the modules/frameworks each SDK offers:

QT 4.7 modules

Compared with WebOS

Where are the higher level frameworks in QT? Perhaps they are in Mer, but I could find no reference for that, which indicates there's not much Mer there.

If you want to talk about competing with the other existing mobile OS'es, just look for anything remotely like AVFoundation in IOS for control over data from cameras or other media...

Mobile programming these days is a LOT more than just being able to draw or do simple animations or being able to hit SQLLite.

Or is this yet another empty implication?

That would imply I ever had any "empty implications", whatever the hell that means.

Is that something like when you are not a mobile developer and you cast aspirations of those who are when they try to tell you how things really work?

So they should have gone with an OS they were totally unfamiliar with

Yes, if they actually wanted to have meaning in the market instead of chasing their tails. Instead the prediction of their demise is sadly all too certain to make.

They could have folded some aspects of MeeGo into the underlying WebOS infrastructure, but Qt 5 is ANCIENT compared to modern mobile OS's. They will get nowhere with this little vanity project, which makes me sad indeed given the effort they will undoubtedly sink into it. I despise wasted potential.

a number of people have caught on to the fact that the engine behind webos is the exact same engine as behind safari, but that safari is *not* the basis of apple's operating systems. the glue that makes apple's OS so dynamic is objective-C, which has built-in runtime dynamic data typing similar to DCOM. that means that components can interact, written in c++, or any other programming language including scripting languages, *without* having to recompile any applications.

no, if you want to know why webos is so fracking slow, you only have to look right here: http://opensource.palm.com/3.0.4/index.html

notice anything? keep scrolling down... keep scrolling down.. lmnop..q... ah ha!

qt4 qt4-4.7.1.tgz qt4-4.7.1-patches.gz

that's the reason.

how do i know this? it's because i was asked, 2 years ago, to get pythonwebkit up-and-running for an embedded client, running on a superb but very strange 400mhz ARM9 processor with access to 800mhz DDR2 RAM (for doing 1080p HDMI video). for an ARM9 it ran like lightning. *but*... when i put pywebkitqt4 on it, it not only doubled the amount of memory usage but it absolutely _hammered_ the processor.

the startup time _just_ for webkitqt4 alone was something like 90 seconds and took up almost all of the available 256mb of RAM. the next best was webkit-enlightenment (130mb and about 8 seconds). webkit-efb was what samsung sponsored for the "bada" initiative. next after that was webkit-gtk at around 6 seconds.

however none of these were acceptable, so i helped denis do a port of webkit to directfb. that got the startup time - on a 400mhz ARM9 - to a stunning 1.5 seconds.

if HP or Palm had paid myself and denis to do that work several years ago, things would have been very different: the startup time and performance of WebOS would have been staggeringly quick.

and the thing is, because the browser _is_ the OS, there's absolutely no good reason to even have GTK, QT4 or in fact any other "engine" underneath. why do you think google created an entire new direct-rendering API ("silk" i think it was called) for android?

lesson learned. only cost $1.2 billion. i would have been happy to have been paid 0.1% of that to fix the problem. talk about irony.

Sending what is a basically a web browser with some java script libraries out to compete against polished binary platforms in a consumer already dominated by well polished easy to manage binary apps was space was not and is not going to work.

Then it is fortunate that WebOS developers have an alternative.

I got my UK TouchPad in the firesale (116 pounds for 32GB model - yes, rip-off Britain strikes again) and whilst webOS is OK, it's not as stunning as people make out. The card model isn't the greatest thing since sliced bread - your "flick to minimise" has to be precisely co-ordinated otherwise you end up having to use the bezel button instead (the number of times I've just scrolled instead of minimising is annoying). The lack of a close button on the windows mean two actions instead of one (flick+flick or bezel button+flick) to get finally close an app.

However, it's the lack of apps that's the real killer of WebOS - whilst software written for the various Pre mobile phone models had slowly increased, the ones that are TouchPad compatible (i.e. didn't run in a small Pre phone emulator) were building up even more slowly. So much so, there was an embarrassing trumpeting by HP recently that they'd hit 1,000 apps for the TouchPad, a mark that I suspect Android and iPad tablets exceeded within a week of their release (and that was a couple of years ago too!).

For example, I can't find a decent free fullscreen webOS chess or Sudoku for the TouchPad (they are either for the Palm Pre phone or cost money), whereas there are dozens of each on Android. It's why I'm now mostly using CyanogenMod 7 on my TouchPad - there's loads of apps on my Android TouchPad now don't have webOS equivalents (even with Preware installed, which I do have).

Microsoft is hijacking the HTML5/JS terminology for Windows 8 similar to how they hijacked the Java language on the windows platform. The support for HTML5/JavaScript is really to use their proprietary WinRT framework. So Win8 apps will not work on webOS.

There's no hijacking there, quite the opposite - a lot of things in WinRT are deliberately made inaccessible specifically to JS apps in those cases where a portable HTML5 solution exists instead (XAML UI being a prominent example, but there are many others). WinRT is there so that OS-specific features are exposed for those apps which want or need them - such as context menus ("charms"), or registering the app as a handler for a certain file type, or app lifecycle management; or for things that could be portable but aren't covered by HTML5 specs today (e.g. camera API).

This, by the way, is not any different from how HTML5 apps work on webOS, which also has its own proprietary API extending HTML5/JS core. This is inevitable, because the existing specs are simply not rich enough to cover all scenarios that are needed for a full-featured app that runs outside the browser.

So an existing webOS app will likely not run on Win8, and an app written specifically for Win8 will likely not run on webOS. However, because UI is HTML5/CSS in both cases, and because many APIs are standardized and thus shared, it's much easier to port. Furthermore, when someone starts writing a new app with portability in mind, it's fairly easy to account for OS differences, and to have a single HTML/CSS/JS codebase that uses portable APIs for its core functionality, and OS-specific APIs for deep integration on every targeted platform.

Heck, for some kinds of apps - e.g. if it's a 2D game, where you can just use Canvas - you might get away without having to use any platform-specific APIs at all.

By the time this made it to slashdot, the deal's more or less in the final phases of burning out.

On the other hand, I did order mine so hopefully it will actually show up.

An Android/Cyanogenmod is inevitable with several devs already signed on with more expressing interest. Source for the kernel is also available.

Unfortunately, though this is a great deal, this is not a tablet where the android community will grow (as w/the nook, which are still available and a great deal in its own right w/cm7).

Not sure if enough information is present to load Ubuntu onto an HP TouchPad.

as well as the unlikely possibility that HP will open source it.

WebOS, like Android, runs atop the linux kernel. You can download the source, plus the patches, from the palm website.

HP is committed to making the webOS developer program the world leader in developer benefits, growing the developer base, and helping developers showcase their products. Over the coming months, the webOS ecosystem will be growing dramatically as webOS is introduced to PCs and printers, and into the enterprise with a scale only HP can provide.

Jeebus, did anyone here sign on to this gobbler?

I don't care *who* 'wants' it, Google is going along with it (and has been going along with it from even before movie studios were involved). The whole reality that one has to root/jailbreak your phone means the vendor is not being completely open.

Though less 'open', WebOS at least gives end users more sanctioned control over their device. You enter a well-documented code to enable the option to provide root shell and sideload applications. Too bad they have not seen success in the market, *but* I would encourage people seeking a device that gives them control to consider it a haven from iOS, Android, BalckBerry, and WP7 devices. I personally will only buy a phone that needs such BS as 'jailbreaking' when I simply have no option left. I don't care how 'easy' it is *unless* the manufacturer comes right out and officially says "here you go, we have no intent on restricting you in the future, have fun" (see http://developer.palm.com/blog/2011/05/10-reasons-for-geeks-to-love-hp-webos/ number 2). I don't want to be stuck in a fight with the company I gave money to for the duration of my ownership of it.

OpenMoko also is open *and* gives ultimate control, but unfortunately is a pretty impractical platform for a lot of the stuff people want to do with their handheld devices.

The "religious fundamentalism" you deride is responsible for developing the system that millions are using on desktops, media boxes, phones, etc., for free. The only reason people work for free is when they are working for an ideal.

As far as your specific concern about video drivers, Ubuntu doesn't (and can't) distribute nVidia's proprietary graphics driver. But downloading and enabling it is as easy as clicking System> Administration> Hardware Drivers.

The last time I checked, fundamentalist preachers don't have "click here for a keg" signs in their churches.

You don't get it, you don't need to write apps for a WebOS. It's a WebOS, it runs the Web, and Web Apps.

No, it's not just "web apps".See the dev kit

"PDK Plug-ins

Plug C/C++ components into your HTML/JavaScript/CSS apps for more power and easier ports.

PDK Plugins description

PDK Plug-ins

Mix web technologies and C/C++ components in a single app

Today, you can use the webOS Plug-in Development Kit (PDK) to build games and immersive apps in C/C++. But the feature that gives the PDK its name—the ability to build C/C++ plug-ins for your HTML/JavaScript/CSS apps—is still in beta as of 1.4.5.

This feature will exit beta in webOS 2.1, opening the door for you to distribute apps that incorporate PDK plug-ins. Using plug-ins, you can more easily port app logic from other platforms while leveraging the Mojo Framework to give users a familiar interface and integrate seamlessly into webOS.

Even if you’re not porting, plug-ins give you the option of utilizing the PDK for graphics- and performance-intensive features as needed, while building the rest of your app in HTML/JavaScript/CSS—and enjoying the lightweight development process and rapid iteration that these web technologies enable.

Plus, by using c/c++, you're not giving users the source to your game or app.

You don't get it, you don't need to write apps for a WebOS. It's a WebOS, it runs the Web, and Web Apps.

No, it's not just "web apps".See the dev kit

"PDK Plug-ins

Plug C/C++ components into your HTML/JavaScript/CSS apps for more power and easier ports.

PDK Plugins description

PDK Plug-ins

Mix web technologies and C/C++ components in a single app

Today, you can use the webOS Plug-in Development Kit (PDK) to build games and immersive apps in C/C++. But the feature that gives the PDK its name—the ability to build C/C++ plug-ins for your HTML/JavaScript/CSS apps—is still in beta as of 1.4.5.

This feature will exit beta in webOS 2.1, opening the door for you to distribute apps that incorporate PDK plug-ins. Using plug-ins, you can more easily port app logic from other platforms while leveraging the Mojo Framework to give users a familiar interface and integrate seamlessly into webOS.

Even if you’re not porting, plug-ins give you the option of utilizing the PDK for graphics- and performance-intensive features as needed, while building the rest of your app in HTML/JavaScript/CSS—and enjoying the lightweight development process and rapid iteration that these web technologies enable.

Plus, by using c/c++, you're not giving users the source to your game or app.

Where there is a http://opensource.palm.com/, I don't know to what extent they're opening up the entire OS.

Could WebOS be the Great White Hope for geeks now that Nokia has gone to the dark $ide?

And how open (rooted) are HP current or future WebOS handhelds to be?

Is there any HP analogue to the N900?

Unfortunately, the quantity of apps is lacking, but as a fan of FOSS, you may be interested in how much WebOS has in common with other Linux distributions.
Kernel 2.6.14
glib, udev, lvm, WebKit, gStreamer, etc

Take a look here:
http://opensource.palm.com/1.4.5/index.html

If you install a terminal app and take a look around, it looks much like a standard Linux system. Often times Linux apps compiled for arm just work.

To answer you question: Freedom! Palm (now HP) have been encouraging people to hack/extend/play around with the system. It's a great little Linux system with a top notch interface(Luma). It's a shame that it's so ignored.

That being said, I have no idea what this "webOS on a PC" means. it may just be the Luma interface running on windows, which just sounds 'ick'.

There was a watch that was a full PalmOS device. You can still find them on eBay and they are probably still the most versatile watch computer ever sold. It was Fossil brand, too.

With technology improvements it should be possible in a year or two to have a full Palm Pixi equivalent in a watch.

I have a website that tell you when your bus or streetcar is going to arrive and I often think it would be very useful if there was some way to have that information on my watch.

Something similar to webOS dashboard controls that get exported to your watch would be one approach.

Palm (now HP, I guess) tells you how to enter "developer mode" for WebOS on their own website: http://developer.palm.com/index.php?option=com_content&id=1639#InstallingEclipsewiththeSDK-dev_mode Developer mode on a WebOS phone is the same as jailbreaking on iOS/Android: it allows you access to the file system, a command line if you want it, and the ability to install applications from any source. There is a LOT of homebrew development for the platform, and all of it is officially supported by Palm/HP. They even recently donated a server to a homebrew dev group.

Thankfully Palm tells you how to do this for free on any WebOS device. Download the tools for free and install your own apps over a USB cable. I think someone actually has a way of doing this wireless too.

http://developer.palm.com/index.php?option=com_content&view=article&id=1552&Itemid=59#dev_mode

Really nice OS, sensible company. Pitiful marketshare. :(

People seem to be OK with an Apple-only phone.

Who knows what will happen with Symbian and MeeGo.

Anyway, I think there was a Pre2/WebOS2 on its way?
http://www.palm.com/us/products/phones/pre2/index.html

Is probably sweet.

Back in the days where a phone where just a phone it would had been a non-issue. Now when it's a computer compatibility matters more.

Because Palm has had their web app to drag-and-drop to create webOS apps for quite some time now.

Because Palm has had their web app to drag-and-drop to create webOS apps for quite some time now.

...for quite awhile now.

Welcome to the party:
http://ares.palm.com/Ares/about.html

3Com press release of the Palm VII in October of 1999, two months before this patent was filed. The press release explicitly mentions wireless e-mail. http://investor.palm.com/releasedetail.cfm?releaseid=338689

There is probably even earlier prior art as the idea is trivial and was plainly obvious when 3Com released the Palm VII (microwave stations anyone?). This patent also seem to cover any computer using Wifi.

It was stupid when it was filed and is stupid now.

C API:
- Android: closed
- WebOS: closed

You apparently haven't heard of the Palm PDK.

So to both developers and consumers, iPhone OS is the most open.

The platform that forbids any language other than C, C++, Objective C and Javascript, forbids interpreters and doesn't allow you to install third party apps is "the most open". Gotcha.

You have to explicitly enable the "I know what I'm doing, stop protecting me" flag in your app to allow these types of exploits.

http://developer.palm.com/index.php?option=com_content&view=article&id=1756

I've never had a problem with the Emulator. Just press ESC for the back gesture. Would be nice if you could test the other physical buttons (some are emulated) and gestures, though.

Besides, you should always be testing on actual hardware as well as the emulator ;-)

This.
Also this.

That is why I love my Pre so much. Fuck Apple.

Palm not only has root available on all their WebOS phones,

Android is Open Source, part GPL and part Apache.

It's partially open source. Ever seen the source code for Android Google Maps or any of the other Google apps on Android?

WebOS is closed source, it uses the Linux Kernel but most of the OS is proprietary.

It has a lot of open source components. Not just the kernel. WebOS is a recognisably Linux in a way the Android isn't, it contains many of the elements of Linux besides the kernel. Heck, it even contains an ARM assembler on-board. (And mine contains gcc too, but that's because it has a Debian chroot installed. :) ) Even the closed-source stuff is mostly HTML5 and Javascript, is not obfuscated, and is easily modifiable.

I cannot customise nor install a custom version of WebOS on a Palm device.

You can customize WebOS quite a bit, and literally hundreds of patches and themes are available for it. Yes, few custom ROMs have been developed for WebOS, but since you don't need to do anything special to get root, or to customize WebOS, there's not much of a need to flash a new ROM.

Because the new C API will not be generally available during this period, only apps using the Web-style API (either hand-coded or through ARES) are eligible.

This is interesting because they claim at present that they will introduce the C-style API in March and that overlaps the period.

See the actual terms for details.

D

http://developer.palm.com/index.php?option=com_content&view=article&id=1841&Itemid=35

Palm actually uses a bunch of GPL'd code (the Pre is Linux based) and they do make the code available. In fact, I think some of it even comes on the device itself.

...citation?

Search engines are your friends:
http://opensource.palm.com/packages.html.

Now, is this actually compliant with the GPL? I'm not sure.

I would like to think that the muPDF people are not sue-happy, so maybe Palm is supposed to release some other code that's not on that page.

http://opensource.palm.com/packages.html

This is not rocket science to find, VG. Upon hearing of an accusation, you really should not take it with face value until you examine it directly. Even if said accusation was wrapped in a lawsuit from a prissy developer.

muPDF is available from Palm's site, both as original and as their patches. Here are URL's for each:

http://palm.cdnetworks.net/opensource/1.3.1/mupdf-1.0.tar
http://palm.cdnetworks.net/opensource/1.3.1/mupdf-1.0.tar-patches.tgz

This news made the rounds last week, and it's entirely possible that those are recent additions. Unless you think that either (1) there are more modifications not listed, or (2) that the court should impose punative damages on what was almost certainly an oversight, this matter is settled.

http://opensource.palm.com/packages.html

And you can root your webOS device trivially easy. And develop on it for free. AND they are/are planning to waive their fee for open-source apps in their app store.

The problem is Palm is abiding completely by the terms of the GPL. Source for the package (and their modifications to it) are freely available: http://opensource.palm.com/1.3.1/index.html and have been for every released iteration of WebOS: http://opensource.palm.com/packages.html.

The problem is Palm is abiding completely by the terms of the GPL. Source for the package (and their modifications to it) are freely available: http://opensource.palm.com/1.3.1/index.html and have been for every released iteration of WebOS: http://opensource.palm.com/packages.html.

http://opensource.palm.com/1.3.1/index.html
http://palm.cdnetworks.net/opensource/1.3.1/mupdf-1.0.tar
http://palm.cdnetworks.net/opensource/1.3.1/mupdf-1.0.tar-patches.tgz

the violation is obvious

No evidence of code out there.... and the app doesn't exist in a vacuum.

If fact, it's quite clear what the problem is: violation.

http://opensource.palm.com/1.3.1/index.html would disagree with you.

I'd agree, it is quite clear what the problem is. But it's not a GPL violation...

http://opensource.palm.com/1.3.1/index.html
http://palm.cdnetworks.net/opensource/1.3.1/mupdf-1.0.tar
http://palm.cdnetworks.net/opensource/1.3.1/mupdf-1.0.tar-patches.tgz

(info from post #30349382)

I don't think I'd predict that WebOS will be up near Android or the iPhone in 2012, but it'll likely still be around. The original analysis doesn't even mention them. Many people think that WebOS has the best technology of any of the existing mobile OSs, although they obviously need more apps (coming soon) and more phones (coming soon).

I see a lot of mis-quoting going on here (welcome to Slashdot), so here from developer.palm.com are the basics of the pricing scheme, for those to lazy to read:

• $99 - Official membership in the Palm Developer Program. $50 per App submission (one-time). Palm will review your applications, help you debug them, and offer them in the App Catalog. You may charge for your application, and you are paid "70% of revenues, net of applicable taxes". Visa and Mastercard accepted. You may also allow users to download your application with a special link to Palm's app repository.

• $0 - Unofficial membership in the Palm Developer Program. $50 per App submission (one-time). Palm will NOT review your applications, help you debug them, or offer them in the App Catalog. You may NOT charge for your application, and you may ONLY allow users to download your application with a special link to Palm's app repository.

Not a bad deal, they give developers freedom (charge a nominal fee for maintenance; if it's going to cost $50 to list it better be worth it), and they're able to yank any malware/trojan BS once it's discovered, and possibly trace the author. I like it.

In September Zawinski was called by Joe Hayashi from Palm, formerly Senior Director of Product Management for Yahoo!. Despite the treatment from Palm over this matter Hayashi said "We aren't asking that you remove the binaries or source of your apps from your web site, and we aren't restricting anyone from distributing their source code, open source license or otherwise."

Yet the Palm SDK License (as linked to in the article) states under section 4. Developers' Ownership and Ability to Distribute its Applications:

4.3 Applications Can Only Be Distributed Through the Palm Application Catalog. Developer acknowledges and agrees, that absent a separate written agreement with Palm, Developer may not distribute any Application except as allowed by Palm's formal approved distribution process and channel (the "Application Catalog"). Developer acknowledges and agrees that (a) distribution of Applications will be subject to further terms and conditions, which may include a share of the revenue generated from sale of the Applications to be paid to Palm by Developer, where such terms and conditions shall be presented to Developer upon or before Developer's request for distribution of any Application, (b) because of certain laws, regulations, as well as contractual or other restrictions, Palm may refuse to allow the distribution of certain types of Applications, and (c) distributed Applications may be viewable or inspectable by third parties, and Palm is not obligated to take any steps to obfuscate the code associated with the Applications or take any other steps to prevent third parties from viewing or inspecting Application code.

Now this is assuming Jamie Zawinski used the SDK to produce the Palm Pre programs (I'm not sure what the Pre can run and these programs seem to be merely ports). After searching around for the terms of service for the application store for the Palm Pre, I came up pretty empty handed aside from the Developer SDK License. The fact that it says 'Beta' on the app store may make this forgivable but I'm not seeing a clear distinction on the fine details and legal on what you may or may not do when submitting an application. It appears there may be some internal conflicting views also -- considering what Hayashi said and what Palm did.

We got more applications than we could handle well, which is a good problem to have. Unfortunately, it means we dropped some things on the floor, and that's bad, but with the impending "stuff" that's coming, this is all going to get a lot easier for everyone and a lot more transparent.

If you didn't get a response in a timely manner, let me apologize to you. We should have done a better job on this, and I apologize for this. I'm working with the people I work with on this to try to make sure we do a better job of this moving forward. Good news is we've hired some people -- one's started, one starts next week, and the third starts the week after that, and that'll give us some great people and some new resources to make sure this gets fixed and works properly.

As the previous poster started, unlike the iPhone, there is a very active home brew community which Palm has not only blessed, but has assisted with:

http://www.webos-internals.org/wiki/Application:Preware

Even worse, the real topic was disappointing. I was hoping it was an article about the Palm Pre.

A friend of mine recently got a Mac. He is a longtime Palm user and has a Palm Treo 680. I assumed that iSync would support the Hotsync and thus all devices powered by Palm OS.

I was wrong. If you take a look at this:
http://support.apple.com/kb/HT2824
You will see that the Tungston and Zire family of phones is supported. No Treo at all. According to him (I only had him on the phone) iSync didn't sync to his phone. He has a roommate who is a Mac fanboy (main reason for the Mac, because he is not a computer geek and onsite support at home is pretty cool) who initially set up everything so I suppose he would have set up iSync if it had worked. So Apple support for Palm seems to be rather spotty at best. No Centro or Treo Pro like the website/blog that Slashdot links to were supported anyways. How can Apple drop support for something they never supported in the first place?

Palm has a very good PIM (actually used to have unfortunately, since developement seems to have stopped). So good that I used to give it to people looking for a simple PIM for their computers who never heard of Palm. They also have a version for the Mac:
http://www.palm.com/europe/en/support/palmdt4_mac.html

Hopefully this will run under Snow Leopard, or maybe Palm will put another revision out if it doesn't.

Anyone here who got his Palm Treo or Centro to run with iSync? And if so, how?