Hello!
Stephan Sokolow has written on Tuesday, 23 April, at 2:21:
>I have one question in the role of a developer.
>As someone who's used Qt in C++ recently (as opposed to via PyQt back
>before PySide was even proposed) and used it for more than the big
>brother of a Hello World app, how would you say the current offerings
>(C++ API, Qt Quick, etc.) compare to Vala (which I've actually used) for
>writing something reasonably memory-safe using native widgets?
>...because, if I can ever spare the time, whether I contribute something
>suitable for inclusion will depend on how much more painful it is to
>work with Qt than with Vala, PyGTK, or PyQt/PySide. (And KDE has shown
>all too well that Qt applications written in C++ can crash readily and
>frequently)
I hope PCMan will answer this shortly. But what I heard from him is
Qt is a lot better in both API stability and variability. And in regard
of debugging - C++ isn't syntetic language but Vala is therefore should
be a much easier to debug C++ applications than Vala (Vala is just a hell
to debug). But I have almost zero experience with C++ and Qt so cannot
tell you much.
>Also, any tips you'd be willing to write up on how to port C-based GTK+
>applications to Qt would be welcome. I'm always up for learning new
>things but I have time to learn them through trial and error far less
>often than I'd like.
Porting GTK+ applications to Qt shouldn't be too much hard but it
will require at least two things:
1) if the application has own GTK classes those API interface should be
completely rewritten because in C++ classes have public and private
methods but in GTK each method is just a separate API (because it's C
after all);
2) all calls to GTK APIs should be replaced with appropriate Qt calls,
also every GTK object should be replaced with appropriate Qt object. I
don't know yet if some list of appropriations ever exists.
There may be some problems with the transition in case if Qt object
has no method appropriate to some method for similar GTK object. But also
opposite is right - some GTK parts may be simplified in transition if
Qt object has convenient method which is absent in GTK.
You're not the one who will need to learn it. But it seems we have no
other choice because GTK3 is a way to nowhere and we decided to not try
to support it because it require too big efforts without any benefits. Qt
seems to be a lot better alternative due to much more stable API.
With best regards.
Andriy.
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list
