>
> You probably mean this:
>
> http://www.gwtproject.org/doc/latest/DevGuideMvpActivitiesAndPlaces.html
>
>
Yes. This will also make the browsers forward/back buttons work to navigate 
through your app. And I would vote that feature 10000x more than having 
movable/resizable components (see bottom).

 

> But I see one problem: The server-to-client communication.
>
> Currently, my server maintains a list of listening clients and sends all 
> the events to each one of them. But you cannot tell when a client goes 
> away, even with server push technologies (comet and all that). Maybe you 
> can simulate this with a timeout or something like that: When there is no 
> activity for a while a client is assumed to have gone away and can be 
> removed from the list of listeners. This approach becomes worse, if you 
> have several tabs with several games. At least, I believe that. Maybe I 
> have not thought about it long enough... :-)
>

I don't see a real problem. If you use polling/comet you already have that 
"issue" and you should already have solved it. And even today I can use 
your app in multiple tabs, I just can't create these tabs by clicking on 
links...I have to create them manually (which would be solved by using GWT 
Places).
If you use Websockets you have a persistent connection between 
server/client and you know when the client closes the connection.

 

The goals I have in mind with moveable and resizeable in-browser windows 
> would be:
>
> Let users define the board's size and position additional widgets like 
> clock, history, etc..
>
>
> For example, having vector based graphics would enable the users to resize 
> the chess board. How could this be done better than with in-browser-windows?
>

Depends on what "etc..." means. A board + clock + history will nicely fit 
onto the screen without multiple in-browser windows. Actually the goal of 
your app, playing chess and communicate with others, is so simple that it 
should not need in-browser windows. Moveable widgets sounds like feature 
creep (http://en.wikipedia.org/wiki/Feature_creep) to me or you are trying 
to solve a problem that can also be solved by rethinking the UI layout in 
general. But thats kind of off-topic so if you want opinions on your app 
drop me a private mail.


-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to