Comments on: Custom component states in Substance 6.0 http://www.pushing-pixels.org/?p=1602 Leaving no pixel behind Thu, 09 Sep 2010 18:02:18 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: Java desktop links of the week, January 25 | Jonathan Giles http://www.pushing-pixels.org/?p=1602&cpage=1#comment-11208 Java desktop links of the week, January 25 | Jonathan Giles Sun, 24 Jan 2010 20:31:12 +0000 http://www.pushing-pixels.org/?p=1602#comment-11208 [...] Grouchnikov has blogged about custom component states in Substance 6.0, the next release of Substance due out in a few months [...] [...] Grouchnikov has blogged about custom component states in Substance 6.0, the next release of Substance due out in a few months [...]

]]> By: Kirill Grouchnikov http://www.pushing-pixels.org/?p=1602&cpage=1#comment-11206 Kirill Grouchnikov Sun, 24 Jan 2010 02:12:26 +0000 http://www.pushing-pixels.org/?p=1602#comment-11206 Tom, This is the initial implementation, and only time will tell if it is better than the old component state layer. I did need to tweak a few core skins to make sure that the matching algorithm does not interfere with the intended visuals. Did you see the second example - using the EDITABLE facet in the Magellan skin? This is how you would do it in your own custom skin. Put EDITABLE facet in the on list for editable text components, and put it in the off list for uneditable text components. This way you will cover both types. If you see that it is not working, create a small (<100 lines) test app and send it to the "users" mailing lists or one of the project forums. Thanks Kirill Tom,

This is the initial implementation, and only time will tell if it is better than the old component state layer. I did need to tweak a few core skins to make sure that the matching algorithm does not interfere with the intended visuals.

Did you see the second example – using the EDITABLE facet in the Magellan skin? This is how you would do it in your own custom skin. Put EDITABLE facet in the on list for editable text components, and put it in the off list for uneditable text components. This way you will cover both types. If you see that it is not working, create a small (<100 lines) test app and send it to the “users” mailing lists or one of the project forums.

Thanks
Kirill

]]> By: tbee http://www.pushing-pixels.org/?p=1602&cpage=1#comment-11203 tbee Sat, 23 Jan 2010 07:16:50 +0000 http://www.pushing-pixels.org/?p=1602#comment-11203 Wow. Interesting approach; especially the "closest match" algorithm. I'm curious how this will work in practice and if it will save you a lot of work. And I'm curious if it will help me do that one thing I want; change the default background color of text controls in a skin. By registering a very specific ComponentState with a custom ColorScheme? Wow. Interesting approach; especially the “closest match” algorithm. I’m curious how this will work in practice and if it will save you a lot of work.

And I’m curious if it will help me do that one thing I want; change the default background color of text controls in a skin. By registering a very specific ComponentState with a custom ColorScheme?

]]>