I think there is hope. This is post by Sanjiv on this blog:
http://www.jroller.com/sjivan/entry/smart_gwt_touch_mobile_support
Jeremy, version 2.3 was an SGWT EE "sync" release to bring the EE features, docs, samples up to date.
See http://blog.isomorphic.com/?p=201
The next release of SGWT LGPL will be 2.4 with a synchronized 2.4 EE release. The target release date is November 14th. I realize this has been a long time since the previous release but you'll be happy to see the number of new features and numerous bug fixes that has gone into the 2.4 release.
Moving forward SGWT will continue to have regular releases on a 3 month (approx) schedule.
Posted by Sanjiv Jivan on November 04, 2010 at 11:48 AM EDT #
Is there any indication that LGPL 2.3 will be released at all and when if it is?
This is getting quite worrying!!
The formerly very regular LGPL updates have dried up!!
EVERYBODY is screaming for version 2.3, but nothing is happening! The only information was Sanjiv on his blog on 30. sept. promising a release a few days later!!
What is going on - is the release coming??
Is this a hint for serious developers to invest in SmartGWTEE??
...or force us to look at other frameworks!?!? :-(
I a sofware ingeneer living in munich and author of the library located here: http://code.google.com/p/gwt4air/ .
For the version 1.3 i d like to make the smart gwt library work inside air and would love to have some advices and feedback from some one of the smart gwt team. Since i did not know how to cantat one of them, this forum was my last chance.
Please feel free to contact me at jazzmatadazz@googlemail.com
Not sure if I am missing something here.... but with the nightly builds having moved to version 2.3 some time ago are we going to get an official non expiring release of 2.2?
This is of limited use to me as we have used "pro" tools in our codebase, and the EE versions are in different packages. This means that switching to the ee version is not quite a simple jar switch. I guess we are stuck waiting for the release unless we want to spend time making our code conditional on pro/ee, or come up with $$$ to pay for isomorphic development sooner.
Leave a comment: