Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Microsoft: Visual Foxpro 10 last hurrah
Message
From
21/03/2007 11:00:02
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01204397
Message ID:
01206574
Views:
28
>Hi, Alex.
>
>>>Impressive or Effective, regardless of the term, the goal is User Friendliness of the application. If you think you are good in building user friendly app in VFP, you can build it even better in .NET and in a faster fashion because the latter offers variety of controls to choose from which are not available in VFP. And these controls are not even available as ActiveX. Can you group rows in VFP's grid? Can you view summary of rows in VFPs grid? Certainly not because VFPs grid is very old fashioned. Certainly there are ActiveX available but for sure most of it don't behave as expected because they are not native to VFP. An eye catching GUI is secondary to me. A user friendly app I think is not much on how it looks but how it behave and how the user can produce results without so much clicks.
>>
>>That sounds like a useful control. Perhaps the goal for some of us may be to use cool .NET controls in VFP forms creating a sort of hybrid tool. How feasible do you think it would be be for an expert VFP/.NET developer be to implement such a graft? Does the way "My" is implemented in Sedna offer some clues?
>
>Not at all. The My namespace is just a wrapper for common things yo can do already natively in VFP, by using WSH, or by using some basic .NET functionality trough COM Interop. What My does is put all this in a hierarchy tree and offer a smart Intellisense that allows you to navigate this beyond what VFP used to provide. They emulate nested namespaces .NET style, but this is just a clever mechanism that helps instantiation and Intellisense.
>
>The NET4COM part of Sedna, so far, doesn't add anything to the UI/controls space. It is a just a way to access some specific .NET classes, also. It is quite limited, indeed, because there is no support for overloading and other features in .NET.
>
>What allows you to do some of this hybrid stuff you are thinking about is the .NET Extender from ETecnologia. I didn't try it fully, but they went beyond standard Interop stuff and they handle many of the hardest issues, allowing for many of these things. Yo may try it. It sounds very interesting, although I don't know how mature/stable the product is. A small warning, though: I guess you won't be able to do any of this without learning a fair deal of .NET, because you need to understand some underlying concepts to be able to use this stuff.

Thank you Martin. Learning a fair deal of .NET is going to be necessary. Leaving VFP totally behind would be a shame.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform