Keeping track of both valid combinations and all lines in separate files is redundant. If we want to add a line and figure out all lines to combine with it, this can be done by taking the set of all lines in all combinations. Much cleaner back-end, and we can implement a GUI to handle choosing valid combinations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To handle choosing combos:
Everything in a list. Random selection that follows a distribution that falls off at higher numbers and never chooses n-1 where n is the length of the list. After combo is chosen, throw it on the end.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Phases can be handled by creating multiple textChooser objects. Fading can have a particular Couplet object transition between requests from two objects.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Question about phases: would it be possible to program it based on time or #of couplets chosen? So, either like a minute for a phase, or 10 couplets chosen for a phase, e.g.
And, can we program a "hard-transition" vs. a "soft-transition," i.e. jumping vs. fading between phases.
Stop me when I start asking for too much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nope, this is all great; keep on going! Better yet, throw your ideas up as tickets with the tag "feature request." Since we're doing a very nice modularized rewrite, we should be able to handle about anything. Remember to be clear and detailed in your tickets.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
General thoughts on programming decisions.
Keeping track of both valid combinations and all lines in separate files is redundant. If we want to add a line and figure out all lines to combine with it, this can be done by taking the set of all lines in all combinations. Much cleaner back-end, and we can implement a GUI to handle choosing valid combinations.
I think I understand this.
To handle choosing combos:
Everything in a list. Random selection that follows a distribution that falls off at higher numbers and never chooses n-1 where n is the length of the list. After combo is chosen, throw it on the end.
Got it.
Phases can be handled by creating multiple textChooser objects. Fading can have a particular Couplet object transition between requests from two objects.
Question about phases: would it be possible to program it based on time or #of couplets chosen? So, either like a minute for a phase, or 10 couplets chosen for a phase, e.g.
And, can we program a "hard-transition" vs. a "soft-transition," i.e. jumping vs. fading between phases.
Stop me when I start asking for too much.
Nope, this is all great; keep on going! Better yet, throw your ideas up as tickets with the tag "feature request." Since we're doing a very nice modularized rewrite, we should be able to handle about anything. Remember to be clear and detailed in your tickets.