From 75cb1cf85dacefce863cbacea57dff33ccf39e5f Mon Sep 17 00:00:00 2001 From: Benjamin Culkin Date: Sun, 7 Dec 2025 21:12:19 -0500 Subject: Part one of DB updates - Centralization Part one of the DB updates - switching to using a centralized source that uses a executor to parallelize. I'd imagine the performance would be more arse than it already was if I ran it now, which is why the next step is to change the save action to use SwingWorker and be parallelized per conversation. After that, set-up the UI for BatchTaskProgressPanel, and configure those SwingWorkers to use it --- firmal/src/main/java/module-info.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'firmal/src/main/java/module-info.java') diff --git a/firmal/src/main/java/module-info.java b/firmal/src/main/java/module-info.java index 7c434fa..7719a71 100644 --- a/firmal/src/main/java/module-info.java +++ b/firmal/src/main/java/module-info.java @@ -7,7 +7,7 @@ module firmal { exports bjc.firmal; - requires bjc.utils; + requires transitive bjc.utils; requires esodata; requires transitive java.desktop; requires json; -- cgit v1.2.3