Spot on, Brian. The kinds of changes to Activities and Places we're contemplating for future versions of GWT are primarily along the lines of using annotations and generators to automate the creation of PlaceTokenizers and ActivityMappers, for example. We're not talking about wholesale replacement, as we strive for API backward compatibility with each release.
Also, we're thankful for a thriving community of 3rd party frameworks around GWT and you're always welcome to look "outside the box" it that suits your needs better. /dmc On Tue, Nov 30, 2010 at 3:19 PM, Brian Reilly <[email protected]> wrote: > There's a difference between "experimental" and "immature". I don't think > Activities and Places are experimental. They are building blocks upon which > more functionality can be built. While there may be bigger plans for future > versions of GWT, I'm glad that we have this much to work with sooner rather > than have to wait longer for a complete out-of-the-box solution. > I wouldn't take Ray's comments (from > http://groups.google.com/group/google-web-toolkit/browse_thread/thread/2173bd71a6289c84) > to mean that these features are experimental. More likely, you'll be able to > rip out a bunch of code when newer versions are released rather than have to > maintain boilerplate. > That said, have a look at the options, including other MVP frameworks, and > then choose what's going to work best for your situation. > -Brian > On Tue, Nov 30, 2010 at 2:34 PM, zixzigma <[email protected]> wrote: >> >> Thank you everyone for your wonderful insights. >> You provided very helpful suggestions and invaluable solutions to deal >> with the problem i described. >> >> I was going to implement some of the solutions offered, but this >> comment by Ray Ryan, >> got me very worried and kind of put me off. >> >> "The activity and place packages in GWT 2.1 are pretty minimal first >> stabs, >> kind of rushed out the door. One focus of GWT 2.2 will be improving >> their >> flexibility and reducing the boilerplate they require. " >> >> >> http://groups.google.com/group/google-web-toolkit/browse_thread/thread/2173bd71a6289c84 >> >> I am going to start working on a new project, and I'm afraid based on >> Ray Ryan's comment, GWT 2.1 MVP is too experimental, >> and there is a very high risk that GWT 2.2 would be dramatically >> different than 2.1, leaving me with >> a lot of boilerplate code to maintain ! >> >> I am leaning toward using GWTP, as Brian Reilly suggested. >> GWTP is more stable and mature than GWT 2.1 MVP, >> and it comes with many added features. >> >> I will keep you updated on this, as I continue with my project. >> >> Sincerely, >> zixzigma >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- David Chandler Developer Programs Engineer, Google Web Toolkit http://googlewebtoolkit.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
