Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Stop the VFP OOP Madness!!!
Message
From
13/05/1998 15:27:25
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00098883
Message ID:
00099173
Views:
35
Colin,

Some time back, in a discussion about automated testing facilities, statements were made along the lines that these were problematic for VFP because VFP "paints" objects on the screen rather than 'use real objects' (to that effect).

No one of repute objected to such statements, while some of the "stars" seemed to concur with the observation.

So, assuming that VFP does *not* conform in this imporatnt area, it seems likely that it is *NOT* VFP stringent "enforcement" which is the problem here. I personally don't know who to blame, but would not put it all on the "purity" of VFP, that's for sure.

I guess if VB is really so bad at enforcement there should be lots and lots of chaos in its ActiveX area, because generally that's the result of lax enforcement. If it were otherwise we would all be far better off with light-to-no enforcement on anything.

In summary, sounds like the enforcement argument is a crock of crap.

Cheers,
Jim N
>>I don't know if this is entirely true, but Microsoft claims that the code remaining in VFP for backward compatability is less than 200K. As far as new menu and report design surfaces, I agree that they are sorely needed, but I'd think if they were coming that we'd have seen them in San Diego. As far as the menus go I'd actually rather see better OCX support so that we could use the coolbars control and some of the other ActiveX menu controls out there that don't work in VFP. IMO, VFP would be much better served in the long run if it can play nice with all of the various OCX's out there than rather then having new elements specifically for VFP developed.
>
>Actually the main reason why VFP has problems with some ActiveX controls is because of how strictly VFP enforces the standards of ActiveX controls as opposed to VB. The trouble with this is most third-party ActiveX controls are tested on VB. I agree with the premise of what you are saying but what M$ needs to do is either reduce VFP's enforcement of the standards (not a good idea IMHO) or increase the enforcement of VB and the like so the actual so called standards are enforced across the board.
>
>Cheers
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform