recent projects. You will learn a lot about practical way of
developing GWT Apps.
J.Ganesan
www.DataStoreGwt.com
Persist Objects directly in App Engine.
On Oct 2, 8:19 pm, "Brandon@MediciGroup" <bran...@thegreshams.net>
wrote:
> Dude, this contained one of the most enlightening things I've ever
> read on this issue; honestly, I hadn't quite realized until now that
> GWT isn't really it's own framework but rather more a framework to
> build custom frameworks with upon which you place your app; you build
> the middleware-framework, essentially.
>
> Yesterday I asked my buddy if there was any one single thing where if
> I didn't get it correct up-front to begin with (with respect to
> building a GWT-app) it would later cause me a lot of frustration in
> plumbing it in later on... he said the only thing he would advise I
> make sure to get correct from the beginning is Gin. He said if you
> start your app from the get-go using Ginjection, you can pretty easily
> plumb more of the newer GWT-features in later as you go without too
> much effort.
>
> I didn't quite understand it yet; but now I think I do -- that's
> because GWT isn't the framework, it's just a bunch of nice tools in
> your toolbelt helping you to build whatever framework you need. And
> I've already seen how some other GWT frameworks do things, so I have a
> target of sorts to aim at.
>
> Thanks for the reply -- you probably didn't quite realize that was the
> little piece I needed to make the lightbulb go off, but it was a big
> help.
>
> :)
>
> On Oct 1, 10:38 pm, Ashton Thomas <ash...@acrinta.com> wrote:
>
>
>
>
>
>
>
> > I wish Google would pay someone just to build sample apps (pick me, pick
> > me!). The GWT community needs someone like Ryan Bates:http://railscasts.com/
>
> > 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 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