Hi Jack -- this completely depends on what you want to do. You can build a standard website using whatever tool/frameworks, etc. you want and you can embed GWT widgets into pages.
You could also build your entire site in GWT. Normally what people do is have a single entry point, and then dynamically add / remove components from the application based on user input. I like the idea of putting nearly 100% of the presentation logic into the client's browser and not having this served from the server. I have always found that model painful. This is the pattern I am using now for building a fairly complex application. The only thing I go back to the server for are stateless service requests for data (not presentation). I found the single entry point model slightly limiting, especially since I want to have a couple different entry points based on the initial URL ( e.g. http://host/app/admin or http://host/user/davis ). I posted a blog on how to use multiple entry points here: http://zenoconsulting.wikidot.com/blog:16 Regards, Davis On Aug 11, 6:09 am, Jack <[email protected]> wrote: > Hi Guys, > > I want to develop a portal in GWT 1.5. As per my knowledge we normally > create a GWT Application by creating a Entry Point Class and you put > all your logic in it. Now in the case of a website you need to go > through one link to another. > > Does it mean that i need to put all my login inside the single Entry > Point Class and change the put the different content on a Panel > everytime the user clicks on a Navigation Menu..? > > Kindly Help.. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
