News for hackers. Stuff that matters.
Re:One Year Later: Review of PyCharm 2.7 from a Vim User’s P... by sigzero on Saturday June 15, 2013 @09:13AM (#5884919)
Try adding these lines:

  -Dawt.useSystemAAFontSettings=on 
  -Dswing.aatext=true
  -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel
to the pycharm64.vmoptions file.
Re:One Year Later: Review of PyCharm 2.7 from a Vim User’s P... by stoolpigeon on Saturday June 15, 2013 @11:12AM (#5885192)
When I originally tried these, they did nothing for me.

And now that I think about it, I wonder if it had something to do with my KDE setup and how it handles GTK stuff. That could be another thing that changed for me that fixed it. Because it did get better recently but I don't know why.

The issue is with Swing, not JetBrains products alone and I sympathize with them but I can say it was bad enough for me that I just couldn't use their stuff on my primary work machine.

Re:One Year Later: Review of PyCharm 2.7 from a Vim User’s P... by Erwin on Saturday June 15, 2013 @10:15AM (#5885070)
Hmm, I have a hard time seeing a difference, but this is a large screen and a decent computer. What uglieness should be fixed by this? I use Oracle Java 1.7.0_21-b11 64-bit. Those hundreds of Java flags are a mystery to me.
Re:One Year Later: Review of PyCharm 2.7 from a Vim User’s P... by AYBABTME on Saturday June 15, 2013 @10:56AM (#5885158)
It tells AWT to use anti-aliased fonts, same for Swing, and then set the LookAndFeel to GTK.