[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NSXML* classes changed to use libxml2 directly... Should we merge th
From: |
Riccardo Mottola |
Subject: |
Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk? |
Date: |
Wed, 25 Jan 2012 11:45:10 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20120104 Icedove/8.0 |
Hi,
On 01/25/2012 11:11 AM, Gregory Casamento wrote:
Any time we allow a user to build without a given dependency they are
getting a sub standard experience with GNUstep. I do consider nib
reading to be a critical feature of GNUstep, and I think it's foolish
to allow users to build without features like this.
I do not consider it at all critical. "Gui" itself is not even critical
for a server user and NIB loading is not critical for gui even. It is a
nice feature, a feature people use.
It hurts us to have so many optional libraries. Since most potential
users may just be trying us out, when they are able to build without
XML support or without Unicode support without various other things,
thy get a bad impression of GNUstep because we've allowed them to get
a bad experience with it.
It does absolutely not hurt us, it is an advantage!
Perhaps you miss the fact that people use GNUstep in many different
ways? People want to embed it, people want to use it for a certain
specific task only?
Some people may want to use just Foundation and don't even care about
nib loading. Why force them?
it is one of the reasons why we loose many users and developers, we
force everything to be a big tank even if it is not necessary.
We warn pretty well about libxml2 missing, but we can build without it.
And currently everything standard even works quite well without it. For
the standard user on the standard linux machine, libxml2 will be just
there,put by the packager of the gnustep packager or just be there
because it is common and it will be picked up by configure. Other users
shall know better and why do you want to rob them of freedom?
Riccardo
- NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/23
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Ivan Vučica, 2012/01/23
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/24
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/24
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Richard Frith-Macdonald, 2012/01/24
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Fred Kiefer, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?,
Riccardo Mottola <=
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Ivan Vučica, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Ivan Vučica, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Riccardo Mottola, 2012/01/25
- Re: NSXML* classes changed to use libxml2 directly... Should we merge this into the trunk?, Gregory Casamento, 2012/01/25