How philongcode/k17_dp_ck works
Project type and purpose
• This is a Java desktop application following a layered, MVC-style architecture.
• Its primary purpose is to manage “Room” entities (ComputerRoom, LectureRoom, LaboratoryRoom), including operations like “Delete Room” and “Open Confirmation Dialog.”
• The README (“Design Pattern”) hints that this sample demonstrates design patterns (Observer, Factory, Use-Case, DAO/Gateway).
File structure
• Top-level src/ package is divided into four layers:
• Observer
• business
• persistence
• presentation
• “Observer” holds Publisher/Subscriber interfaces for event dispatch.
• “business” contains use-cases (DeleteRoomUsecase, OpenDialogConfirmDeleteRoomUseCase), DTOs, entity classes and a RoomFactory.
• “persistence” contains Gateway interfaces and DAOs (MySQL or MockData) plus ConnectDB utility.
• “presentation” holds Controllers, Models, View classes (Swing UIs), and View-level DTOs.
• Main entry points: MainUI.java (application window) and Main.java (app launcher).
Insights from the README
• The goal is to showcase design patterns and a clean separation of concerns.