Mailinglist Archive: opensuse-factory (710 mails)
| < Previous | Next > |
Re: [opensuse-factory] Package categorization
- From: Dimstar / Dominique Leuenberger <dimstar@xxxxxxxxxxxx>
- Date: Thu, 30 Jun 2011 09:03:42 +0200
- Message-id: <1309417424.3000.18.camel@3120-3560.ams.tmf-group.com>
On Thu, 2011-06-30 at 03:28 +0400, Ilya Chernykh wrote:
I think THIS is the underlying problem that needs to be addressed, and
NOT what toolkit an application is written in.
I'm by far not a purist when it comes to the choice of my applications.
As long as the app does what I need/want and is appealing, I could
really not care less what the dev used as Toolkit to develop it. That's
just not my problem. GTK, Qt, Wx... all have their pros and cons.. some
devs might love to hack X11 code directly :) Their choice! Who am I to
say: nah: you use X11 directly: I don't want to use that app if the app
is exactly what I need?
Back to the topic: I am aware of a bunch of applications mainly ignoring
proxy settings from the desktop. This is indeed very frustrating, as
you'd need to configure proxies in various places.
THIS for example has been solved with the introduction of libproxy,
which passes the 'right' configuration down to the app.. extracted from
the running session, whatever it is. Not to say the solution is perfect,
but it goes in the right direction.
Same approaches can be done for similar problems. All that needs to be
done to 'sell' this to App devs or even better get it deep nested in the
toolkits (happened for example on the GTK side, as libproxy is needed by
libsoup and glib-networking). Same should happen with Qt for example.
=> Target the actual problem, don't try to conveniently maneuver around
it.
Dominique
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
If some people do worry a lot about the frameworks and libraries used by
their
apps, they need some real concerns in their life. There's no need for
openSUSE
to spend time feeding into more of this silly toolkit purism nonsense.
If people do not care which applications they install, they will find out
that the desktop
settings they had set up do not apply everywhere, a disappointing discovery.
I think THIS is the underlying problem that needs to be addressed, and
NOT what toolkit an application is written in.
I'm by far not a purist when it comes to the choice of my applications.
As long as the app does what I need/want and is appealing, I could
really not care less what the dev used as Toolkit to develop it. That's
just not my problem. GTK, Qt, Wx... all have their pros and cons.. some
devs might love to hack X11 code directly :) Their choice! Who am I to
say: nah: you use X11 directly: I don't want to use that app if the app
is exactly what I need?
Back to the topic: I am aware of a bunch of applications mainly ignoring
proxy settings from the desktop. This is indeed very frustrating, as
you'd need to configure proxies in various places.
THIS for example has been solved with the introduction of libproxy,
which passes the 'right' configuration down to the app.. extracted from
the running session, whatever it is. Not to say the solution is perfect,
but it goes in the right direction.
Same approaches can be done for similar problems. All that needs to be
done to 'sell' this to App devs or even better get it deep nested in the
toolkits (happened for example on the GTK side, as libproxy is needed by
libsoup and glib-networking). Same should happen with Qt for example.
=> Target the actual problem, don't try to conveniently maneuver around
it.
Dominique
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |