Christof's Guineu (.Net Compiler for Compiled VFP applications) does just this already, fwiw. Check out Christof's blog at http://guineu-blog.blogspot.com. And you are right, translating from one form object to another has already been done, and could be transferred to any technology that has objects able to be defined, either as objects (I think Scott Gu has announced this for the next Silverlight) or as files of some sort. It's all a matter of having classes that reflect the properties and methods relevant to the conversion. I don't expect Samuel to end up doing less: he has said that they will be supporting Silverlight development, but I don't know any details.

Hank

>why would you want to?
>
>Because $250 is orders of magnitude less than the cost of 63-man-months(> 5 man years) described by you to reinvent an existing app into a new UI. Plus it doesn't take 9 months to get the result, meaning the product gets out the door quicker- or that 5 developer-years gets to be spent on something completely new rather than another round of reinventing the same wheel.
>
>I doubt that you could write a translator to do this
>
>Why not? Strahl wrote a translator to convert a 32-bit data-aware form to dHTML a decade ago. All the UIs do is connect to different dlls or hooks. Assuming that eT has used OO they can build the hooks for each UI technology and then just call the one that's needed. sure it takes time to assemble hooks for each technology- but eT only has to do that once.