Adding themes to a native Windows app isn't simple. Particularly in this case where there are lots of standard Windows controls combined with custom coded controls. To theme the whole app (including all dialogs and menus) is going to take a long time to do. That's assuming Cakewalk decides to theme the entire app and not just the track and console views.
 
Once done, however, any new controls will (should) automatically be theme-aware. That's when you can build an easy to use theme editor. Until then, hardcoding is probably the only way to do it.
 
Regards,
Dan

dcumpian
Once done, however, any new controls will (should) automatically be theme-aware. That's when you can build an easy to use theme editor. Until then, hardcoding is probably the only way to do it.
 

Bolded for truth.  It takes a while to refactor 20+ years of legacy UI.
 

Adq
It is base not only on this case, but the whole last years conception. There is too many hard-coded things in Sonar and there is lack of crucial settings, because... and so on. May be it changes, but there are more words than actions. And read this:
http://forum.cakewalk.com/FindPost/3420226
I'm very afraid of this "We're about to move on to discussions" and "But we may introduce".

We already have an internal tool for designers/developers, but it's not ready for primetime. Hence "we're about to move on to discussions" about this. There's nothing nefarious here, it's just part of the monthly product cycles. Once the integration between SONAR and the theme tool is ready, if a color bothers someone, they'll be able to easily change it and share it with others.

"But we may introduce enhancements and expansions over time." is just that. We're already working on another theme, but themes themselves will need to adapt along with application updates. For instance, we'll need to properly handle greater than 4k resolutions soon, and themes will need a bit of tweaking as a result.
 
Most importantly themes are a community driven feature, and this all depends on feedback cycles. We need to be open to introducing new enhancements over time. 

Good to hear it, thank you for clarification.

Seth Kellogg [Cakewalk]
Most importantly themes are a community driven feature, and this all depends on feedback cycles.

What about new Feedback Portal? Is it gonna be ready anytime soon?

Adq

Seth Kellogg [Cakewalk]
Most importantly themes are a community driven feature, and this all depends on feedback cycles.

What about new Feedback Portal? Is it gonna be ready anytime soon?

I don't have a date for you, but I know it's being worked on.
 
Our Webteam is handling this task, and I don't regularly sit in on those meetings to know for sure.

Well I guess one can argue that CW won't be thinking of developing a public theme editor if SONAR was to be EOL'ed on June 1, based on some of the crazy theories floating around in various threads. Just saying.
 
I just hope the theme editor does more than just allow changing colors of flat controls.

Ah, ok, good, thank you!

SilkTone
Well I guess one can argue that CW won't be thinking of developing a public theme editor if SONAR was to be EOL'ed on June 1, based on some of the crazy theories floating around in various threads. Just saying.
 
I just hope the theme editor does more than just allow changing colors of flat controls.

Flat/3d can be controlled via the images used in the theme. For example, we (or the user base) could potentially offer a flat mercury and/or 3d tungsten down the road.

Honestly, I'm really interested to see what Panup and the community comes up with.  

Seth Kellogg [Cakewalk]

SilkTone
Well I guess one can argue that CW won't be thinking of developing a public theme editor if SONAR was to be EOL'ed on June 1, based on some of the crazy theories floating around in various threads. Just saying.
 
I just hope the theme editor does more than just allow changing colors of flat controls.

Flat/3d can be controlled via the images used in the theme. For example, we (or the user base) could potentially offer a flat mercury and/or 3d tungsten down the road.

Honestly, I'm really interested to see what Panup and the community comes up with.  

Excellent, thanks Seth!

Seth Kellogg [Cakewalk]
 
It is base not only on this case, but the whole last years conception. There is too many hard-coded things in Sonar and there is lack of crucial settings, because... and so on. May be it changes, but there are more words than actions. And read this:
http://forum.cakewalk.com/FindPost/3420226
I'm very afraid of this "We're about to move on to discussions" and "But we may introduce".
 
We already have an internal tool for designers/developers, but it's not ready for primetime. Hence "we're about to move on to discussions" about this. There's nothing nefarious here, it's just part of the monthly product cycles. Once the integration between SONAR and the theme tool is ready, if a color bothers someone, they'll be able to easily change it and share it with others.

"But we may introduce enhancements and expansions over time." is just that. We're already working on another theme, but themes themselves will need to adapt along with application updates. For instance, we'll need to properly handle greater than 4k resolutions soon, and themes will need a bit of tweaking as a result.
 
Most importantly themes are a community driven feature, and this all depends on feedback cycles. We need to be open to introducing new enhancements over time. 

Thanks so much for thyour post on this Sethh!