[Kleopatra0]

diana_eva, on 2020-May-14, 07:08, said:

You are right, and this is all far from perfect...

It's inconvenient to have to jump back and forth between servers.

Sorry about that. It's not perfect and we are aware. Our team is working on better integration.

I do apologise, I didn't mean to be rude or nasty, just pointing that the new solution is not perfect. Actually we should be grateful that BBO exists. As humans we tend to be always unsatisfied...

[barmar]

westwind3, on 2020-May-14, 10:48, said:

Mr ( or Madam secretary )
can I add a few more little niggles
1) The UNDO button , that should be right up on the table beside the claim button, impossible now to hit an immediate, obvious misclick.
2) Why only list events with a 2-hour window. In the past ( and I must reveal myself now as PC version user ) , would commonly book Speedball , many hours ahead
3) The bidding panel N S E W why not put the names in , even if it truncates to 4 characters. How many times do I have to do a double-take , who bid what ?
4) The claim button , instead of "I claim 7 of 9" , making it quite clear that 2 are conceded, you get "I claim 7" and now you have to carefully do some math.
5) Please put BBO "time" on the window bar. Instead of trying to figure out if 2PM Speedball is my local 7 or 8 , I will know it is in 40 minutes time

Do you have the ear of BBO ,if you add these to your wishlist

None of these things have anything to do with the split between the casual and tournament servers. They seem to be complaints about the HTML version.

[barmar]

chmtc, on 2020-May-14, 23:31, said:

Consider for example AWS solutions

We use AWS and Heroku for some of our services.

Redesigning the main server to run in the cloud would be a huge project. It's just not designed in that way. The casual/tournament split we did last week took a week of programming, and as can be seen it leaves much to be desired.

A totally new architecture in the cloud would be even more incompatible with the old clients.

We do have plans to make more incremental changes, splitting things up into more micro-services. But it can't be done all at once.