Re: [trinity-devel] QT->TQT changes in main trunk

Thanks Slavek, Michele, Yes, I remember well and I recall all the good effort you put into the initial renaming while we bridged with 3.5.13_SRU waiting for renaming, Darrel to finish tidying up the help system and the artwork for the all publicly visible material (I still have some of the original gimp and inkscape files from the time). The only reason I posed the question, was I recall you had all but eliminated any KDE3/KDE4/TDE Qt naming issues back then, and I also recall all the effort that went into the tool to help port kde/qt sources to tde/tqt so if somebody wanted to build their favorite kde app on tde, it could be done without a whole lot of grief. I'm all for it if it is needed, but I didn't think Plasma/Frameworks5 would conflict with the Qt naming from Qt3, and with kde.org tossing kde4 on the trash heap of desktops that were going to be better than KDE3/TDE and change the world, I was just curious if it justified all the manhours to do. If it will make everything cleaner, then it is a good thing. If it will just make it that much harder to build kde apps on tde -- well, if the conflict isn't the driver, is it worth the effort? I may be thinking wrong, but I recall the year+ long effort to rename and rework and eliminate all conflicts in the 2012-2014 timeframe, and that was a whole lot of work. When Michele says "probably as much work as going forward", that worries me. You guys (and girls) know best, and the past efforts work seamlessly, so if it will make things easier/cleaner, no reason not to do it.