... Well, one windowing package would be easier to maintain than two, which ever we choose. ;)
That's the whole point. We have a bunch of incomplete Qt bits, two functioning Qt apps, and the rest, that is well tested and now much improved, is Tk.
I'd be arguing for Qt if it was the other way round.
Work was done on a Qt replacement because that's what the people doing the work wanted to do. At this point, we have some unknown amount of work to get this new stuff going at all, let alone to the reliability the current code has. Finally, no matter what, all the SIS bits are Tk and going to stay that way.
At the end of the day, the only way to get to a single gui toolkit is to drop Qt.
-- David N. Lombard Rossmoor, Orange County, CA http://www.fourmilab.ch/cgi-bin/uncgi/Earth?imgsize=320&opt=-z&lat=33.8&ns=North&lon=118.08&ew=West&alt=7&img=learth.evif
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
