5 ms·
Then all we'll need is a great cross-platform UI toolkit. People have been working on them for 20 years but I not sure if anything really works well.
by melling 14y ago
Then all we'll need is a great cross-platform UI toolkit. People have been working on them for 20 years but I not sure if anything really works well.
- username111 14y agoThis is the reason I don't use jetbrains products, I use linux and the Java font rendering is absolutely awful, I've tried all the fixes and I can't find any of them pleasing enough to use.
- kunai 14y agoWhy don't you try Qt Jambi or GTK+ if Swing on Linux is awful? GTK integrates perfectly with Linux if you're using GNOME. Just a thought.
- ultimoo 14y agoI use GNOME. How would one go about switching out Swing for GTK while running a JetBrains IDE (or another application)?
- kunai 14y agoSimple. Switch to VIM. Or, just write GTK code from scratch directly in the IDE. It's not too hard. I currently use Swing in Java, all written from scratch - no IDEs to be found. I've also dabbled around with simple GTK+ apps. They aren't as easy, nor as efficient, to work with as the standard Java toolkit, but you get used to it. I switched back to Swing because I wanted as few dependencies as possible.
- duaneb 14y agoSo--I'm still missing something. Are you saying that the way to get good font rendering in IntelliJ is to write GTK+ apps? It sounds like you misread the OP.
- kunai 14y agoAh, I see. I'm sorry about that, but I don't think that there's a solution to fix Swing font rendering in IntelliJ itself. Unless, of course, you dive into the source code.
- lucian1900 14y agoHow would one magically make Intellij or any other Java IDE that isn't Eclipse use one of those?
- martinced 14y agoI'm using IntelliJ IDEA on Linux since version 4 or so (we're now at version 12). And I agree with you but... The trick is to use a pixel perfect font with no anti-aliasing at all and to set the correct vertical spacing between lines and then IntelliJ is just going to look fine (for a Java app). So first you go download a real font (a font made especially for programming, like the Proggy fonts which you can get at proggyfonts) (I take the .ttf version) You relaunch IntelliJ and then go to: Settings / IDE Settings / Appearance / Editor / Colors & Fonts / Font and then you set your pixel perfect font, say : ProggySquareTT (Size: 16, Line spacing: 1.3) (oh and btw IntelliJ is so stupid that if you have "Show only monospaced fonts" checked it won't understand that Proggy is monospaced and hence not show it into your fonts choice list) I'm 40 years old and still have 10/10 eye vision, which I attribute to two things: avoid dark characters on light background scheme anytime it's possible and never ever using anti-aliased fonts (which are blurry) "Pixel perfect" is the way to go here. And anyway anti-aliased fonts under Linux are so fugly compared to OS X / Windows that you're really not missing much by going pixel perfect. Regarding the other IntelliJ IDEA fonts (the ones which are not the editor / console), I'm stealing a Tahoma.ttf from Windows and settings everything to be Tahoma. Same for my Emacs but for whatever reason under Emacs I'm using Terminus and not Proggy at the moment ; ) Now of course it's really sad that the only "ok" desktop UI ever made with Swing is the one made by JetBrains: it took people who wrote the fscking most advanced Java IDE to come up with a reasonably looking Java Swing app : ( The Eclipse guys didn't even bother and created their own UI (SWT) which kinda speaks volume about the nameless mediocrity that Swing is : (
- cdi 14y agoI fixed font rendering on linux in IntelliJ for me by deleting hinting information from font in fontforge editor. Google it.
- pooriaazimi 14y ago@martinced: You've been hellbanned for the past 5 days. Which is a shame - your comments are long and informative. > I'm using IntelliJ IDEA on Linux since version 4 or so (we're now at version 12). > And I agree with you but... > The trick is to use a pixel perfect font with no anti-aliasing at all and to set the correct vertical spacing between lines and then IntelliJ is just going to look fine (for a Java app).* > So first you go download a real font (a font made especially for programming, like the Proggy fonts which you can get at proggyfonts) (I take the .ttf version) > You relaunch IntelliJ and then go to: > Settings / IDE Settings / Appearance / Editor / Colors & Fonts / Font and then you set your pixel perfect font, say : > ProggySquareTT (Size: 16, Line spacing: 1.3)* > (oh and btw IntelliJ is so stupid that if you have "Show only monospaced fonts" checked it won't understand that Proggy is monospaced and hence not show it into your fonts choice list) > I'm 40 years old and still have 10/10 eye vision, which I attribute to two things: avoid dark characters on light background scheme anytime it's possible and never ever using anti-aliased fonts (which are blurry) > "Pixel perfect" is the way to go here. And anyway anti-aliased fonts under Linux are so fugly compared to OS X / Windows that you're really not missing much by going pixel perfect. > Regarding the other IntelliJ IDEA fonts (the ones which are not the editor / console), I'm stealing a Tahoma.ttf from Windows and settings everything to be Tahoma. > Same for my Emacs but for whatever reason under Emacs I'm using Terminus and not Proggy at the moment ; ) > Now of course it's really sad that the only "ok" desktop UI ever made with Swing is the one made by JetBrains: it took people who wrote the fscking most advanced Java IDE to come up with a reasonably looking Java Swing app : ( > The Eclipse guys didn't even bother and created their own UI (SWT) which kinda speaks volume about the nameless mediocrity that Swing is : (
- zem 14y agoqt works superbly. i wish it had more language bindings, but other than that it's an excellent cross-platform toolkit.
- swah 14y agoStrangely, Sublime Text seems to win hearts on every platform...
- melling 14y ago"Edwin: Sublime Text is written in C++, with a small amount of Objective-C for Cocoa integration on OS X, and Python for plugins." http://www.sublimetext.com/blog/articles/sublime-text-2-0-released http://www.sublimetext.com/blog/articles/sublime-text-2-0-re... In short, they used the native libraries on Mac OS X.
- swah 14y agoYet, a single guy, three platforms.
- veeti 14y agoQt, Qt, Qt. Basically the only toolkit that gets native look & feel right.
- wtallis 14y agoQt is great for getting the native look, but it's never mastered the native feel, at least on OS X.
- rosser 14y agoWhat do you find missing in the subjective experience of using Qt-based tools under OSX?
- jjoonathan 14y agoA lot. It has been a year since I last used Qt, but given the frequency with which I hit bumps in their integration with OSX, I'm quite sure that they haven't all been fixed by now. Keyboard shortcuts, drawers, and focus passing would randomly fail to work, since Qt was welded into the Cocoa event system and sometimes missed rather important edge cases. For instance, pressing the Esc key was programatically indistinguishable from clicking the 'Ok' button in custom drawers. More often, power-user shortcuts were overridden, didn't respect configuration changes, or entirely absent. Some views (table view IIRC) didn't even try to exactly mimic the native look and feel. Menus worked in fundamentally different ways on different platforms: if somebody designed an app to work on Windows, which does menus on a per-window basis rather than globally, menus would randomly appear/disappear on OSX. Oviously this wouldn't be a problem if all your users knew about it, but they won't. Integration with launch services was absent or crippled. Docking windows required tons of theming if you didn't want them to look like crap. Sometimes constraints or conventions imposed by cocoa were overridden, leading to subtle differences in the positioning of button text and so on. I spent 2 person-days hunting down the cause of a 2-pixel border between the edge of one view and the window backing; the hunt ended in failure when I realized that I would have to monkeypatch or completely replace Qt's layout system in order to get the view snug against the edge. Sometimes Qt's abstraction layer led to unacceptable performance tradeoffs that would be easy to solve on any given platform but were simply not addressed in the Qt API. In general, the UI design tools didn't enforce platform-specific conventions and were miles behind XCode in terms of ease-of-use. I had a few problems that weren't specific to integration, but they were just as frustrating. The documentation, while great for an open source project, was still far behind the status quo for native libraries. I found their documentation on coordinate systems very difficult to understand (in comparison with the Cocoa documentation) and sometimes it was just plain wrong, e.g. about mouse event propagation within graphics views (and you would think that would be a fairly heavily trafficked page, no?). If you want your Qt app to seem native, you had better be prepared to dig through Qt itself and patch its deficiencies. This often means being intimately familiar with the native libraries, since the bugs reside at edge-cases the Qt devs weren't thinking about when they wrote the code. Honestly, if I had to do it all over again, I think I would have just insisted coding the front end twice using native libraries and development libraries each time.