All,
I've been thinking about deprecating the Xlib backend, so that we can focus
more on Cairo. I have discussed this with Fred and I would like to know what
everone else thinks about it.
Later, GJC
--
Gregory Casamento
## GNUstep Chief Maintainer
On 25 Dec 2006, at 14:59, Gregory John Casamento wrote:
All,
I've been thinking about deprecating the Xlib backend, so that we
can focus more on Cairo. I have discussed this with Fred and I
would like to know what everone else thinks about it.
Depends what is meant by 'deprecate'.
It
Richard,
The reasons behind the move to Cairo are as follows:
1) Cairo is being used by a number of other projects. It is very stable and
well maintained.
2) Cairo has been ported to a number of other operating systems, including
windows and has a large number of output targets. This way,
Gregory John Casamento schrieb:
Richard,
The reasons behind the move to Cairo are as follows:
1) Cairo is being used by a number of other projects. It is very stable and
well maintained.
2) Cairo has been ported to a number of other operating systems, including
windows and has a large
It's done then...
Both XLIB and ART will be deprecated in the near future. We are shifting
focus onto the Cairo backend. Development efforts on the backend should
concentrate on getting the Cairo backend up and running.
Once this is done XLIB and ART backends will stay in the repo for a
On 12/25/06, Fred Kiefer [EMAIL PROTECTED] wrote:
Gregory John Casamento schrieb:
Richard,
The reasons behind the move to Cairo are as follows:
1) Cairo is being used by a number of other projects. It is very stable and
well maintained.
2) Cairo has been ported to a number of other
[EMAIL PROTECTED] wrote:
I've been thinking about deprecating the Xlib backend, so that we can focus
more on Cairo. I have discussed this with Fred and I would like to know what
everone else thinks about it.
I think the less backends the better, as its less code to maintain. That
said,
