Hi All,

I have seen VB.NET videos where fields objects are dropped from the Data Source which cause a label (with the proper caption) and a textbox (usually) to be created on the form. Certainly this way save us a lot of time when you have many fields to create with many forms

I have not seen anything in SF documentation that will cover this, and I had tried dropping a field object from one of my SF business object from the Data Sources windows but it will not create the objects from the SF class, instead they will be created from the default .NET classes.

So my question would be, is there any facility in SF to help you out in this regard? or we have to simply manually drop labels, textboxes from SF Toolbox and manually change the caption and assign the BindingField?

Thanks!

Edhy Rijo

Hi guys!



I don't want to get into a long debate on this, and I cannot comment specifically on VPM's strengths (or weaknesses) as my VFP framework experience is based on VFE and a custom-developed OOP framework.



My experience with both those VFP frameworks was similar to Edhy's. I found the experiences very positive, allowing the development of strong, scalable, and maintainable applications much quicker than otherwise possible. I have to say that unlike both Aaron and Edhy, my experience with the VFE Data Dictionary was incredible--the ability to objectify data (down to the field level) and control behavior using custom field behavior classes, identify lookup and validation at the data layer independent of the UI, and introduce custom behavior via exposed hooks was powerful stuff. The fact that the Data Dictionary also allowed for dropping controls and labels on forms that auto-bound to data dictionary properties and eliminate the need to update labels with "Customer Address" hundreds of times in every form in an app was even more icing on the cake.



I agree with Edhy that to the extent that builders and other goodies can facilitate and quicken delivery of applications, MF should consider adding them to the great framework known as StrataFrame. I would image such improvements need not require a developer to use them, allowing them to "roll their own" if they have the time and inclination. Choice is a happy thing, right? There should always be the flexibility of each developer to map his or her own approach to solving business problems, but to categorically discount tools found helpful by others based on individual preferences or experiences may not be in the best interest of the overall community.



Now if you'll excuse me I've not touched StrataFrame yet today so I really need to get back to some fun stuff!



Have a good one!




________________
_____/ Regards,
____/ al

That is indeed correct but it is important that the tool or suggestion is in fact a benefit to the overall community. My point is that VPME is not as wonderful as some posts in these forums would suggest and I would choose to argue that point in the hope of preventing SF from becoming a .NET version of VPME - which in my opinion is not in the interests of the overall community.

I am here because I became fed up with VFP/VPME and consider .NET/SF to be light years ahead in comparision. That doesn't mean I don't want to see SF evolve as I very much do.

I am not trying to force my views on the SF developers but I will argue my corner if I believe other products are being held in comparison to SF unfairly.

Good dialog, guys.  If you look around the forum, you will see that this debate has come up more than once and we have mentioned that there will be most of what you are requesting in future updates.  The goal is to get away from data queries...this would be slow and unresponsive the large the app became.  But we have some ideas that we feel will be beneficial to everyone and still make it easy to make changes.  This will not be implemented until SF 2.0, however, when we rewrite all UI controls.

SF 2.0?? Cool. When?

________________
_____/ Regards,
____/ al

It will be late in the year before we release a totally new SF 2.0.  We want to make sure that there isa  migration path and there is a LOT of new stuff that we want to do including more RAD and web components, etc.