Hi all,

As we were asked for in private, some details about "less than 5% code adaptation"

A- AUTOMATED adaptations

FoxLANWeb ships with an adaptation tool which
- scans the project(s)
- changes any VFP baseClass into a sub-class of foxLANWeb base classes
- adapts event code structure
- changes messageBox(), inputBox(), etc. into wMessageBox(), wInputBox(), etc.
- produces a reports on manual adaptations necessary : what and where
- optionally, writes taskList shortcuts and or adaptation comments into the code

Adaptation tool has an option to copy all files into a test directory in order to check that automated adaptation does NOT affect normal application operation.

B- MANUAL adaptations

1. Break down method code expecting a modal result (e.g. value=messageBox(...) / DO FORM ... TO value / show(1)) into 2 parts :
code before modal result remains unchanged
code AFTER modal result is moved to another method (foxLANWeb standard or custom)

2. Set up an environment procedure (or class) independant of main directory physical address, and shared between LAN and WEB projects

3. Implement GUI 'surface' events (mousexx(), keyxx()) in JavaScript

4- Set up wConnect-derived Server and Process classes (some properties to set)

5. Miscellaneous minor adaptations such as: implement 3 hook methods, assign a default value to form init parameters, add some dodefault(), etc.