comment on

I too was surprised to see Qt4 bindings in KDE sources instead of CPAN. Since KDE 5 was released this summer, but last update of Perl-Qt was in November and involved something about KDE4, I guess that this binding will be slowly dying, too. But at least it's usable for now, while Qt5 still deals with font issues (all fixed in 5.4) having reached third minor release: surely, but slowly.

Speaking about usability, at least 480 people regularly use perl-qt4 it and 7124 have it installed for some reason, despite the absence of packages depending on libqtgui4-perl (pyqt4 is 20 times more popular, and there are approximately 97 packages depending on python-qt4 while not being a python library; pyqt5 is not so widely used as of now).

Your point is proven, but, still, I think that installing Qt module from KDE bindings is a lesser mess than employing Python as Qt GUI "driver".

In reply to Re^3: perl + Qt, the easy way by aitap
in thread perl + Qt, the easy way by vkon

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks