More DRY needed #2

New Issue

str3tch · 2025-01-12T15:48:23+01:00

str3tch commented

2025-01-12 15:48:23 +01:00

Due to the fact that the amount of data needed for the application will grow and will always be large, I don't feel comfortable to maintain the one state of the application. That's why Component Architecture was chosen. In short every screen that is show is a container which has it's own components, thus giving us ability to maintain them independently.

Now we can clearly say that there're some duplicate functionality in different comonents such as table navigation, which consists of:

Go to next
Go to previous
Go to first
Go to latest

Implementation in each component does not differ except the data type inside the vector. Would be cool to have some sort of a wrapper that implements repeating functionality. Potential targets are:

table navigation
scrollbar changes
read data from file
write data to file
account parsing

Due to the fact that the amount of data needed for the application will grow and will always be large, I don't feel comfortable to maintain the one state of the application. That's why **Component Architecture** was chosen. In short every screen that is show is a container which has it's own components, thus giving us ability to maintain them independently. Now we can clearly say that there're some duplicate functionality in different comonents such as table navigation, which consists of: - Go to next - Go to previous - Go to first - Go to latest Implementation in each component does not differ except the data type inside the vector. Would be cool to have some sort of a wrapper that implements repeating functionality. Potential targets are: - table navigation - scrollbar changes - read data from file - write data to file - account parsing

str3tch added the

enhancement

help wanted

labels 2025-01-13 14:42:34 +01:00

Sign in to join this conversation.