Re: perl + Qt, the easy way

I really think this is (from a technical point of view) cool, but for the life of me I cannot see any sensible application of it.

If I know enough Python (and I need to know enough Python to make your approach work) to put together the Qt-part of a program, why would I then want to use Perl for the rest?

I'd just do it all the way Python rather than incurring the risk of having to debug a potential mess of under the hood glue-code should anything not work the way I expect it to work...

Comment on Re: perl + Qt, the easy way

Replies are listed 'Best First'.
Re^2: perl + Qt, the easy way by LanX (Saint) on Dec 13, 2014 at 23:55 UTC
> why would I then want to use Perl for the rest? yes... ... but the (maybe naive) question should rather be how to use Python bindings from XS and to avoid the Python-middle-layer. The demonstrated Python code doesn't look semantically different to Perl's, so why can't an XS extension dock to it? Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :)}	[reply]
Re^2: perl + Qt, the easy way by vkon (Curate) on Dec 14, 2014 at 12:17 UTC
I have tons of my perl apps already, some of which are really efficient, so rewriting them to python will only made them worse... So my approach will not only save me from rewriting to python, but also will provide me a possibility to continue using strong parts of perl... yep.... :-\|	[reply]
Re^3: perl + Qt, the easy way by RonW (Parson) on Dec 15, 2014 at 16:41 UTC
Follow up question, why Qt? There are other GUI tool kits that have usable Perl bindings.	[reply]
Re^4: perl + Qt, the easy way by vkon (Curate) on Dec 15, 2014 at 20:20 UTC
... I am not big Qt user but ocasionally do Qt... ok, the question could be generalised to ''why use libA when there is nice libB available'' there could be gazillions reasons in different situations... I even not bother enumerate them.....	[reply]


Don't ask to ask, just ask
	PerlMonks