The Linux version really uses Qt for the whole thing. The Windows version seems to use WinAPI. But I also read from somewhere else that there is a thin layer between Opera and the underlying toolkit.
Can you only move around in your text with arrow keys, page up/down and home/end? That's a deal breaker for me. I've given VS some flak for that at http://tech.slashdot.org/comments.pl?sid=1245985&cid=28106773 but it applies to most editors except emacs and vi.
Yes, KDevelop 4 has a "Vi", even though still not yet complete (e.g: I can't use:> to indent - or maybe I miss something?)
In fact, KDevelop's vi capability comes from KatePart, the ultra-advanced text-editing component from KDE.
(And yeah, I use h, j, k, l to navigate because my down and right arrows are broken)
Slashdot Mirror
The Linux version really uses Qt for the whole thing. The Windows version seems to use WinAPI. But I also read from somewhere else that there is a thin layer between Opera and the underlying toolkit.
Can you only move around in your text with arrow keys, page up/down and home/end? That's a deal breaker for me. I've given VS some flak for that at http://tech.slashdot.org/comments.pl?sid=1245985&cid=28106773 but it applies to most editors except emacs and vi.
Yes, KDevelop 4 has a "Vi", even though still not yet complete (e.g: I can't use :> to indent - or maybe I miss something?)
In fact, KDevelop's vi capability comes from KatePart, the ultra-advanced text-editing component from KDE.
(And yeah, I use h, j, k, l to navigate because my down and right arrows are broken)