How hanlinag/point-of-sale-system works
Project type and purpose
• This is a standalone desktop Point-of-Sale (PoS) application implemented in Java using the MVC pattern.
• It serves two user roles: Admin (inventory, reporting, user management) and Cashier (selling items, card payments).
• It uses JavaFX (with JFoenix) for UI, MySQL for persistence, JasperReports for report generation, and supports barcode/QR scanning via a TCP-based Android scanner.
File structure
Top-level artifacts
• JAR libraries (JavaFX, JFoenix, JDBC, JasperReports, Apache Commons, POI libraries, XML Beans)
• UCSMPOS.sql (schema)
• enduserguide.pdf, README.md, LICENSE
src/ directory (MVC + utilities)
• /common – shared helpers (Common.java)
• /controller – JavaFX controllers (one per FXML view)
• /database – DAO/connection utilities (ConnectionUtils, MySQLConnUtils, DBInitialize)
• /functs – business utilities and helpers (QRReceiveData, ReportGenerator, EditingCell, SearchBarcode)
• /model – domain objects (ProductItem, Sale, CardUser, etc.)
• /ui – FXML view files (Admin_panel.fxml, Page_login.fxml, cashier_main.fxml, etc.)
• /jaspertemplate – .jrxml/.jasper report definitions
• /major – application entry points (Login.java, MainAdmin.java, MainCashier.java)
README for additional insights
• Confirms MVC design.
• Highlights core modules: Admin panel (inventory, categories, customers, suppliers, promotions, charts/reports) vs. Cashier panel (sales, card redemption/creation).
• External Android scanner pushes barcode/QR over TCP.