>>< When I was doing development in the 90s, .....
>>
>>Oh, what a good developer you were! Really, looking back now at your works (which don't need any introduction) shows your genius.
>>
>>We are really fortunate to have you now in the fox team. You are doing a great job!
>>
>>On the side note, do you miss writing code? Not at all?
>
>I sometimes miss writing code, but I don't think about it much since I am busy on other work all the time. Some of the VFP tools I created were GenScrnX, SuperCls, BuilderB (also known as BuilderX), the Application Wizard, many FFC classes, Class Browser, Component Gallery, ScreenX, WebExplorerX, the Transformer (for Win/Mac conversions), etc. Yesterday I helped Randy Brown on the VFP team debug something in the Class Browser source code. Something changed in a recent internal build of VFP 9.0 and it broke something in the class browser code, and he the team the bug was exposed when running the class browser code. I'm working on a new cool tool, I just showed it to Calvin Hsia this afternoon and he said he was cool. :) I won't disclose more about it now, maybe at DevCon next month.

I Did'nt think that Calvin Hsia was like that. So he really likes himself? Claiming that he's cool. Just teasing ;-)

I know I'm hard on the marketing thing about VFP but I appreciate a lot all of those tools that you did.

But there's one thing though that puzzles me. Where should we place the Component gallery? I mean doest it still have a place that no other tools in VFP occupy? I asked the question to other developers and they don't seem to really use it. Some told me that they used other tools instead. I used it a couple of times (more exploratory than anything) and I thought that the tool really had potential.

The way I see it is if it's still there with all of the other tools there must be a good reason.

With VFP 9 coming is there a reason we should use it or is there something else that does the same kind or job?