On Sat, Jan 12, 2013 at 2:13 PM, Uwe Rathmann <uwe.rathm...@tigertal.de>wrote:

> Hi Denis + Laszlo,
>
> > IMHO, this for QextSerialPort: do not see any features.
>
> QextSerialPort is pretty old ( from the 90s ) and the fact that it isn't
> really a Qt library is probably the reason why it has survived all the
> development of Qt without being actively maintained.
>

It has design flaws in my opinion, unfortunately. I personally do not think
that the reason has been it is not really a Qt library, but the fact that
it was the only somewhat usable solution. The serialport usage has always
been common enough including the embedded, and this is what Qt users were
only able to find before.


> But I don't vote for it in any way - all I wanted to do is to report from
> a related discussion as far as I can recall it.
>

Sure, no worries. Thank you for that.


> > In summary I would say that QtSerialPort completely outperforms
> > conventional counterparts of similar libraries for Qt, and it's true.
> > You yourself can compare it. :)
>
> QextSerialPort has one killer feature: Qt4 support !
>
> Qt4 is where the applications are and probably will stay for quite some
> time. Especially in embedded environments using the serial port is quite
> common and unfortunately Qt5/QWS seems to be regression.
>
> I guess QtSerialPort could easily support - even early - Qt4 versions.
> The question is if this is something you could do as a graduated Qt5
> module ?
>

"* Qt4 and Qt5 support"

... from my initial email in this thread. We will not drop this support any
soon as there are already downstream projects depending on it like my
commercial one.

Laszlo
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to