Explore AI tools for assets and styling

[ctm]

See if there are easy wins to allow me to recover geometries and write SASS code for asset placement, controls, etc.

I've got a handful of screenshots from my A9+ and my iPhone 16e. See what tools can do with them. See if I can do a rigged demo soon, to aid in describing what we can do in a Kickstarter.

Mb2 should be skinnable sooner, rather than later. Although I lack graphic design or even an artistic eye, if there are tools that can create geometries for the nick chip box, card placement, buttons and checkboxes and/or generate a background, I should at least know what they are and what they cost (with luck, I can do a rigged demo using free tiers).

Start with tools mentioned in this Medium AI-Generated CSS That Actually Works: Tips, Tools & Best Practices article and with Workik.

[ctm]

I did a little work on this yesterday and got good enough results for the immediate buttons that I'm going to add a @media (min-aspect-ratio: 3/2) block to table.scss that contains the CSS I got back. I'll also hack table/graphical.rs to add the needed ids and classes in. I'll do this in the ai-1791 branch and keep it to myself for now. I think that the larger controls on my A9+ tablet will then inspire me to grab coordinates for nick-chips and cards. It'll also allow me to write a semi-informed status report.

[ctm]

I've done enough that I think I can start using it on my A9+ this evening. It'll be a bit ugly and jarring, but it should inspire me to get to a nice proof-of-concept fairly quickly.

Here is some low hanging fruit

• immediate buttons:
  • Stud
    • Bring-In
    • Complete
  • slider doesn't move (I had fixed that yesterday, but the change probably didn't make it to table.scss)
  • different gradients
    • check
    • bet
  • slider caps
    • +
    • -
    • make them move by big blind amounts
    • disable them as appropriate
  • hide the log when it's time to act
  • different colors for mini buttons (Min, 50%/3 BB, Pot) depending on whether there's action
    • default is yellow
    • orange if there's action
    • red if it's an all-in raise
  • different color for raise button depending…
  • switch from 50% to 3 BB when appropriate (now Switch from "50%" to "3 BB" when appropriate #1797)
  • Fix so when it's time to draw, the chat box disappears
• advanced checkboxes:
  • add ids
    • Fold
    • Call
    • Raise
  • add styling
    • Fold
    • Call
    • Raise
  • Log
    • styling
    • scrolling
      • Figure out why scrolling doesn't happen automatically on my A9+ after sending a chat message (now Chat line doesn't always cause scroll down in experimental UI #1796)
    • chat input
      • Add click-handler
        • Have it add enable-input to chat-and-input
        • Have it set focus
      • Make existing onkeyup Enter handler remove enable-input from chat-and-input

[ctm]

Embarrassingly, the Action component doesn't know what the big blind is. Instead, it receives an inputs property that contains some preset-buttons, one of which is min and the other is max. That's been sufficient for the controls that we've given the users in the past. Logically, it makes sense for there to be a big_blind property that is an Option<ChipCount>, but surprisingly, Table doesn't explicitly have that, either. OTOH, it should be trivial to be able to add a big_blind() function that gets the info from the table's ActionTracker, although even ActionTracker only currently has big_blind_during_first_round. IOW, it's a PITA, but the information is there.

[ctm]

I've gotten all the PS buttons, checkboxes and log placement and styling done for my A9+ tablet. The log doesn't scroll properly, nor is there a way to type in chat (because that's. done via a separate window/overlay @ PS). We currently don't have a place for the "any" checkboxes: bet-or-raise-any, call-any, call-any-or-check, raise-any, but I can add them in later.

FWIW, I don't think we gain anything by disabling the slider caps, but I'll leave that as an unchecked todo checkbox for now.

Getting the log to scroll (and probably getting back the ability to chat) seems like a good stopping point. I feel bad that I worked on this today (a high caffeine day) rather than working on business stuff, but I'd like to update the Coming Soon section of the Players' Manual and add a UI paragraph and get a status report out and I wanted to get the PS style controls working for this evening's game.

[ctm]

I got the chat log to scroll and made it so clicking on it brings up a text input field and it seems to work fine with a web build, but the text doesn't scroll to the bottom when I send a message when on my A9+ tablet. I'll check and see what happens on other platforms. It shouldn't be hard to fix, but it might be time consuming, depending on where all it happens. Android builds are currently the slowest, probably because it builds for multiple architectures at once.

[ctm]

I've merged and deployed this code, even though it's not finished. It's hidden behind an "experimental" preferences setting (#1793). I'll keep this issue open until I "Fix so when it's time to draw, the chat box disappears". I'll then probably turn the two remaining checkboxes (switch from 50% to 3 BB when appropriate and Figure out why scrolling doesn't happen automatically on my A9+ after sending a chat message) into issues of their own.

[ctm]

Removing the chatbox when we have a drawing button (and not checkbox) is tricky. I think we'll need to hoist the call to discard_controls to before we compute background_class and have discard_controls return both Html as well as some sort of flag that says whether a button has been presented rather than a checkbox. I can't say I'm happy with that solution, but I don't think it's one that merits sleeping on.

[ctm]

I implemented and tested the solution I described in my previous comment. Deploying now.