Wouldn't it be more performant to have one larger js file that gets downloaded once than 25 separate js files for each tiles page?
If it starts getting too big, you could aways introduce RunAsync and then as each jsp page downloads it would pull down only the necessary compiled javascript if it wasn't already available on the client. On Nov 11, 11:58 am, "Pablo G.F" <[email protected]> wrote: > I want to have several EntryPoints. My first idea was that having code > separate in several EntryPoints would generate so many app.nocache.js > as EntryPoints. I´d like this because I'm gonna embebbe this > javascript generated in jsp pages with Tiles pattern. So I ´ll just > use the exact javascript I need in each page. > I mean, I have a layout webpage and the content is update depending on > the webpage we´re linked. If that page uses GWT, I embebbe the > <script ...... application.nocache.js> instruction and then, all > references (id="x") are available, so the js generated by the > entrypoint can add the GWT widgets into that references. > > But I think I´m wrong because it seems that all entrypoints compile > into an only javascript file (named as the "rename-module" property > from the gwt.xml file). > Is there any way to have a javascript file for each entry point? The > multiple module solution is not valid for me because we´re talking of > using about 25 or so different entryponts... > > In case all entrypoints are compiled into a single javascript file, it > ´s ok, but that would make jsp pages heavier in javascript terms. > > Thank you -- 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.
