Projekct refactoring
-
Hi,
I have one big class for reading / writing settings from / to device, it is backend for qml too.
It conteins Q_PROPERTYS, fields, slots, methods, signals etc. for settings group - like uart, server settings ... n.
Class still growing and won't stop soon. Spliting it to small backend class for each group is good idea? App use tcp / serial communication in separate thread.Mam moc jak Harry Potter, w zębach mogę przenieść hotel.
-
Hi,
I have one big class for reading / writing settings from / to device, it is backend for qml too.
It conteins Q_PROPERTYS, fields, slots, methods, signals etc. for settings group - like uart, server settings ... n.
Class still growing and won't stop soon. Spliting it to small backend class for each group is good idea? App use tcp / serial communication in separate thread.What is "big"? How many LoC do you have?
It's always possible to outsource some stuff, but the question is, does it make sense? Does it increase the readability?
-
<400 in .h
<2000 in .cppMam moc jak Harry Potter, w zębach mogę przenieść hotel.
-
<400 in .h
<2000 in .cpp2000 lines in code file is not that much, if you have a good structure.
-
Ok thx, soo i will stay with this structure, ofc app files still growing with new functionalities - device controled by application firmware is also develop
