How akiratomori/slang-word works
Project type and purpose
• This is a standalone Java desktop application (built on JDK 17) that uses Java Swing for its GUI.
• It implements a “Slang Word Dictionary” with features to search by slang or definition, view search history, manage (add/edit/delete) entries, and play quiz‐style games.
File structure
• Top level:
• Main.java – application entry point
• slang.txt, history.txt, mySlang.txt – persistent data storage (dictionary and user history)
• Slang-Word.jar – build artifact, plus misc. docs
• source/
• model/ – business‐logic and data‐access classes:
– FileManager.java (loads & saves text files)
– SlangWord, SlangWordList, ListSlang (data structures)
– HistorySearch (manages search history)
• util/ – ConsoleIO.java (console‐based I/O for testing)
• views/ – Swing GUI pages, organized by feature:
– search/ (SearchPage, SearchSlangPage, SearchDefinitionPage, HistoryPage)
– manage/ (ManagePage, AddPage, EditPage, DeletePage)
– game/ (GamePage, FindSlangPage, FindDefinitionPage)
• Home.java – the main launcher GUI that routes to feature pages.
Extract insights from the README
• Confirms MVC‐style separation: data (“data/” aka .txt files), utilities (“ulti/” → util/), and UI pages.
• Describes functional groupings: /search, /manage, /game.
• Deployment: run with “java Main” or extract the JAR.
Detail
• Break out major pages as subcomponents or group them under a “Views” container
• That ManagePage orchestrates Add/Edit/DeletePage dialogs
• Interactions during a quiz: GamePage → FindSlangPage/FindDefinitionPage → Model
• Don’t omit the user‐history flow: every search → HistorySearch → history.txt