I've often thought a worthwhile project would be to only recreate those DBF files on the fly when the form/report/visual class is edited, but make the code the actual artifact that is kept around. That would have made source control so much better. The way we do it now is backwards.
Eric On Fri, Feb 7, 2025 at 2:44 AM Alan Bourke <[email protected]> wrote: > > I thought one of those extensions would give you all the Foxpro > > functionality, like the MANY languages you can write in, in the shell of > VS > > Code. It might even allow you to deploy to linux. > > If VFP didn't have visual classes with the metadata and code snippets in > DBF files, and there was a way of defining the UI declaratively, like for > example XAML in WPF, then that would be a runner. > > -- > Alan Bourke > alanpbourke (at) fastmail (dot) fm > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CAAwxvUnhkTJOYP0qw07iBiDGdqXn1K1L=mm7qqym6eiuzoh...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
