Closes#193
Closes#191
Closes#180
Closes#182
Closes#446
Closes#435
Closes#450

What is new? ✨

Project Structure

• sandbox
  This folder copies the structure ofview insidesource. It is supposed to help develop visual components using PyQt. Each file inside the sandbox must follow the patternsandbox_{component_name}, and be stored in the same project structure found onview, because it uses the structure to automatically build the components.

• source

  • commons
    Stores objects and configurations that are used across the software.

  • domain
    Keeps all the logical foundation of the software, and all necessary configuration to make the program run. It is the only part of the software that interacts with mathematical libraries.

    • boolean_expression_solver
      Is where all the logic to solve equations or inequalities is. Now it is complex enough to deal with multiple logical connectives AND, OR. It also knows how to prioritize expressions with the use of parenthesis.
    • entities
      Those are the objects from the domain of the project. In a very basic way, they are meant to replace the dictionaries and will be used across the software to perform necessary calculations.
    • [WIP]filter

  • view
    Contains all the visuals of the software and is the only part that interacts with PyQt library.

    • components
      Components encapsulate logic and contain elements. They act as higher-level UI constructs and may involve more complex interactions. Components are responsible for managing the behavior of elements and coordinating their actions.
    • elements
      Elements are minimal, basic components with common behavior. They are the building blocks of the UI and can make the use of items.
    • items
      Items are VERY minimal components, mostly used to display information and with almost no modifications from its parent Qt class.
    • pages
      Pages represent distinct sections of the application UI. Each contains one or more components and is responsible for displaying them. They are the content to be displayed inside the windows.
    • utils
      Contains methods, configurations, and constants that are required across the view.
    • windows
      Windows are what will actually be displayed as a complete component of the software. Its internal contents are pages, and they have extra configurations as of where it's going to be displayed, the window size and so on.

  • controller
    Makes the interactions between windows of the software.

• test
  This folder copies the structure ofsource, as each file containing logic is supposed to be tested to grant coverage.

Discoveries

1. CODE DOCUMENTATION
   Following the proposed pattern fromAdd code documentation #191 , the code is being documented. Some examples can be found atsource/view/components.
2. TESTS
   Apart from testing the logic fromdomain, components fromview are also being tested using PyQtTest.
3. ICONS
   Instead of downloading icons to be used in the software, it is now installed a libraryqtawesome that allows us to import icons directly.
4. COLORS
   Now we have a standardized way to use colors on the software, that adapts to the system's theme.
5. LOGS
   It was implemented a way to add logs at the crucial parts of the software to facilitate debugging once the executable is generated
6. CONFIG
   Stores the needed settings and information of the software, including, for example, the software version.