Hi Thomas,

Thanks for your contribution.

With foxLANWeb, the SAME application code works on LAN (as usual) AND on the Web.
GUI code is preserved, no need to split it into a 'LAN' version and a 'Web' version.

Not to change the application basics, we just replace VFP base classes with foxLANWeb's (automated), without affecting normal LAN operation.

Then dev. can adapt application code gradually, based on awAppAnalyst recommendations.

Hook pattern is used in some places, though not as the app to framework interface.


>Thierry,
>>With FoxLANWeb, your very same Visual FoxPro code works on both LAN and Web!
>>* Less than 5% of the application code needs be adapted
>....
>>FoxLANWeb comes with # 1,500 structured classes, methods and procedures, and a powerful code adaptation tool performing over 80% code adaptation work in either scx, vcx or prg, and allowing full application testing before migration.
>>
>>Demo and source code : http://www.FoxLANWeb.com/
>
>Looked at the source code and had the nagging feeling that at least some of the shown changes
>could have been handled "better".
>
>I missed something like an I-Layer in codebook terms, an isolation area where adaptions from own code to fwk
>code can be used with OO-techniques. Also I got a gut feeling that for using the FoxLANWeb approach for multiple
>projects the Hook pattern should be used more often - even if only to separate the code for both GUI's even if they
>are "active". Or do you use facade objects via factory ?
>
>And yes, without at least some hints about planned price structure
>further thinking about it is more of a hobby than a business idea...
>
>my 0.02 EUR
>
>thomas