The application that I'm working with has been around for a long time
and has used a few different web frameworks. The last one we adopted
(Tapestry 4) took that reverse approach of being the primary
framework and providing an adaptor for the previous framework. This
time around, I'm not looking
Hi,
On Jun 16, 3:14 pm, Brian Reilly brian.irei...@gmail.com wrote:
This is a technique that I'm finding useful for using GWT to implement
new features in an existing web application.
With multiple pages you will lose the gui state of the GWT-
application.
Multipages will have poor user timing
This is a technique that I'm finding useful for using GWT to implement
new features in an existing web application. The application already
has a configuration-driven menu system that effectively resolves to a
separate HTML file for each page. If I want to use GWT to implement
new pages, I need to
Hi,
could you please tell what the benefit of multiple host pages should
be?
To me it still looks like a misconception because of still sticking
with concepts of pre-AJAX era.
Stefan Bachert
http://gwtworld.de
On Jun 13, 1:33 am, Mark mark.java.john...@gmail.com wrote:
Hi,
There is now a
Hi,
There is now a project on Google Code (http://code.google.com/p/gwt-
multipage/) for managing multiple host pages. And, tutorials here -
http://claudiushauptmann.com/ and here -
http://uptick.com.au/content/managing-multiple-host-pages.
Cheers
Mark
--
You received this message because you
I had this problem some months ago.
I had several pages in the same project (GWT 1.4), sharing services,
code and images.
The first approach was to create several modules, but each module had
to be compiled separately.
The problem was that the whole compilation took num-modules times more
than a
Why have multiple entry points? Why not just the one that decides which
code to run?
On Fri, Mar 13, 2009 at 6:12 AM, Magius antonio.diaz@gmail.com wrote:
I had this problem some months ago.
I had several pages in the same project (GWT 1.4), sharing services,
code and images.
The first
One Abstract EntryPoint with a child EntryPoint for each form was OOP-
nicer,
but only one EntryPoint with a 'switch-case' will do the job.
On Mar 13, 11:56 am, Vitali Lovich vlov...@gmail.com wrote:
Why have multiple entry points? Why not just the one that decides which
code to run?
On
It seems like deferred binding would be a better approach from a whole
number of perspectives (although I'm not sure if you can define a custom
pivot point that's not based on user-agent or localization).
If you can figure out a way, you'll get performance benefits
(compilation-time determination
Hello!
My question is perhaps not so relevant for Ajax applications, but for
various reasons (including CMS), I would like to have a GWT
application with multiple pages. What is the best way to do this? I
have thought to have a GWT module for each page, but wonder if it is
practical? Grateful
10 matches
Mail list logo
