Qt Toolkit Support Likely to be Dropped from Mozilla
Wednesday February 12th, 2003
dasx writes: "Looks like the Qt port of Moz is going under. It's been stricken from the 1.3b branch — which probably means it's gone for good. Hopefully, some of us can bring it back to life." Please don't spam the bug with useless comments or whining.
Update! A page describing the current efforts to get the Qt port back to a working state has been posted.
Thursday February 13th, 2003 8:21 AM
You are replying to this message
I don't get it. Has QT really been dropped from the branch? But seawood's patch to remove QT has not been approved for 1.3 and Asa remarked that resolving the situation- either removing QT or fixing it- doesn't have to happen in the 1.3 timeframe. If it had been removed, one would expect to see a comment on the bug stating as much and/or approval of the patch to remove QT.
Anyway, here are my thoughts:
"Hopefully, some of us can bring it back to life."
That is what people have feared all along- that the decision to drop the QT code would be lamented and a bunch of people would try to get it to a state where it could be included in the tree but not really be interested in maintaining it, thus increasing overall breakage. If there were people who were really willing to maintain the QT port, with all the continuous year-round fixing and testing that entails, working to keep it just as up-to-speed with the latest patches as the GTK port, then people wouldn't be dropping the code. The question now is whether people have really stepped up to maintain it or if they are just trying to keep it in the tree.
I still don't see any real reason for the existence of a QT port besides toolkit fanboyism. People may quote other ideas, but would they really get implemented?