In the deep dark past, there was a version of Maple for Windows CE that ran on just one machine (since all those CE machines were on weird CPUs at the time). It ``worked'', but that's about as much as can be said for it!
Take a good look at Maple, and you will see that it really is many different products in one. One product, the glorified calculator
, could potentially be done on a PDA. In fact, many old TI calculators do just that, but with Derive (a darn fine CAS by the way) instead of Maple. But even that has problems as frequently the answer does not fit on the tiny screen.
Which leads to all the other uses of Maple, whether it be as a presentation device
, exploration medium
or some new applications, bottom line is always the same: such uses are very screen real estate heavy
. In other words, they need a lot of screen space
. So while Maple on a PDA seems like a cool idea indeed, most use cases
for it show that there is an impedance mismatch between the product and the media. This is not Maple specific -- many companies are having a really hard time making their web-based products work properly on the small screens of cell-phones and always-on PDAs. Ever wonder why the most successful such device, the RIM Blackberry, has a comparatively huge screen? Now you know.
In fact, this need for being able to use all available screen real estate when doing work in Maple is so strong (at least in my uses), that even though I have a giant screen (23 inches diagonal, which I run at 2048x1536, the equivalent of 4 full 1024x768 screens), I still
get annoyed by some of the real waste of useful space by the (new and even a little bit the old) GUI.
Ah well, I am saving up my money to buy a bigger screen
, although what I would really like is too pricey