Yeah, rails is a whole framework when GWT is nothing like that but samples that explain different things would help. The best thing about GWT seems to be the most difficult thing for developers: Just a tool to build some sick apps with custom frameworks built from the ground up where you do all the custom building.
Seems like this topic is coming up more and more.. GWT is used in too many enterprise applications where the developers who build sweet custom frameworks can't release the code. I have a framework that I built and it works great for me but I would never be able to release it. Even if i could, it would only help a subset of people using more or less the same app configuration while confusing the heck out of other people.
I could never go back to building apps without GWT but I also know the amount of work that has to go into building one of these bad boys
Resources like we see in the rails community will probably never exist for the GWT community because of the nature of GWT. Just too many variables. Best thing to do would be to jump on to one of the GWT frameworks that exist but then you miss out on what makes pure GWT custom apps great... I've seen GWTP mentioned several times.
Personally, I love working with my own framework. Best thing to do is to understand the available frameworks and whether they fit your project or if you need to build your own. Then you just have to roll your sleeves up and never look back
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/EEr7OT9dmgAJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment