Confused with the "module" concept in GWT.
7 views
Skip to first unread message
jack.tang
May 20, 2006, 4:22:34 AM5/20/06
to Google Web Toolkit
I looked some google web application and found that a lot of them keep
this layout
this layout
----------------------------------------
head
----------------------------------------
menu | <div id="dynamic-content">
items |
| </div>
----------------------------------------
>From my eyes, GWT is very good at this architecture and very clean.
Unfortunately, some are not, say two screens exist, one is sign on page
and the another is register page. Shoud I write like this?
<html>
<body>
<div id="dynamic-content"></div>
</body>
</html>
Or keeping two modules? what's your thoughts?
Thanks.
/Jack
Simp
May 20, 2006, 5:59:20 PM5/20/06
to Google Web Toolkit
In my opinion the strength of AJAX is enabling creation of web
applications that don't feel like webpages but real applications.
So you should probably play on that strength and incorporate a login
and registration into the application.
If you need one slot or more is up to your GUI design. ;)
applications that don't feel like webpages but real applications.
So you should probably play on that strength and incorporate a login
and registration into the application.
If you need one slot or more is up to your GUI design. ;)
jack.tang
May 21, 2006, 4:33:13 AM5/21/06
to Google Web Toolkit
Hi
I still care the url style much. IMO, http://xxx.com/account/login.html
and http://xxx.com/account/register.html are much better than
http://xxx.com/account.html#login, http://xxx.com/account.html#register.
I still care the url style much. IMO, http://xxx.com/account/login.html
and http://xxx.com/account/register.html are much better than
http://xxx.com/account.html#login, http://xxx.com/account.html#register.
Reply all
Reply to author
Forward
0 new messages