📬 My Email

Email Management App

Note

💌 Under Development!

Completed Tasks

1. Initiate DBConnection with JPA/Hibernate using Singleton Design Pattern;
2. Building Business Entities hierarchies with JPA/Hibernate and then implement mapping between these entities;
3. Auxiliary classes with helper methods;
4. Class hierarchy for loading effect applied on starting the app and loading each menu/submenu, made with builder, factory and null object design patterns.
5. Custom message for header/logo with several different message styles: CLASSIC, MODERN, HACKER, ASCII ART;
6. Classes/interfaces that can deliver custom header with position, frame and styles designated for specific use;
7. Error classification along with severity defined in a standalone class hierarchy;
8. A separate class that delivers the loading bar and logo for when the app is started;
9. Custom printing of errors to console in a specific text frame;
10. Following SOLID, DRY, YAGNI and KISS design principles;
11. CPosition, HFrameWithContent, HMessage, Header Menu, AuxiliaryMessage and PrintMenu classes with associated methods along-with-builder and null object for each class;
12. Logo/Loading progress bar, Login Page and Main Menu page completed;
13. Various loading effects for moving forward, go back and quit;
14. Using Command along with a Builder design pattern to create the menu hierarchy and interactions with this menu;
15. Faceted builders were made for DB entities to clarify the construction of complex objects using fluent interfaces;
16. A configuration file was made as an .yml along with a POJO which reflects that config loaded with a ReadConfiguration class made as a singleton with an inner static class inside it;
17. Logging classes hierarchy was made with LogMessage in various formats (FormatConversion), like JSON, XML YAML and plain text. Now for each format, we have two methods for conversion, classic and pretty using ObjectMapper, YAMLFactory and XmlMapper. In other words we serialize each error/exception into a desired output and put it in a log file. With log4j we define only the file, rotation policies and where to print the errors, file and console. For building the LogMessage object we use a builder and when we define logging for a class we use Logging.class to access the methods and LoggingSettings to se the logger for each class.
18. To continue…interaction with DB and logging under development.

✅ Business Entities from DB point of view.

✅ A view of these entities and all java classes from this project but from Java Object-Oriented perspective.

✅ Logo and loading effect when the application is started.

✅ Completed loading effect.

✅ Starting page.

✅ Login page.

✅ Main menu page.

License

Released under MIT by @valentinsoare 📫 Contact me