smox / measuresmanager Goto Github PK

necessary tasks:
-> It should be possible to scroll the table if there are to many entries to display on one page.

Nice to have:
-> It should be possible to edit fields directly on double click
-> It should be possible to add a row

-> Add Version in Info section
-> Remove all unused Buttons/Menus/...
-> Refactor the code
-> Test the hole application
-> Fix bugs and test the hole application again until everything seems fine
-> Tag Version 1.0 in git
-> Deliver

-> TreeList instead of List
** The problem is, that only one measure per entry can be selected and this measure should have child measures.
** For every child measure (exception "special measures") it should be possible to add a text

-> Enhance seed data for standard measures
** Schwefelung, Anreicherung, Entsäuerung, Umfüllen, Vorfiltration, Flaschenfüllung (Gebinde 0,25; 0,75; 1; 2)

-> Add Special measure: "Umfüllen"
** For this task it should be possible to select n containers, the amount (in liters, default is max of source container) and create n entries for "Umfüllen".

For example:
5000L in Container 8
Add entry with measure "Umfüllen" -> Select Containers -> Add amount (if always full tank, except take max)
The program creates n entries with the given data.

Contraint: The sum of all destination containers can be less or equal the source container but never exceed it.

-> A new entry should be always a copy of the latest or the selected entry (except measures).

If you delete a Wine with entries assigned to it, following exception will be thrown:

Caused by: org.h2.jdbc.JdbcSQLIntegrityConstraintViolationException: Referential integrity constraint violation: "FK_QEBCX3HQ3DP84WQ56PEWYELO8: PUBLIC.ENTRY FOREIGN KEY(WINE_ID) REFERENCES PUBLIC.WINE(ID) (2)"; SQL statement:
delete from PUBLIC.Wine where id=? [23503-200]

Possible solutions:

1. Show an error message if there are entries left
2. Ask the user if all assigned references should be also deleted (CASCADE).

-> Add logging framework (e.g log4j)
-> Configuire log cycle (e.g. files not grater than 5 MB; only last 10 files)
-> Bei allen TODO Statements müssen Logging Statements eingebaut werden und evtl sogar bei allen Aktionen (Nachvollziehbarkeit).
-> Replace all todo statements with logging statements
-> Catch Exception e in main-function and log to file

--> It should be possible to add, edit and remove container

A container has following properties:
ID
Designation / Name
Type (plastic, stainless steel, wood)
Location (Droß, Stratzing)
Capacity/Amount

-> It should be possible to change the year
-> It is okay if the program restarts after the change

-> Every time when the application will be exited it should create a backup
---> If should check if there are differences between the last backup (md5 checksum) and if there are no differences it should not create a backup
---> The format should be ~/.MeasureManager/backups/db_yyyy-MM-dd_hh-mm-ss.db

-> Add Popup with Year (default: current year) and Wine (selected as default if a wine is selected)
-> Create a Table with all entries for a wine in DIN-A4 (Landscape) format
-> Data should be ordered by creation realizedAt date.
-> It is not necessary to add page count

-> Add check that a user cannot save (on editing) an empty wine name
-> Do not deactivate edit mode when input is invalid
-> Activate edit mode on double click
-> Add feature to undo current edit by pressing escape and deactive edit mode

-> Rename Button "Neue Maßnahme hinzufügen" to "Neuen Eintrag hinzufügen"
-> Minimum size for MainWindow
-> If you resize the MainWindow the splitter should not be moved (fixed offset)
-> Minimum size for left view of splitter
-> If you double click on an entry it should be possible to edit it
-> Set a home-directory for database and logs (~/.MeasureManager)
-> Rename database from test to MeasureManager

-> The application should be exported as a EXE file and runnable on Windows 10.
-> Add Splash screen
-> Add Icon

In the main window you can delete entries if you click on the red basket.
It would be nice if it would ask you if you really want to delete it before actually deleting it to prevent unintended behavior