Today, I came across some flavors of SWT that help the mobile application developers. See http://blogs.forum.nokia.com/blog/hartti-suomelas-forum-nokia-blog/2007/10/09/eswt-plug-in-for-s60-3rd-ed-fp2-sdk
The site "http://www.javalobby.org/java/forums/t102370.html" says:
This adds yet another UI toolkit to the already overly fragmented mobile UI toolkit panorama. There are now over a dozen UI toolkits available to mobile users. Most of the toolkits are very basic, and this is where eSWT intends to make a difference. The eSWT toolkit provides advanced features that will enable an easier transition to the mobile space by those familiar with SWT. AGUI is supposed to compete in the advanced mobile UI toolkit war, but its future is now uncertain (the AGUI JSR was approved over a year now. However, adoption by vendors is yet missing). Sun is pushing JavaFX Mobile very strongly and some of the AGUI people moved over to the JavaFX Mobile team. The outcome of the Savaje acquisition is still unclear. Savaje was one of the few vendors that supported AGUI. eSWT is not a JSR, I find it always a bit strange, when corporation that participate on the JCP/JSR process, go outside of the standardization process and roll out their own proprietary/costume solutions. IBM does this, and so does Nokia. It makes one wonder - Why do they bother to participate on the standardization process in first place? Nonetheless, the embedded Eclipse community appears to be doing a very good job catching up with NetBeans, and the eRCP is worthy of a deeper investigation. Competition is always good. It is however unfortunate that one of the competitors is totally standardized and open, while the other is just open.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment