Messages
Reply
Edit
Delete
FAA will :
- derive Commons.VCX from xxx.vcx
- adapt the code everywhere in your project(s)
- do the adaptation only once - if code was previously adapted, FAA should not change it.
If you want to share xxx.vcx across several *.vcx / projects, you can store it in a central location (e.g. in an ancestor folder as mentioned earlier) and force FAA to take this folder for each project you adapt.
FAA never overwrites a class in xxx.vcx - the code you've written there should not be lost.
Not sure it's a good idea to have all subclasses named the same (don't know if you took the same names as a sample only or for real) - the CSS class hierarchy does not take *.vcx into account, just the class name (could be changed though). FAA should accept this naming scheme though.
I have this particular structure of classes and i need to know if what i normally do with VFP is possible with FIC.
I have these classes:
Commons.VCX (subclasses all foxpro base classes; calling them for example _textbox, _form, etc.etc)
Erp.VCX (subclasses all classess in Commons.VCX; calling them _textbox, etc)
Support.VCX (subclasses all classes in Erp.VCX ; calling them _textbox, etc)
I need to make 2 new applications. The first, called Support, uses Support.VCX) and another one, called Erp, uses Erp.VCX)
The logics inserted in Erp.VCX must be used even in Support application , through Support.VCX)
At which level do i need to do adaptation ? If i make it in Support application all classes under it are modified and so next time i'll make adaptation, for Erp application, what happens ?
I need not to write logics for every app....
Thierry Nivelet (FoxInCloud)
Never explain, never complain (Queen Elizabeth II)
