Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Sharing a FoxInCloud Adaptation Assistant issue on wwThreads

$
0
0
Sharing a FoxInCloud Adaptation Assistant issue on wwThreads
FoxInCloud
Sharing a FoxInCloud Adaptation Assistant issue on wwThreads
05/15/2012
02:40:11 AM
3I405Q4ET Show this entire thread in new window
Gratar Image based on email address
From:
Thierry Nivelet (FoxInCloud)
To:
All 
Attachments:
None
FoxInCloud Adaptation Assistant (FAA) is a set of 2 .app located in <your program data folder>\Microsoft\Visual FoxPro 9\AB\AW\ folder:
- 'awAdapterStart.app' is a simple starter installed once for all; it polls foxincloud.com for a new version of awAdapter.app (see below) and downloads it if necessary
- 'awAdapter.app' contains classes, tables and forms doing the whole job with over 400 methods and a large number of regular expression patterns. awAdapter.app creates several tables in the same folder as your source project (named <yourProject>-awAdapter*), a .xml configuration file, and .log files.

FAA is designed to analyze, adapt and publish all kind of VFP applications and coding styles.
So far, FAA has analyzed over 780 applications tallying more than 9M VFP instructions (http://foxincloud.com/shared-projects.php); largest applications tally more than 500,000 instructions.

Despite FoxinCloud team's continuous effort, you might experience some error when running FAA against your own application.

Some of you suggest that we add a global error handler that would overcome these errors; this is something we might do in the future but, meanwhile, we prefer that you guys share issues on this message board by posting a debugger window screenshot: in this screenshot we can see everything we need to plot and fix the issue, e.g. call stack and variables.

Sharing a debugger frame screenshot on wwThreads is fairly simple:
1- Make sure VFP debugger executes in a separate window: Tools > options > debug > Environment > debug frame, then 'Set as Default' (we know no SET for this feature)
2- If VFP reports an error while running FAA, note down the error message and number, then choose 'suspend'
3- Open the debugger window: Tools > debugger
4- If necessary, expand 'Call Stack' and 'Locals' windows so that all content is visible; please expand array nodes if possible
5- Take a screenshot of the debug frame with whatever tool you see fit (Windows 7 provides a simple Screen Capture tool)
6- Post your screenshot image to a ftp or a http server - e.g. some free ftp service or your own web site
7- Post the issue on wwThreads with error message and error number and append your debugger screenshot using the following code:

<<img src="ftp://yourDomain/yourDirectory/yourScreenShot.ext" />> or <<img src="http://yourDomain/yourDirectory/yourScreenShot.ext" />> e.g.: <<img src="http://foxincloud.com/images/FAA-debug.jpg" />>

Here is an sample debugger screenshot, kindly shared by Patrick B.

Thanks for helping us making FAA better suit your needs!

West Wind Web Monitor

Viewing all articles
Browse latest Browse all 10393

Trending Articles