OK, then we'll need to specify minimal minor version for Qt5 as well ->
easy!
On Monday, October 28, 2013 4:41:54 PM UTC+13, pcma...@gmail.com wrote:
>
> A little bit off topic, but I'd like to raise some concerns about Qt 5.
>>
>> I'd suggest that we use Qt 5.1, not 5.0.
> Qt 5.0 removed many X11 related APIs which we used heavily.
> If we use it, rewriting many places is needed, which is not a trivial task.
> Qt 5.1 added them back as a module and only some header names are changed.
> http://qt-project.org/doc/qt-5.1/qtx11extras/qx11info.html
> So porting existing code to Qt 5.1 will be much easier, I guess.
> Though in the long run we may use Wayland, it's not ready yet and X11 will
> still exist for quite a long time.
> We therefore need to keep the X11 code working.
>
> Regards
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
