Given my recent pull request: #24
Here were my goals and current comments / concerns after reviewing what was pushed recently:
Related Words Use Case:
Output related words to user AFTER they've clicked the translate button. No words will appear if no relevent related words (at developer's discretion) are provided.
If words appear, user may click on any provided word. That click will loop the Translation Use Case, so that word will appear in the input box and automtically have the translation version appear. This makes it similar to GoogleTranslate and is effecient on our end. *
My use case discussion points:
@AddisonLuo04 , since your use case translates words, could you help in letting me know which calls i should make given that a user clicks on it? That clicked word would still be a string object sent from the veiw to the interactor, so i'm thinking it'll be the same implementation as what you have now, but using different part of java swing to get it in our input boundary.
@AddisonLuo04 @sophieebyr Should we be combining the outputs of our use case? Cos retrieving the translated word, txt to speech file, and related words could all happen when the user presses the button. Here are possible ways to go about it:
[ ] All gets computed at the same time once user clicks translate. If user clicks on some audio button, speech to text will play. If user clicks on a generated related word, the translation use case is called again
[ ] Certain/All use cases computed individually: Translate button only translates. Speech to text button and generate related words button can only appear as requests once translation is done. These clicks let the program know to run our use cases. Still, UI feature for playing the audio file and clicking on a potential generated word must call for google translate again. Sophie and I would have to make a fail view in case no words come up or if audio file isn't processable.
Also, since this is all happening on the same panel, we'll need to manage that when constructing the view and such.
Side notes:
We can make a possible future feature where there are buttons / clarifying / warning text panels to confirm user's choice to even generate words, translate the clicked generated word, etc... but for time's sake and GUI implementation, we'll do less conditional cases.
Given my recent pull request: #24 Here were my goals and current comments / concerns after reviewing what was pushed recently:
Related Words Use Case:
My use case discussion points:
Side notes: