Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding an import feature #17

Open
dylan-chong opened this issue Sep 7, 2023 · 0 comments · May be fixed by b-inary/desktop-postflop#33
Open

Adding an import feature #17

dylan-chong opened this issue Sep 7, 2023 · 0 comments · May be fixed by b-inary/desktop-postflop#33

Comments

@dylan-chong
Copy link

I'm writing something that'll take a GGPoker hand history and have it spit out what i need to put into wasm-postflop:

  • oop, ip ranges
  • starting pot
  • effective stack (just want to confirm this is based on the stack size at the beginning of flop?)
  • possibly later: bet sizing (although at the moment it seems good enough to let the user decide)

That way, I don't have to manually enter the above things (mainly the chart)

If i could write some sort of import button that would take a hand-for-anaylsis in some format, which would include things such as the above (but be specific to wasm-postflop of course, or a solver format, if there is one)
It would be great if it could primary be a text field, so that the clipboard can be used for a quick workflow. (File support could be done at a later date)

I could then have my tool take a GGPoker hand and spit out the format for wasm-poker, copy it to the user's clipboard, then the user can go to wasm and paste it there.


my questions are:

  • would you be open to someone implementing such a feature? i'm really keen to have a go at it. keen to play with vue and some open source stuff. plus it don't think it will be terribly difficult
  • how would you like it to be designed? both in terms of ui and backend structure.
    • there's already a tree config load/save thing that i'm wondering if it should be built upon or not. i guess on one hand if we do, it would be harder to import tree config without wiping someone's range, and on the other hand it would be weird to have two different save/load features (one for tree config, one for the entire app)
  • as i implement it, would i be able to make WIP pr's so i can get feedback every now and again that i'm doing it the way you'd like it

Anyways, hope to hear from you soon!

@dylan-chong dylan-chong linked a pull request Sep 28, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant