Release candidate for Substance 4.3

The release candidate for version 4.3 of Substance look-and-feel (code-named Nairobi) is available. The list of new features includes:

Target date for release is April 14. Only defects will be fixed until this date.

Related posts:

  1. Release candidate for Substance 4.0 The release candidate for version 4.0 of Substance look-and-feel (code-named Key Largo) is available. The...
  2. Release candidate for Substance 4.2 The release candidate for version 4.2 of Substance look-and-feel (code-named Memphis) is available. The list...
  3. Release candidate for Substance 4.1 The release candidate for version 4.1 of Substance look-and-feel (code-named Lima) is available. The list...
  4. Release candidate for Substance 5.3 I am extremely pleased today to announce the availability of release candidate for version 5.3...

This entry was posted on Monday, March 31st, 2008 at 4:19 pmand is filed under Substance, Swing, UI. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

4 Responses to “Release candidate for Substance 4.3”

  • Bastien Says:
    April 29th, 2008 at 11:29 am

    I often use your substance library, but what i dont understand if why you put and put new features into your stuff but not even the least bug is fixed.

    Example: i wanto to align text in a jcombobox or in a jtable. Therefore i write my own ListCellRenderer etc… now the text is for example aligned right/center/left etc… but what happened too is following: the alternating row colors in the opened JComboBox or in the JTable are gone WHY ? This is a problem since Substance 3.0 and its still in 4.3…

    I will bookmark this URL to see wether you answer, because i am really interested in an answer. I could not find a forum where i could report bugs, so i post here.

    Kind regards,

    Bastien

  • Kirill Grouchnikov Says:
    April 29th, 2008 at 11:41 am

    Bastien,

    The best way to have a bug fixed is to report it. Version 3.0 was released in September 2006 and there is no need to wait so long to report a bug. That being said, this specific behavior is as designed. It is documented in question 13 of the project FAQ. If you do not extend the SubstanceDefaultListCellRenderer class that provides the striping support, you will have to do setBackground() on your own custom renderer yourself.

    If you have additional questions, you can use the project forums and mailing lists. These are accessible from the main project page (in the toolbar on the left hand side). If you want to post to the “users” mailing list, first you’ll need to subscribe to it. If you want to post to the project forums, first you’ll need a java.net user ID and then you’ll need to request an Observer role on the project.

    Thanks
    Kirill

  • Bastien Says:
    May 1st, 2008 at 12:16 am

    Thank you for your fast answer!

    I dont want to be a beta tester if this means requesting an Observer role due to lack of time. But I use your LnF in all of my applications. So sometimes i use version 4.1/4.2/4.3 etc because in each version something changes and a certain feature in my app doesnt work then anymore. For example i have JTextField/JTextArea with a Background Image. Fine with 4.1 but not 4.3 and i dont know why. Such questions i would like to have answered. So is there a forum where i can ask without being a beta tester? I have months ago registered about 3 times on your forum. After a certain time my user/pass did not work anymore same with java sun forum(another topic…) so i got sick of reregistering everytime. And the time i could login i havent seen any thread button to start a topic. But if you say now registering is fine and i can really start a thread i will of course register once again.

    Bastien

  • Kirill Grouchnikov Says:
    May 1st, 2008 at 3:22 pm

    Bastien,

    You don’t need to be a beta tester if you don’t want to. All i said is that java.net-hosted projects require you to have an Observer role to be able to post to the project forums. To be able to post to the project mailing lists you just subscribe to them and that’s it.

    Since you describe yourself as a library user, it would be nice (but not required) to provide feedback when things break. I do see some bugs in my testings, but those bugs that slip by have to be reported by the users. If nobody reports a bug, it won’t get fixed (unless i see it myself).

    So, one option is to try different releases and don’t do anything when you find a problem. Another option is contribute back and write a short e-mail, forum posting or even bug report (in the project issue tracker) that describes the problem and provides a small reproducible scenario. I don’t think that it’s too much to ask.

    Going beyond that, some users decide that in order to make sure that the bugs are fixed before an official version is released, it’s in their best interest to download the dev drops every once in a while to see if something is broken. That is your decision to make, and i don’t force anyone to be a beta tester.

    Sometimes java.net experiences short outages (an hour or two each week, mostly announced in advance). So, if you can’t log in, just try in a little while, or reset your password.

    Thanks
    Kirill