>>I recently took some time to evaluate kwin on a TDE system. The >>kwin developers have done excellent work; kwin itself operates > well and >>the configuration dialogs are relatively sane compared to most > modern >>offerings. At this point I agree with Martin that TDE should be >>looking at using kwin as a default instead of our old twin fork as > soon as >>possible. >> >>I have put together an Etherpad >>(http://trinity.etherpad.trinitydesktop.org/61) detailing the >>changes that need to occur before this can be done. Both TDE and > kwin will >>need some modification to ensure that TDE doesn't lose features > after the >>migration is complete. > > Based on the etherpad notes, this sounds like a post R14 goal. As > twin->kwin is a significant transition, I'm guessing R15? > > Darrell Yes, though it would be nice to have R14 in a state where major API/ABI changes in the TDE core libraries are not needed to integrate kwin into TDE. We will see if that is practical or not shortly. ;-) Tim