|
 Printer Friendly |
Employing a naming convention in Woodstock models
Making use of code hints in the Woodstock editor
Applies to: Woodstock 3.2x
Date: 02/15/2005
Using a naming convention can be very helpful when working with Woodstock models. In Woodstock, you must declare unique names for several different model components—thematic attributes, action codes, yield tables and outputs—and it is sometimes easy to exhaust meaningful component names, let alone keep track of and remember all of your declared codes. The purpose of this tech tip is twofold: [1] to describe a naming convention that you can employ in your Woodstock models, and [2] to describe a coding aid in the Woodstock editor.
While you can use any naming convention that you wish in your Woodstock models, a convention that associates a code name with the section in which it is declared is particularly useful. The concept is simple, preface every declared code with a letter that indicates the parent Woodstock section: preface action codes with an ‘a’, yield table codes with a ‘y’, and output codes with an ‘o’. In this way, you can use the same root code name in different model sections if you wish. This type of naming convention becomes very powerful when combined with code hints in the Woodstock editor.
Code hints is an editor option that you can use to display a list of declared user codes and model keywords. To activate hints, open the editor options by clicking Tools > Editor options. Next, display the Hints tab and check all of the provided model sections whose codes that you wish to display in the code hint list, including keywords. You access code hints by simultaneously pressing the Ctrl key and space bar.
You can use code hints to complete code entries. If you type the first few characters of a code name, Woodstock will filter the code hint list to display only codes that begin with that character string. If you select a code name from the code hint list, it is entered in the editor where your cursor is located.
This is when the naming convention described above becomes very powerful. If you type a ‘y’ and press Ctrl-space, the code hint list will display all declared yield tables. Similarly, if you type an ‘o’ and press Ctrl-space you will be presented with a list of declared output codes. This can be particularly helpful when declaring outputs, which reference thematic attributes, actions and yield tables.
|
|
Stora Enso Predicts a 2.5% Savings
“We asked, ‘If we had made the decision and optimized the problems, how much money would we have saved?’” The answer was approximately 2.5 percent.”
- Continue reading...
- View all case studies...
|
 |
|
|
|
