-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jan 02, 2003 at 02:39:52PM +0100, Klaasjan Brand wrote: > > Ok, well where do Xt apps fit in? Or do they, even? > > Both Qt and GTK do not depend on Xt. This does not prevent you from > running Xt applications. If you want to you could port Xaw to Xft. My point was that I considered (note the tense) this possibility a bad thing. But read on... > > I'll take xterm over any of its replacements any day of the week. > > IMO, no one can touch it. I don't much care if the fonts are > > anti-aliased, or if I can make my background "transparent" -- all that > > seems to accomplish is to slow command output WAY down... > > It's called sacrificing performance for rendering quality and no sin. It depends on the application. If I'm using an application whose primary function is reading something (like a web browser), then yes, I'd like it to look pretty. But if the purpose is more functional, like a terminal emulator, then I just want the output fast. Otherwise (and this is the key), rendering the output SLOWS DOWN THE COMMAND I'M RUNNING! In many cases, this may be extremely undesireable. > Maybe you haven't found out, but it seems there's a button to turn the > anti-aliased stuff off... Which, at least for KDE, AFAICT, is global, and can't be turned off on a per-application basis. See above. > > For comparison, open an xterm, gnome-terminal, and konsole all next to > > eachother (if you have room, or near to eachother if not). Then: > > > > $ ls -laR / > > > > ...in each of them. > > Interesting benchmark, but when do you actually do that in real life? If I use commands much like this one rather often, actually. > your terminal is scrolling so fast you can't read the text what is the > value of having a terminal instead of eg a progressbar? I don't always care about reading ALL of the output, but I use large line buffers (can konsole or gnome-term adjust this setting?) so that I can scroll back to important bits. And an example would be extracting files from a tar archive... You want the output, but you don't want it to slow down the tar. If you have many small files (which normally is the case), then it will definitely have an impact on the performance of the tar command. > > Notice that xterm blazes. Konsole is noticably slower, and gnome-term > > is /dog/ slow. > > Keep in mind that xft/render is quite new in the mainstream distributions > and will be optimized further. If you don't like it, just use xterm. > Your choice. Well, the problem appears not to be with Xft at all. But I'm getting to that... On Thu, Jan 02, 2003 at 01:00:14PM -0500, Havoc Pennington wrote: > On Thu, Jan 02, 2003 at 08:09:56AM -0500, Derek Martin wrote: > > Ok, well where do Xt apps fit in? Or do they, even? > > > > I'll take xterm over any of its replacements any day of the week. > > xterm does support Xft2. Try something like "xterm -fa monospace" I > think. That's very interesting, I was not aware of that. How does one learn what fonts are available to be used this way, and how does one specify the SIZE of said fonts? Incidentally, I tried a similar benchmark to the one I described above, using xterm with this font, and konsole with the same font. The performance of xterm was consistent with xterm using the 7x14 fixed width font (I believe these are bitmapped, yes?), and similarly the konsole window performed similarly (but a bit better) with this font as compared with the default font I use with konsole windows. This suggests that Xft is not at all to blame for the poor performance of konsole and gnome-terminal -- at least not directly. Very interesting indeed... - -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+FLztHEnASN++rQIRAhxLAKCL4P8oqYgoftxeAzyuIOzIU3mhIgCfVbNX 7o1H3OH7li0WAz6zUhX4jUk= =+0W4 -----END PGP SIGNATURE----- -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
