Sam,

It's possible (and documented in the archives of this list somewhere)
to use a single EntryPoint to instrument multiple HTML pages with
GWT.  The mechanism is to have the EntryPoint code discover which HTML
document it is running in, and then switch on that.  But that's
probably premature optimization in your case, and I would avoid it for
now.  Simpler to create an EntryPoint/Module for each page you
currently have, and use Module inheritance to reuse code.

Keeping your current page structure is antithetical to using "DOM
manipulation"; you do one or the other or some mix of each, but it's
an architecture decision to subsume what are now two HTML pages into a
single HTML page with richer DOM control.  As Len says, you are
looking down a path now where it will be key to discover pages that
should be combined like that.  Call it Document Refactoring: moving
the boundaries of pages for a richer web experience in an evolutionary
way.  Get Martin Fowler involved; co-author a best-seller :-).

Walden

On Aug 27, 12:40 am, Sam <[EMAIL PROTECTED]> wrote:
> Hello all,
> Thanks a lot for your valuabel help. What are all the options that you
> said sounds quite appealing if I am going to create my product rt from
> scratch. But in my case , we do have a stabel product and we are
> planning to use GWT for some of the widely used pages as well as for
> the forthcoming enhancements. So if we are planning to go for using
> GWT with the exsisting web pages which are legacy web pages, we have
> to go for either DOM manupulation or we can write a class for each web
> page as per above discusion , rt ?
> Thanks
> Samir
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to