Open astephane opened 7 years ago
I think that the current design of having writeHand(), writeGameLine(), writeGameTable() in the Hand class and derive the Hand class for variants severly limits extensibility of the program.
IMHO, there should be a HandWriter class which would be initialized with the given Hand as reference which should be derived by room. But, the different variant supported would add some complexity by using multiple inheritance to factorize the code (crossref between HandWriter derivation for rooms and for variants).
That said, I'm only implementing export for PartyPoker. So, I add some writePartyPoker*() functions in the Hand class to limit the redesign of the code. But, if more work has to be done on this topic (e.g. export for other rooms), I think a re-design should be decided before added more code.
Instead of writing site specific code to re-assemble hands histories, we could add an option for saving the entire text of each hand during import. I believe that was the original intent with the table RawHands.
That would be a very nice feature. Especially if there were an option like "bulk export".
My problem is that I've lost some HH files which are in my FPDB database. I then need to re-create the original file.
Currently, Hand.handText exists but, unfortunately, its value is None.
Yes, we'd have to add an option to populate that table
I've finished (99%) PartyPoker export. It's pushed in my GitHub.
if a field is added to the database and the original hand text is stored and retrived via Hand.handText, the copy-to-clipboard feature could be rewritten outputing Hand.handText.
Add an "Copy to clipboard (original room format)" feature