Nice GWT books you can find here ...
http://gwt-books.blogspot.com/
Cheers!
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send em
I for one don't want to write any more xml in my life than I have to. I
prefer my history service written in Java with auto completion, etc...
that's why I use Guice over other DI frameworks. I think your argument is
for declarative history service, which I could get behind. But the
particular xml
I would suggest watching Ray Ryan's videos on architecture from Google
I/O 2009 and 2010. That couple of hours will help you understand how
to solve a lot of your architecture/design problems.
On Jun 3, 4:22 am, ping2ravi wrote:
> This post i am not asking a problem but suggesting a feature reque
This post i am not asking a problem but suggesting a feature request
for GWT.
Now history stuff is working well, except few things(Basic GWT issue/
feature, because of its nature of converting java into javascript at
the time of compilation
Hello
You should check this book:
http://apress.com/book/view/9781590599853
And the associated website:
http://code.google.com/p/tocollege-net/
It mix both HTML/Freemarker templates with GWT modules.
Fred
On 1 juin, 18:02, ping2ravi wrote:
> Hi All,
> I am trying to create a website and stuck
I advise you to take a look at this book:
http://apress.com/book/view/9781590599853
and the related website:
http://code.google.com/p/tocollege-net/
The books explains how you can nicely split your web application
between HTML/JSP pages and GWT modules
Fred
On Jun 1, 6:02 pm, ping2ravi wrote:
check this out to give you some ideas about the history service..
http://code.google.com/p/handlebars/wiki/PlaceServiceOverview
On Jun 2, 8:08 am, ping2ravi wrote:
> Ya this approach looks good, thanks kozura.
> Now my app will look like this.
>
> myapp.html#type=profile&id=100 cal
Ya this approach looks good, thanks kozura.
Now my app will look like this.
myapp.html#type=profile&id=100 call server and get data
myapp.html#type=profile&id=234 call server and get data
myapp.html#type=profile&id=100 get data from cache and
refresh panel
I recommend you use a single widget with a method to change the data
showing in it (user profile, whatever). You have to be able to
populate it anyway, so that's no extra code. Caching panels is
generally a bad idea and a lot of overhead.
As for limiting server calls, you can cache the data retu
Thanks Shaffer/Sri,
I think i will go with GWT, the only thing is that i will have to
implement History which usually i dont do while writing the
websites(jsp/html page based). May be thats the reason i thought
writing history is overhead but i guess this over head will give me
good webapp/website.
There is a big difference between a website and a webapp, and deciding which
is more suitable for use case is more important than choosing the
technology.
*Website* is old-school. There are multiple pages, and moving from one page
to another is done via hyperlinks. Websites aren't interactive, and
Just a quick response...sorry I don't have time at this second for a
more thorough one...
Items 1, 2 & 3 are hardly unique to GWT...you've described the
standing challenges that DHTML/AJAX clients have dealt with for
literally the last 10 years. GWT does have some advantages,
especially in histor
Hi All,
I am trying to create a website and stuck with confusion over whether
to use GWT for presentation or JSP based framework like Spring MVC. I
want UI to be very user friendly,faster etc and this is possible with
GWT. But following problem comes with GWT
1) Book marking of any page. As GWT is
13 matches
Mail list logo
