SHERLOCK -------- SHERLOCK currently evaluates interfaces created in Visual Basic 3.0 (Visual Basic 2.0 and 4.0 interfaces may fail or give erraneous results). For more information about Sherlock, read the technical report available on our web site (http://www.cs.umd.edu/projects/hcil): 96-08 Mahajan, R., Shneiderman, B. (May 1996) Visual & textual consistency checking tools for graphical user interfaces, CS-TR-3639, CAR-TR-828, ISR-TR-96-46. SHERLOCK consists of two parts: 1) A parser for Visual Basic .frm files to convert them into an application independent Canonical Format. 2) Seven executables each of which gives an output. To interpret outputs look for the following Technical Report at the HCIL web site. Since SHERLOCK was not designed from scratch to be a product. These seven programs evolved from the orignal one single program as a result of our research. Although all 7 programs are different programs they share lot of same code (classes and functions), any organization trying to integrate SHERLOCK with its Visual Basic design process should make an effort to integrate these components together. These components work fine seperately, but each executable takes at least .20 Megabytes of memory. 3) Note that the parser and executables were built on a UNIX environment on Sun/Sparc platforms running SUN OS 4.1. The executables may or maynot run on other UNIX platforms. To run on other platforms the code may require little tweaking. Some parts of the code uses some UNIX libraries and system commands which may not be platform independent. The code has not been tested on any other platform 4) Executables are in the directory Executables. Executables directory also contains additional data files which are input to some parts of the code. These files should always copied along with executables before running the executables. Code is in the directory Code. Code for the parser is in the directory Parsercode 5) The code was compiled using gnu g++ (gcc 245) compiler and may require some tweaking with other compilers like CC. 6) The code was only tested with four applications in VB 3.0, any bugs beyond that have not been resolved. 7) The parser (translator) code has no documentation as it was written by the GE side of the project and was later linked to SHERLOCK code. First Step: 1)Save all the Visual Basic .frm files in text format in a single directory in which all the SHERLOCK directories (Code,Parsercode, Executables) and this documentation is contained. Run the following script .If you have problem running the executables. The code is contained in the sub directory Code. The script is designed for running one VB application at a time. Copying new VB .frm files to this directory again and running the script would overwrite the previous outputsif present. 2) The script also converts the .out output files to postscript using enscript. If your UNIX environment uses some other postscript viewer, you can modify the script below. Also, enscript should be available on the web (atleast a demo copy ------------------------------------------------------------------------------ #!/bin/csh -f foreach f(*.frm) vbparse $f $f.cft end ls -x1 *.cft>filenames mkdir cftfiles mv *.cft cftfiles mv filenames cftfiles cd cftfiles cp ../Executables/* ./ measures filenames>measures.out enscript -rG -fCourier7 -pmeasures.ps measures.out concordance filenames>concord.out enscript -2rG -pconcord.ps concord.out baskets filenames>baskets.out enscript -2rG -pbaskets.ps baskets.out buttons filenames>buttons.out enscript -2rG -fCourier -pbuttons.ps buttons.out spellcheck filenames>Mispell.out enscript -2rG -pspell.ps spellall.out bcapitals filenames>bcapitals.out enscript -2rG -pbcapitals.ps bcapitals.out capitals filenames>capitals.out enscript -2rG -pcapitals.ps capitals.out yes|rm spell.out Mispell.out