- HTC Touch
- HTC Touch Pro
- HTC Touch Diamond
- HTC Mogul
Official support for a selection of Windows Mobile Standard (these are typically the ones with the mini Querty keyboard and no touch screen like the Samsung ACE (i325)) is said to be announced shortly as well. Moreover, Sprint Titan is said to be integrated on Sprint’s mainstream Feature Phones.
In addition to the production stack which installs only on devices operated in the Sprint network (Sprint branded phones as well as non-Sprint branded phones provisioned by Sprint), Sprint offers 90 days trial versions of the stack which install on any Win Mobile 6 device. I have tried with a HP iPaq 614c and it works great! In my opinion, with these trial stracks Sprint offers a great service to all OSGi enthusiasts around the world who can pick up the stack and get started.
Compared to what Sprint released in December last year, the new stacks now support Location API on the CDC side, contain a bunch of bug fixes and have been performance improved. Functionality wise, there is still work to be done (full web widget and service remoting support, additional JSR support on CDC (like 135), OSGi Bundle App Model support, etc.). However, the new releases are a major improvement over the old versions and should be fun to use!
The new release package also consists of a new version of Sprint’s Eclipse IDE plugins (now Eclipse 3.4 is supported, several bug fixes were applied) as well as an 80+ page developer guide that helps developers get up speed. A set of application demos (binaries, source code and documentation) will come out shortly as well.
It’ll be very interesting to watch what the creative people around the world will start doing with this beautiful and powerful platform!
6 comments:
This is great news! Question: When you say Titan will be "integrated on Sprint's mainstream feature phones" what exactly do you mean? To my knowledge, eSWT has only been implemented for Windows Mobile and S60. Does Sprint count some devices running such systems as "feature phones?" Or will there be bundles to support GUI development using some non-SWT toolkit? Also, your statement suggests that Sprint will have CDC/FP Java runtimes on feature phones. I'm not necessarily doubting you, just that if it's true we've come a long way! :-)
Hey David, great to hear from you again. Sorry for the little late response. I have read your blog on Palm's webOS and your speculations on them having OSGi built in. I must admit, I agree 100% that OSGi would be a perfect fit for webOS, especially in combination with Sprint/ProSyst's Rich MobileNet Application model (in this model you can make use of phone platform capabilities as those are exported as webservices on the local web server). This would complement their WebKit UI story in a powerful, beautyful and extreme performant and charming way. Why don't we join forces to envangelise them on Mobile OSGi?
Anyway, to your questions:
When you say Titan will be "integrated on Sprint's mainstream feature phones" what exactly do you mean?
What I mean here is that they will put their Titan platform on a Brew based feature phone handset.
To my knowledge, eSWT has only been implemented for Windows Mobile and S60. Does Sprint count some devices running such systems as "feature phones?" Or will there be bundles to support GUI development using some non-SWT toolkit?
Correct, I do not assume they could port the eSWT part to feature phones in near term so I conclude they will support other app models instead.
Also, your statement suggests that Sprint will have CDC/FP Java runtimes on feature phones. I'm not necessarily doubting you, just that if it's true we've come a long way! :-)
I can tell you for sure that indeed we have come a long way!
Cheers,
Jo
Hi,
Is there any implementation of Mobile OSGi for CLDC devices?
I only know mBS CLDC Edition from Prosyst.
Thanks.
The ProSyst implementation is about the only one I know as well.
Jo, how does the CLDC implementation work in the absence of classloaders, reflection, etc?
A fully compliant OSGi implementation you will never get on CLDC. Missing classloaders, an entirely different security concept, etc. are reasons for that. However, it is possible to carry over at least some of he good stuff like the service registry.
The CLDC OSGI Framework of ProSyst is more like an SDK which you can use to modularize your app (the FW gets embedded into your midlet suite).
Post a Comment