Keith Packard wrote:
> ... a trivial (and usable) compression scheme ... is done by
> using PolyFillRect ...
> By the time screens have doubled in resolution, I expect Render will be
> relatively well established and core protocol workarounds needed only for
> really old (and low resolution) hardware.
This seems like a great combination.
Xft+Xrender addresses the strategic (long term) need:
Client side font handling means new technologies can come
out without waiting years for X protocol or X server changes
to propagate into the field.
Xft+PolyFillRect(or XPutImage) addresses the tactical (short
term) need:
Ability to run on systems with older (pre Xrender) X servers.
The one place where this could be an issue is running Xft
on pre Xrender X servers on slow data links. Do people know of
other places or environments that are not covered by
Xft+Xrender or Xft+PolyFillRect?
If these are a large and/or important part of the X user base
then perhaps it should be addressed as a core part. If this is
a small or fading part of the X user base then perhaps it
could be handled as a special case.
My impression is that most of the modern and interesting X
environments and applications already are a problem for X
systems with a slow data link. Gnome/Kde/Qt/Mozilla already
ship around a large amount of images which probably makes them
unusable for systems with a slow data link.
Lets try to get a list of the environments where newer apps
want to use Xft for better font handling and also want to
run on pre Xrender X servers on slow data links (or other
environments where there could be an issue).
--
Brian Stell
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
