howtos:toolcoding:subroutinepackage
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
howtos:toolcoding:subroutinepackage [2012/02/08 21:55] shona.weldon |
howtos:toolcoding:subroutinepackage [2013/06/04 12:38] (current) shona.weldon |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Subroutine Package ====== | ====== Subroutine Package ====== | ||
| - | From here you can download a set of sub-routines that can be put in your Vx/views directory. They can then then be loaded using the informants window and once in your model any view can call the sub routines. | + | Subroutines are reusable code files that can be called from views. The advantage of using them is there is only one copy of common code which makes it more maintainable and also gives consistency to how you interact with your views. |
| + | |||
| + | We have developed a set of subroutines you can use as a starting point. Please contact your whatIf? support person to get the package | ||
| + | |||
| + | Please consider these **use at your own risk**. We are not supporting them but are just providing them as a starting point from which you can modify them as you wish! | ||
| + | |||
| + | **whatIf? Team members**: Please look in /models/caness/V5/views/subroutines for the most current subroutines and under there find TemplateExamples for the most up to date templates. | ||
| - | This is the subroutine package that should be unzipped in your model's Vx/views | ||
| - | {{:howtos:toolcoding:subroutines.zip|}} | ||
| ===== Setup of installed files ===== | ===== Setup of installed files ===== | ||
| - | Once you have extracted the files there are 3 files you must copy and adjust for your current model/version | + | Once you have extracted the files there are 2 files you must copy and adjust for your current model/version |
| getModelVersion_CopyAndCustomize.t | getModelVersion_CopyAndCustomize.t | ||
| Line 11: | Line 15: | ||
| * copy this file and re-name it to: getModelVersion.t | * copy this file and re-name it to: getModelVersion.t | ||
| * Edit the file and adjust the version number | * Edit the file and adjust the version number | ||
| - | |||
| - | getProjectNames.t | ||
| - | * This file is used to manage the names of various projects which might be running out of this model | ||
| - | * For now the only thing it is used for is makeing export directories for each project and is related to the getProjectExportPath.t subroutine | ||
| - | * copy this file and re-name it to: getProjectNames.t | ||
| - | * edit the file and adjust the project names | ||
| informs_CopyAndCustomize.samm | informs_CopyAndCustomize.samm | ||
| Line 31: | Line 29: | ||
| Now you are ready to write views that use subroutines. See below info about the examples that are a part of the sub routine bundle you have downloaded and extracted. | Now you are ready to write views that use subroutines. See below info about the examples that are a part of the sub routine bundle you have downloaded and extracted. | ||
| + | |||
| ===== Examples ===== | ===== Examples ===== | ||
| - | In that new folder you will find an examples sub folder with some example views: | + | In that new folder you will find an TemplateViews sub folder with some example views: |
| - | levelVarProjection.t | + | levelVarProjection_<verson>.t |
| * This type of view projects a variable which holds variables which are not share variables, like rates or efficiency levels etc | * This type of view projects a variable which holds variables which are not share variables, like rates or efficiency levels etc | ||
| * It gives several different ways to project this variable through a menu command | * It gives several different ways to project this variable through a menu command | ||
howtos/toolcoding/subroutinepackage.1328738133.txt.gz · Last modified: 2012/02/08 21:55 by shona.weldon
Page Tools
