Qt bindings

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Qt bindings
by ac on Wednesday 04/Jan/2006, @15:43

Is it possible for things like the Qt-DBUS bindings, poppler-qt etc to be moved into kdesupport or equivalent? I really hate having to download svn code from another server just to try out things that are necessary, not optional ;)

Any other suggestions welcome, I'm currently using kdesvn-build to do all the hard work.

Related Links

·   Articles on Developer
·   Also by ac
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Qt bindings
by Christian Loose on Wednesday 04/Jan/2006, @16:15

I don't think that the dot is the right place to discuss such things.

[ Reply To This | View ]

Re: Qt bindings
by Brad Hards on Wednesday 04/Jan/2006, @18:07

Well, the whole poppler (or dbus, whatever) project isn't going to move into kdesupport (any more than they would move into a Gnome archive, or an enlightenment archive), and the bindings are closely tied the underlying project. Also note that there are no KDE dependencies in the poppler-qt bindings, so why should it be tied to KDE? Sure, it will be used by KDE, but also by other, non-KDE, projects.

It is much easier to maintain the bindings in conjunction with the underlying code, and freedesktop.org is a good place to work on such projects.

[ Reply To This | View ]

Re: Qt bindings
by Waldo Bastian on Wednesday 04/Jan/2006, @21:36

kdesupport started out as a repository for dependency libs as a convenience to developers so that people didn't have to hunt down packages across the internet.
Actual development always took place elsewhere, kdesupport just acted as mirror that got updated once in a while.

[ Reply To This | View ]

Re: Qt bindings
by ac on Thursday 05/Jan/2006, @15:22

What about making it easy for KDE developers to use the bindings as well? Why should I have to check-out some svn code from a non-KDE repository just to get a working development KDE? Sure, I can do it. Do I want to? No.

Look, if kpdf relies on poppler-qt and I have to check it out of freedesktop.org, I just wont bother. I'll live without and use xpdf or something else. It's not going to affect the little bugfixes and enhancements I want to do in other parts of KDE.

But when it comes to Qt-dbus, that's a different matter and I hope that it's integrated into the KDE svn.

[ Reply To This | View ]

Re: Qt bindings
by Thiago Macieira on Thursday 05/Jan/2006, @19:55

> But when it comes to Qt-dbus, that's a different matter and I hope that it's
> integrated into the KDE svn.

I'm working on that. It'll take time, so volunteers are welcome.

Currently it's being hosted on the KDE Subversion server pending freedesktop.org bureaucracy.

[ Reply To This | View ]

Re: Qt bindings
by Ian Monroe on Friday 06/Jan/2006, @10:22

Heh, well with SVN you can stick external SVN sources into the tree. That would be a clean way to do it. Having stuff in SVN that requires manually syncing seems kind of in defiance of the point of downloading from SVN... to get the most-up-to-date.

[ Reply To This | View ]

Re: Qt bindings
by Christian Loose on Friday 06/Jan/2006, @13:59

> Having stuff in SVN that requires manually syncing seems kind of in defiance of the point of downloading from SVN

Actually not for those external libs. Our stuff often doesn't work with the in-development versions of those libs (e.g. HAL/DBUS and media kioslave).

So having a snapshot of those libs in our SVN that is known to work is IMHO a good idea.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I always have things in progress." -- Kurt Granroth
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.