Hi,

In theory it doesn't sound all that bad, but in practice I can see 2 or 3 problems

a) Our patches don't exit to desktop (at least not yet), so you'll have to reboot and load the selector manually
b) Someone will have to do the dirty work and collect all info, take screenies, hunt for manuals etc which is too time consuming (imagine having to delay a patch just because we can't find enough data for the interface!)
c) Most of the interfaces are, imho, fugly and not that usable :)! And to make different screenies etc for tt and falcon would mean at least 3x the work.

Ok, I realise that I'm writing the above under the scope of a developer (i.e. actually having to implement this ;)). As a user, yeah, it wouldn't be bad to have a framework for something like that.