Initializing help system before first use

Converting Custom Runner Code to Script Blocks

In VDL 2.0 the custom runner file allowed the view developer to layer on extra scripted functionality.
This generally took the form of: 
insight
        .getView().applyVDL('#main', function () {
                // custom code here
        });

Which was placed in a script block in carefully constructed html that made up the custom runner which was referenced from the runner attribute in the companion file. This is no longer needed. VDL 4.7 now allows script blocks to be placed within the view, or in linked JavaScript libraries, and this removed the need for a separate custom runner file.

Parent Topic Migrating VDL 2.0 Apps to VDL 4.x

© 2001-2019 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.