Thank you very much Rui, and honestly, I think it is useful.
It does not get muddy due to excess colors, plus the user can decide what color to put (in my case I am going to use very saturated tones for tracks and more pastel tones to identify Midi and Audio) so that the app does not turn into a psychedelic rainbow :).
I'm trying to understand how Qt works, in case I can help, make proposals with code and not burden you with work, or simply to customize Qtractor to my liking.
I come from web development and graphic design.
I was surprised that although Qt tries to separate the structure of the interface with XML from the "logical" code with the .ui... it does not manage to do so at all. And if I understood it correctly, it is more of a help that is later translated into C or Python code (depending on what you work with), than a true structure.
In web design everything is much more separated. The entire structure is accessible.
Form structure: Html (includes classes and IDs to be manipulated). There is no logical code or reference to shapes, sizes, colors (you can have them but it is not recommended).
Behavior: Javascript (full access to structure, with its classes and IDs)
Visual style: CSS (full access to structure, with its classes and IDs)
This makes everything much more versatile and cleaner.
The html reads clearly and you understand the entire structure of the elements.
The programming is totally separate. You access without having to touch the Html, the same with the visual CSS part.
Now I understand that any small change really becomes difficult for you.
Thank you very much Rui, and honestly, I think it is useful.
It does not get muddy due to excess colors, plus the user can decide what color to put (in my case I am going to use very saturated tones for tracks and more pastel tones to identify Midi and Audio) so that the app does not turn into a psychedelic rainbow :).
I'm trying to understand how Qt works, in case I can help, make proposals with code and not burden you with work, or simply to customize Qtractor to my liking.
I come from web development and graphic design.
I was surprised that although Qt tries to separate the structure of the interface with XML from the "logical" code with the .ui... it does not manage to do so at all. And if I understood it correctly, it is more of a help that is later translated into C or Python code (depending on what you work with), than a true structure.
In web design everything is much more separated. The entire structure is accessible.
Form structure: Html (includes classes and IDs to be manipulated). There is no logical code or reference to shapes, sizes, colors (you can have them but it is not recommended).
Behavior: Javascript (full access to structure, with its classes and IDs)
Visual style: CSS (full access to structure, with its classes and IDs)
This makes everything much more versatile and cleaner.
The html reads clearly and you understand the entire structure of the elements.
The programming is totally separate. You access without having to touch the Html, the same with the visual CSS part.
Now I understand that any small change really becomes difficult for you.
Thanks again for everything :)