works between linux and Android clients. Required renaming so struct
names and names of fields within match in c and java code. The point
is to test this as the foundation of rematch: now you have to type in
a deviceID in order to invite, which clearly sucks for users. Either
that goes away, or it's replaced with something that scans existing
games and lists past opponents as possible invitees.
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
instead wait until room name is tapped. (I did this in two places
though one might have been enough. On some devices anyway that
AndroidManifest change is needed to close a keyboard if it's open
prior to opening the activity.)
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
user-visible SMS, providing a URL same as email that launches the app
with a new game. Game works sending via NBS (data SMS) when both
devices are on GSM (T-mobile, anyway.) Plan is to use os version and
gsm info included in invite to warn user when the game can't
communicate, but that test isn't done yet. Also removed debug pref
allowing to force send by NBS.
(callback), since it's confusing to have the game offer to beam where
all that's being sent is the install URL. Hmmm -- maybe we do want
that. Consider....
Fix board sometimes coming up half-height by indicating that it should
never have a soft keyboard associated with it. It's otherwise getting
told its height is half what it should be, and I can't find any way to
get the layout redone when the keyboard goes away. (The keyboard in
this case is leftover from the previous activity.)
nagTime when saving a game that's some interval in the future IFF it's
a local player's turn. Set an alarm for the soonest nagTime. The
alarm seems to be firing at the right time, so what remains is to post
notifications. Also, rather than have two Receivers listening on boot
event added a new one whose sole job that is (and that kicks off other
stuff on boot.)
