Hi Csaba,

That's not really how GWT is best used. It's better to look at a GWT
app as a single "page" containing a number of widgets. For example, if
you have an number of different forms you might implement each one as
a separate Composite and stack them in a DeckPanel (or TabPanel etc)
or generate them on demand in a single container widget. You might
drive this from some navigation widget based on e.g. a menu or tree.

If you have a large chunk of static HTML content you need to include
somewhere you can put it in a Frame widget from which it works like
straight HTML pages. I did this for some help files for example.

Technically you can build your site in a traditional manner using HTML
pages and embed separate GWT mini-apps in these pages as required.
This might be a viable strategy if a) it is an open site with a lot of
static HTML content and no overall security framework, and b) there
are a limited number of mini-apps that really are completely separate
from each other. However as soon as these mini-apps need to
communicate with each other and share state you will run into trouble.
For example implementing user sign-in, permissions and preferences
across the site would be more difficult.

regards
gregor



On Oct 22, 8:24 am, "Csaba Kávai" <[EMAIL PROTECTED]> wrote:
> Hi guys,
> I am wondering what the main concept is to build a major website with GWT? I
> mean if there are a lot of html files, how do you build it or get control of
> the widgets of the them? It should be a natural way that each html file is
> connected with an entrypoint where the you build the final site or get
> control of widgets with wrap method. However if you do this in one module,
> than each entrypoint is being loaded when a new html file of the module is
> shown. As a beginner a made a helper class that implements EntryPoint and
> quits when not the corresponding page is being loaded:
>
> public abstract class MyEntryPoint implements EntryPoint {
>     public void onModuleLoad() {
>         String className = getClass().getName();
>
> if(Window.Location.getPath().endsWith(className.substring(className.lastIndexOf('.')+1)+".html")){
>             loadPage();
>         }
>     }
>
>     protected abstract void loadPage();
>
> }
>
> Of course this could be done by making as many modules as many html files
> you have. Is there any other solution?
>
> Thanks,
> Csaba
--~--~---------~--~----~------------~-------~--~----~
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