Simon,

Well, I have no real opinion either way actually. From what the proponents are suggesting it's pretty cool. My concern would be to not break things in the sense that if someone wanted to keep developing as we now do they could. Sounds like a good implementation of 2-way programming would allow that.

I do like the notion of everything being stored as text for the simple reason of version control. I think that adds to the 'pro 2-way' argument. The price of changing is, I suppose, what detracts.



>Hi
>
>I would very much like the two-way programming available in Visual dBase etc. It makes life much easier to be able to combine visual form design and text based programs.
>
>I would certainly vote for this feature in a future version of VFP.
>
>Simon White
>
>>Gerry,
>>
>>>>>- design the Form "visually"
>>>>>- save it as "text"
>>>>
>>>>Could you use the View code option with the form open in the Class browser for this?
>>>
>>>I want it all ... "Viewing" is not the same as "two-way programmming".
>>>
>>>And the View option doesn't handle "deep" hierarchies either.
>>>
>>>Borland/Inprise has even patented (recently) their implementation of "two-way".
>>
>>
>>I'd kind of like to have this as well plus some sort of ability to 'fake' a table so I could run the form without some of the gyrations.
>>
>>I'd think that this would make a great enhancement request for VFP8...