Thanks Karthik for the reply.
Client side rendering (DOM manipulation) and Server side rendering
(HTML manipulation), certainly these
achieve rendering efficiency, but still programming approach is still
same, that client side event programming.
Server can get away from rendering totally, keepi
Or you could wait for server-side rendering to be supported by GWT. The GWT
team has dropped few hints in a couple of threads indicating that the day
could not be very far off when GWT does support server-side rendering. See
the following threads:
https://groups.google.com/forum/#!topic/google-
ya, even with another module we just get view, not model.
On Aug 6, 3:40 pm, dreamer wrote:
> Thanks for reply Stevko.
>
> Meaning big javascript verses bunch of html pages.
>
> would it be great if some we combine these ?
> In module html file we load entire java script, why not small chunk of
Thanks for reply Stevko.
Meaning big javascript verses bunch of html pages.
would it be great if some we combine these ?
In module html file we load entire java script, why not small chunk of
javascript
just to render that page? - for outside it is just a html page.
Will multiple modules serves
You may want to investigate other toolkit frameworks that fit your wants
better.
One that comes to mind is Closure which, I have read, allows for the
creation of pages in both the browser and server via the use of templates.
For clients that have a fast client, the browser loads javascript and
ren
Thanks Magno Machado Paulo.
You are suggesting to reverse the calls. Meaning first call RPC to
load model then gwt async to load
view&presenter. second gwt async can be called only on success of
first rpc for model. to make sure model is available in all
conditions.
So there are two async server c
You could use your server to fetch the data and embed it on the host page.
Then when the GWT code is loaded, it can read the data and render the screen
without making a new request on the server... For exemple:
User request http://your-app.com/?page=contactlist
The server receives the request, fetc
Thanks for the reply Magno Machado Paulo.
Code splitting is a console, documentation is telling on main page,
for every event click where
ever we need to load composite, suggested to use GWT.runAsync.
But the problem is I ended up getting Async call within Another Async
call, one for loading com
What it your app read a particular parameter on the URL that tell the app
what "page" should be rendered, then everytime you need to display a new
page, you generate a get request with the parameter for the page you wish to
display.
If you use runAsync on each page, the browser will always load on
Hi,
How about if it is possible to build Rich Internet Page (RIP), in a
more productive tool like GWT designer and eclipse plug etc
and server serving these pages using some web framework ?
My friend asked why don't you hand code html+ajax, sure that is
perfect, if that magic is possible with GW
10 matches
Mail list logo
