Entire site on GWT?
1 view
Skip to first unread message
holden
Apr 14, 2008, 1:25:19 PM4/14/08
to Google Web Toolkit
Hi, I have a question
Is GWT suitable for writing an entire website? A site that has users
with login/passwords and everything.
Or is it designed just for a small part on the site that needs some
AJAX features?
Rodrigo
Is GWT suitable for writing an entire website? A site that has users
with login/passwords and everything.
Or is it designed just for a small part on the site that needs some
AJAX features?
Rodrigo
Axel Kittenberger
Apr 14, 2008, 2:15:08 PM4/14/08
to Google Web Toolkit
yes
romant
Apr 14, 2008, 2:16:21 PM4/14/08
to Google Web Toolkit
Hi Rodrigo,
> Is GWT suitable for writing an entire website? A site that has users
> with login/passwords and everything.
yes it is, that's probably the reason why so many people like it. I
personally implemented such thing. The best is that it behaves almost
like a regular standalone application, you do not actually need the
back, forward and refresh buttons anymore if you do not want. Have a
look at the basic simple example "Mail Application" to get the idea
(http://code.google.com/webtoolkit/examples/).
Cheers,
Roman
> Is GWT suitable for writing an entire website? A site that has users
> with login/passwords and everything.
personally implemented such thing. The best is that it behaves almost
like a regular standalone application, you do not actually need the
back, forward and refresh buttons anymore if you do not want. Have a
look at the basic simple example "Mail Application" to get the idea
(http://code.google.com/webtoolkit/examples/).
Cheers,
Roman
sloughran
Apr 14, 2008, 2:16:30 PM4/14/08
to Google Web Toolkit
It's most def. suitable for writing an entire website. GWT combined
with RPC's to the server can make for an extremely powerful website. I
am working on a full implementation now of a website that has users,
login and passwords, editing of preferences and requests and getting
status on servers. It's pretty much done with the exception of the
actual implementation of some async calls on the server. So far, there
hasn't been anything that I can't figure out to do in GWT.
with RPC's to the server can make for an extremely powerful website. I
am working on a full implementation now of a website that has users,
login and passwords, editing of preferences and requests and getting
status on servers. It's pretty much done with the exception of the
actual implementation of some async calls on the server. So far, there
hasn't been anything that I can't figure out to do in GWT.
holden
Apr 14, 2008, 2:50:46 PM4/14/08
to Google Web Toolkit
thank you all very much :)
Janusz Prokulewicz
Apr 14, 2008, 1:33:36 PM4/14/08
to Google Web Toolkit
The answer is YES :)
Michael Neale
Apr 14, 2008, 6:06:58 PM4/14/08
to Google-We...@googlegroups.com, Google Web Toolkit
Whole site is fine, if that is hat you want. Thing gmail for Ajax all
the way.
the way.
jhulford
Apr 15, 2008, 9:52:08 AM4/15/08
to Google Web Toolkit
One limitation you're going to run into is that the content of your
site will not be search engine friendly since it's all generated
dynamically via javascript DOM manipulation. For most people here who
are programming actual rich web applications that's not really a
concern. But if, say, you were writing a blog application (or a
company home page) it would be important to the users that the content
was searchable by search engine crawlers. Doing the whole site in a
traditional GWT way (loading content from Async calls etc) would
preven that from happening. You'd probably need to write some of the
code in whatever serverside language you'd prefer in order to show
existing/hostorical posts in the HTML when the page is requested so
that the content is searchable.
site will not be search engine friendly since it's all generated
dynamically via javascript DOM manipulation. For most people here who
are programming actual rich web applications that's not really a
concern. But if, say, you were writing a blog application (or a
company home page) it would be important to the users that the content
was searchable by search engine crawlers. Doing the whole site in a
traditional GWT way (loading content from Async calls etc) would
preven that from happening. You'd probably need to write some of the
code in whatever serverside language you'd prefer in order to show
existing/hostorical posts in the HTML when the page is requested so
that the content is searchable.
jhulford
Apr 16, 2008, 10:34:44 AM4/16/08
to Google Web Toolkit
I didn't mean this comment to be read as you can't have searchable
pages if you use GWT, you can. It's just something you need to make
sure you consider and an additional development step that you'll need
to plan out that you probably don't have to think too much about if
developing a traditional web-app.
pages if you use GWT, you can. It's just something you need to make
sure you consider and an additional development step that you'll need
to plan out that you probably don't have to think too much about if
developing a traditional web-app.
pinto
Apr 17, 2008, 8:50:34 AM4/17/08
to Google Web Toolkit
Hi,
So does it mean the pages created through GWT can not be crawled by
search engine crawlers ??
If that is the case then what are the steps we can take for "search
engine optimization" for example increasing the search ranking for
your site ??
regards,
Arvind
So does it mean the pages created through GWT can not be crawled by
search engine crawlers ??
If that is the case then what are the steps we can take for "search
engine optimization" for example increasing the search ranking for
your site ??
regards,
Arvind
Reply all
Reply to author
Forward
0 new messages