A suggestion (not obligatory) for FIS-GUI Claz HomeController.

[pwgit-create]

Extracting some of the functionalities into separate classes would help make the HomeController
class more modular and maintainable. Let's identify which parts could be moved out:

1. Scan Handling:

• The logic related to starting and stopping scans can be extracted into a ScanManager or similar class.

public class ScanManager {
    private final ScanService scanService;
    private final HomeScreen screen;

    public ScanManager(ScanService scanService, HomeScreen screen) {
        this.scanService = scanService;
        this.screen = screen;
    }

    public void startScan(boolean singleDirectory) throws Exception {
        boolean startScanSuccess;
        if (singleDirectory) {
            JTable table = screen.getMonitoredDirectoriesTable();
            MonitoredDirectoryTableModel model = (MonitoredDirectoryTableModel) table.getModel();

            int viewRow = table.getSelectedRow();
            if (viewRow != -1) {
                int modelRow = table.convertRowIndexToModel(viewRow);
                Optional<MonitoredDirectory> dir = model.getDirectoryAt(modelRow);
                startScanSuccess = scanService.startScanById(dir.get().id());
            } else {
                startScanSuccess = false;
            }
        } else {
            startScanSuccess = scanService.startScan();
        }

        if (startScanSuccess) {
            screen.showSuccess("Scan started successfully.");
        } else {
            screen.showError("Failed to start scan.");
        }
    }

    public void stopScan() throws Exception {
        scanService.stopScan();
        screen.showInfo("Scan stopped.");
    }
}

2. Polling for Live Feed Updates:

• The polling logic could be moved into a LiveFeedManager or similar class.

public class LiveFeedManager {
    private final ScanService scanService;
    private final HomeScreen screen;

    public LiveFeedManager(ScanService scanService, HomeScreen screen) {
        this.scanService = scanService;
        this.screen = screen;
    }

    public void startPolling() {
        // Implement polling logic here
    }
}

3. UI Updates:

• All UI-related methods could be encapsulated in a ViewManager or similar class.

public class ViewManager {
    private final HomeScreen screen;

    public ViewManager(HomeScreen screen) {
        this.screen = screen;
    }

    public void refreshView() {
        // Refresh various tables on the screen with updated data from instance variables.
    }

    public void clearLiveFeed() {
        screen.getLiveFeedText().setText("");
    }
}

4. File Operations:

• The file search and summary retrieval logic could be moved into a FileManager or similar class.

public class FileManager {
    private final ScanSummaryService scanSummaryService;
    private final HomeScreen screen;

    public FileManager(ScanSummaryService scanSummaryService, HomeScreen screen) {
        this.scanSummaryService = scanSummaryService;
        this.screen = screen;
    }

    public void searchForFiles() throws Exception {
        String query = screen.getFileSearchField().getText().trim();
        if (query.isEmpty()) {
            return;
        }

        boolean searchContainingInput = screen.getSearchContainingCheckBox().isSelected();

        try {
            String searchQuery = searchContainingInput ? "%" + query + "%" : query;
            List<File> fileResults = scanSummaryService.searchFiles(searchQuery, true);
            // Update the UI with search results
        } catch (Exception e) {
            screen.showError(e.getMessage());
        }
    }

    public void getSummaryForFile(File file) throws Exception {
        ScanSummary summary = scanSummaryService.getScanSummary(file.id());
        // Update the UI with summary
    }
}

Updated HomeController:

With these new classes, your HomeController class would look much cleaner and more modular.

public class HomeController {
    private final Logger log;
    private final ScanManager scanManager;
    private final LiveFeedManager liveFeedManager;
    private final ViewManager viewManager;
    private final FileManager fileManager;

    public HomeController(Logger log, ScanService scanService, ScanSummaryService scanSummaryService, HomeScreen
screen) {
        this.log = log;
        this.scanManager = new ScanManager(scanService, screen);
        this.liveFeedManager = new LiveFeedManager(scanService, screen);
        this.viewManager = new ViewManager(screen);
        this.fileManager = new FileManager(scanSummaryService, screen);
    }

    public void handleScanButtonClick(boolean singleDirectory) {
        try {
            if (scanManager.isScanRunning()) {
                scanManager.stopScan();
            } else {
                scanManager.startScan(singleDirectory);
                liveFeedManager.startPolling();
            }
        } catch (Exception e) {
            log.error("Error during scan operation: {}", e.getMessage());
            screen.showError(e.getMessage());
        }
    }

    public void searchForFiles() {
        try {
            fileManager.searchForFiles();
        } catch (Exception e) {
            log.error("Error searching for files: {}", e.getMessage());
            screen.showError(e.getMessage());
        }
    }

    // Other methods...
}

By breaking down the HomeController into smaller, more focused classes, each class has a single responsibility,
which makes the code easier to maintain and extend.