>Dear all,
>
>1) True windows object
>I am getting response that if VFP were to implement true windows object then it would slow down the application. I for one would not be concerned with this because the speed of todays PCs are fast enought and if those who cannot afford to get new machine then they should just stick to the old VFP or even FPW. My message is that VFP needs to keep up with the current trend because mainstream development testing tools are not going to support VFP becuase it is the only one different in MS programming tool family.

Not everyone has current PCs. IMO, many of our clients will suffer.

>
>2) UI
>Look at the current UI for VFP 6.0. It is does not have the similar look as compared to VB or C++. The buttons and screen has the outdate old look.

This was demonstrated at last year's DevCon. It's already changed.

>
>3) Development Environment.
>IMHO, MS can revamp the whole development UI but keep the "command window". It is this that differentiate VFP from other development tools. It is a sort of "dos prompt" for developers.

No, I disagree. If any changes to the Development UI, it will be to integrate it into Visual Studio shell, which I hate. It's much less productive than what we have now.


>
>
>Regards,
>Kueh.