Hello,
Gosh, Oh no, he again? Yes, it's me again.
I think I state the obvious, but what procedure does a real WinDev-er use?
Like this :
- CDM (I think no)
- LDM
- RAD generation
- all the rest, changes and adds, hand-made
If so, what in case of big changes? Even in the LDM ?
TIA, Teun
oo RAD (cloned) and hierarchical oop is good !
imagine a project with
a class for HF accès
a class for RAD
a class for user groupware
a class for parameters
a class for logs
a generic class for main generic functions (sepcific repport launch...)
etc,
those classes are 'main' ones, created in globals
they bring main common object for your project skeleton
note wd8 can bring all them in componants (to link devoted files and windows)
built your extra RAD-Like windows to fit your own specific windows (with a rad-like classe for code)... you can add them in the default RAD or adapt-it (see our french-witten ressource for it)
Then comes projects specifics modules...
why not continue ?
1 module = a set of classes/windows
Then here are paththrough classes that are used by many modules : use 'heritage' and you should be ok.
after surch a structure : the oop !
Built you classes to a newbie usage level
each method with produce an atomic function... ie myLight:On() myLight:Off()
then module windows code will simply 'play' objects methods and produce effects in small codes easy to debug...
Hope i understood question..
Regards
R&B