Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Windows Desktop Apps
Message
De
22/04/2016 05:59:55
 
 
À
21/04/2016 09:07:13
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01635157
Message ID:
01635211
Vues:
96
My question was naive, I must admit. It is asked too much to expect modules built with other tools/languages to be aware of all that vfp-apps are aware of. Having admitted that, I now realize it IS important to be aware of this when people (e.g. of Microsoft) claim that new extensions can be built with other tools/languages. In the case of many (vfp) legacy applications that will imply that new extensions will have to act (e.g. upon a database) asif it were a separate executable. So, it will have NO knowledge of the state of variables and settings. And tables will have to be opened as in a private datasession. I think this is all doable, but it will require some (some?) redesign before it can actually be implemented.


>You can build Windows apps today that can watch things.. UI updates, changes in variable values, etc. I don't think we can have an application be aware of open tables without a lot of work. The common way to connect to data in ,Net is through some type of data provider. Think ODBC, but there are other options. Just as in VFP, you can't be aware of what ODBC has open behind the scenes, you can't be aware of that in .Net. To make it work, you'd have to handle all the file open/close/etc yourself. I'm not sure it gains us that much to maintain all that code.
>
>
>
>
>>Hi All,
>>
>>In 2015 Microsoft introduced the phrase 'Windows Desktop Apps' for PC-applications. This month they demonstrated the preview of the ‘Desktop App Converter’. The claim is that legacy apps can run without much adaptations inside a 'container'. Moreover, extensions can be built with the legacy platform, but also with newer platforms.
>>
>>I interpret this as the claim that, in time and gradually, we can build new modules and/or replace existing modules with another tool/language. Eventually the application might be totally VFP-free. However, esp. one question pops up:
>>
>>Modules (.app) in VFP are aware of the open tables/cursors, the public/private variables and the various SETtings. Will we be able to build a module with such a new tool/language that is also aware of open tables/cursors and variables??
Groet,
Peter de Valença

Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform