Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP Common Controls Accepted to VFPX
Message
 
À
21/08/2006 15:11:38
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
01147339
Message ID:
01147455
Vues:
17
Thanks Craig - I did not know - I haven't even had time to catch up on my "Dating ame" re-runs.
Regarding:
The VFP team has never had responsibility to create or maintain ActiveX controls that ship with VFP.

Don't you see a basic attitude or a lacking of "the customer is always right" with MS's approach.

How big of deal can it be? Are supposed to not use active X?

Why enhance VFP while leaving the OCX is the dust.

What MS seems to be doing is telling the VFP community to go **** itself. Why make us spend money on new versions of VFP that will never look better than a classromm programming project? OCX makes all the difference in the world.

Will they take away you MS diplomas if you take the position that ignoring the importance of OCX to the VFP community if you say it like it is - it's not MS's responsibility to policy - it's MS's responsibility to the customer - what you said in that statement is that MS could care less - what would it take - 200-300 hours to deliver an upgraded beta OCX for VFP?

Do you like offering it to MS so easily?:-) Don't be cheap Craig, play hard to get everyonce in a while.




>Do you really not know what SednaX is (or actually, was)? It's a community effort to enhance VFP. It's now been renamed VFPX. It's at http://www.codeplex.com/Wiki/View.aspx?ProjectName=VFPX
>
>The VFP team has never had responsibility to create or maintain ActiveX controls that ship with VFP.
>
>
>
>>A link to Steve's Blog:
>>http:www.//sellenoff.blogspot.com/
>>
>>Begins second entry down.
>>
>>I was searching for some info on VCX and OCX and I found "Steve".
>>
>>He talks about Sedna X - he - as many of us - wonders why MS's VFP team has not assured that OCX controls have kept pace with VFP releases.
>>
>>It almost as if MS is telling us not to use active X - essentially - they are telling us to write FoxBase or dBase TXT applications.
>>
>>But he did mention Sedna 10 and the fact that his OCX ComCtrl VCX is being looked at as something to be included in Sedna 10.
>>
>>Why has Microsoft forced us to jump through hoops just to get our VFP apps with OCX controls up and running on an MS OS?
>>
>>Why is it so difficult for MS to do this?
>>
>>And, what is SednaX?
Imagination is more important than knowledge
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform