No problem... now lets get some votes for that bug
I'd email Scott Violet directly... but I don't want to irritate the Sun engineers
better save that for when I have something more to offer.
I'm toying with the idea of getting set up to build Mustang... but the chatter I'm seeing suggests it's pretty late in the game for them to integrate outside code for the first release.
The performance is just sooo bad though. I know that quite literally my company has lost customers over issues with JFileChooser. First it was the sorting in details view (that Sun would not even acknowledge as a bug in the Windows look and feel - they call it a feature request!)... That's been fixed for Mustang finally (thanks guys), and I know they are at least trying to pay attention to some other look and feel fidelity issues... but the performance problem has been downplayed for so long... it's like they don't believe it's there... if yousearch the bug database for JFileChooser perfomance issues you will see tons of examples.. marked duplicates where they probably should be, then the duplicate get marked as could not reproduce, and it's all just washed under the table like nothing ever happened.
I saw one bug marked closed that indicated some new bindings to Win32 shell functions in Mustang were going to fix the performance.. but many builds after that "fix" the performance is still unacceptable.
On one hand we want to be as cross-platform ready as possible, on the other I'm getting lots of flack because of issues like this. At our weekly status meetings you should see the looks I get if I say I've upgraded the JRE for the next build... most of the people in the room take it as a sign of trouble. We've been burned by performance issues in the JRE before - with an indeterminant progress bar generating garbage very fast, then the GC kicked in at such a high thread priority that it starved device drivers and our video capture application drops frames. Customers expect it to run 24/7 to stream TV channels or archive TV broadcasts... they get mad when the system locks up in a few hours and it's all because of something horribly wrong in the JRE that wasn't like that in the last version.
Now we have some long awaited fixes coming in Mustang, but they've lost confidence, and if it only fixes half the bugs, they will think, "here we go again, another year and a half to wait before anything gets done about it." Then the "why aren't you using .Net?" questions start and we have to point out why we don't want to use .Net even though it will solve these issues (on Windows).
Can you tell it's stressing me out?