Yes, BlueSteel looks very nice now, especially with those rounded corners! When sitting at typing distance from the monitor, the pixels on the corner aren’t as noticable, at least to me. Perhaps swing doesn’t have proper anti-aliasing or something, or just not implemented in this version of Substance. There have been quite a deal of closed tickets [in Substance project] that regard fixing memory leaks and what-not, so performance and reactiveness should have improved. I’m hoping someone picks it up and keeps improving it.
Regarding the Spark freezing when switching from Substance skin to JTattoo skin… yes I’ve noticed the “Change Now/Apply” button causes a freeze. I’ve also noted that even in JTattoo, clicking the “Change Now/Apply” button does not always cause each window element to properly pick up the new theme (probably depends when they get redrawn in memory). Sometimes text highlight for example will stay on the old color scheme, or window backgrounds, etc.
Perhaps it may be worth making Spark auto-logout/back-in upon clicking the “Change Now” button in order to guaruntee all window elements reflect each LaF or Color change? This would make clicking the “Change Now” button expensive, but perhaps would make for a better UX since they wont get the freeze from Substance or partial LaF’s applied from JTattoo?
Stange on the default skin change. I don’t see anything in the SPARK-1539 patch file that would have changed this? I myself have been running the Fast LaF for a while and have gotten pretty fond of it… did it perhaps default to that?
And the merge conflict will be due to my current workflow… and I’m not sure how to get around it unless someone has a suggestion? Since I’m posting patches, then I don’t know which patches will be applied in which order, or if they will be applied at all (refactored, rejected, etc). So I can’t really continue to work from my working directory since then each patch would compound on the previous. Instead I’ve been making a new local copy of the Trunk and working from that to create each patch independent of each other. This will cause a merge conflict, but in Git at least it would be auto-resolved and merged. Does SVN not have this ability? Or should I change my workflow somehow?