Found this from Kevin - and definitely agree with Craig's call - while much of it is fairly general (get a blog, participate in the Sedna ER list), the two best points he makes:
- creating Visual FoxPro components for Visual FoxPro has a direct impact on the IDE and increases Visual FoxPro's overall usefulness.
- Remember, the @Say is dead and there's no excuse for creating yet another dated looking switch-board application running on spaghetti code that accesses a horribly denormalized database.
I'm actually getting ready to move a VFP 8 app into VFP 9 and am looking forward to the visual improvements to be made.
The SPS Weblog - Visual FoxPro Community Action