7 Mar
2012
7 Mar
'12
7:02 a.m.
On Wed, Mar 7, 2012 at 9:31 AM, Timothy Pearson
<kb9vqf(a)pearsoncomputing.net> wrote:
But why would you need both Qt3 and Qt4? Just choose one and stick
with it. Do you want Qt4, then migrate completely.
Will someone
tell me or put the link to the description of why someone
would need to rename QT API?
I know that for programmer this is a disaster!!! This will strangle
the development!
I have addressed this issue multiple times on this mailing list. It is
impossible to use Qt4-based libraries in TDE, such as Webkit, while the
symbols from Qt3 conflict with those from Qt4.
You can blame the developers of C++ and Qt if you like, but unless we want
TDE to remain niche by never integrating well, and also not being able to
take advantage of all the work put into Qt4-based libraries, this renaming
had to be done.
Can you put some examples of what issues with Qt4 this renaming addresses?
It isn't hard to adapt BTW, just tack a "t" onto the front of the old
"q<foo>" functions and static members.
There are standard API and standard documentation, and development
tools that are designed for this standard. Getting into this business
you doom yourself on endless job of synchronizing with Qt4 API
evolution. Not saying about the deep of current API coverage. That is
not the work for one man!
"Stock" Qt3 is available if it is needed, but I am personally using TQt3
so that I can take advantage of Qt4-based system libraries in the future.
Tim
If f.ex. I will utilize reference countable pointers from Qt4, then
Qt3 will go to depreciation at once! So this TQt looks like all big
nonsense... :-(