>One thing I'd like to see (although I'm not entirely sure it will fit in your current goals for the product) is the ability to run VFP tools inside the VFP environment (just like everyone currently does, eg. with the Toolbox, class browser, object browser, etc) but be able to isolate it from the rest of the VFP environment. One thing that really limits usability with VFP-based tools is the fact that a CLEAR ALL blows them away. Then you have to restart any tools you may have had open.

The VFP team has looked at the CLEAR ALL issue carefully back to the VFP 3.0 days, and there has never been a good solution to implement based on the fact that those tools are VFP objects in the same memory space. This won't change in the future, but with more memory and desktop space, a possible solution is to have 2 instances of VFP open at the same time, one for running and debugging and one for editing things like class libraries and programs.