On Sep 6, 2014, at 4:56 PM, Clifford Yapp wrote: > If that's the case, we're looking longer term to switch from Tk to Qt > for our GUIs. Given that, I'd hate to see you spend a tremendous > amount of effort embedding Tk in Qt to make what will ultimately be a > temporary situation work (Sean may have a different opinion here, but > personally I'd rather not put any more investment into Tk > integration/support than we have to...)
Nope, I concur. Converting MGED and/or Archer's main window over to Qt is the next step. > My suggestion would be to either a) go with the setup that is working now and > take a stab at the > polygon drawing with an eye towards having that feature available when > we do switch to Qt, or b) look at what would be involved with making a > version of the simple classic-mode MGED that uses Qt for its windows. Great suggestions, either way. Cheers! Sean ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
