From: Chris S. <chr...@gm...> - 2011-03-18 12:58:53
|
I'm fine with having this as streamlined pbem, but my main interest is in having it support real-time play. -- Chris Please consider the environment before printing this e-mail. On Fri, Mar 18, 2011 at 3:45 AM, Phil Davies <de...@gm...> wrote: > I'd definitely favour the least intrusive approach, anything that > could steal focus is considerably annoying and this is treated > differently across different OSes. Certainly if you can turn on or > off notifications that would be nice, I'm prone to playing in spare > moments so the ability to just bring the screen up and see if it's my > turn yet rather than being prompted for it would be great, I > definitely see this more as 'streamlined pbem' rather than an attempt > to do proper realtime play (which will be better suited to a proper > client/server architecture) > > Phil > > On 18 March 2011 01:56, Rick Westerman <wes...@pu...> wrote: > > Lots of interesting comments on this proposal. Erik's willingness to > implement this -- in some form and then make it better -- is greatly > appreciated. > > > > My gaming partner and I looked over Erik's proposal and it seems fine > to us. Further refinements could include a 'poke' option -- a way to remind > a person that it is his turn (although I see no way to do this given the > current Rails method of sharing files; it seems more doable in a > client-server type of arrangement.) Another refinement might be a way to > do messaging among the players -- although once again this seems more > suitable for client-server.) > > > > Another suggestion would be to have rapid checking for new files and > then slowing down later. In other words in immediately after submitting > one's turn then checking every 10 seconds (as an example) may not be too > often. On the other hand if the other players are taking time to complete > their turns, then checking every 30 seconds or so should be fine. We are > thinking of those sometimes interminable stock rounds that can occur where > is it might be "player A pass", "player B pass", "player C" pass, "player D > do something", "player A pass" and so on until "player D" runs out of things > to do. If the time delay between each player is 30 seconds then the SR > could take a long time. > > > > > > As for the following. > > > > > > ----- Chris wrote: ----- > >> Actually, I would be fine with Brett's more graceful approach. My > >> answer was that a popup would suffice, not that it is preferred. I'd > >> rather have the notification area solution, as long as it only bugged > >> me when it was my turn. > > > > Bugging when it is person's turn and being silent (or at least quietly > in the log file) when it is not is important. > > > > > > Thanks again, > > > > -- > > Rick > > > > > ------------------------------------------------------------------------------ > > Colocation vs. Managed Hosting > > A question and answer guide to determining the best fit > > for your organization - today and in the future. > > http://p.sf.net/sfu/internap-sfd2d > > _______________________________________________ > > Rails-devel mailing list > > Rai...@li... > > https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |