Add type property to constant, design parameter and state variable arrays

[1fifoto]

Consider adding type: "string", "integer" and "float" to each constant, design parameter and state variable entry.

[1fifoto]

For example,

global.constants = [
    { name: 'pi', type: "float", value : 0.0, units : '_' }
];

[1fifoto]

Although adding a 'type' property is not a very object-oriented way to do things, it will help us from having three different constant arrays for string, integer and float. In other words, checking and branching on type is a no-no in the OO world.

[1fifoto]

Nothing uses this, so I don't know if we need this.

[grumpyinca]

Having an integer type for design parameters and state variables might be a match for a search algorithm that implements integer programming technology. However, I am having trouble getting my mind around string values for DP & SV. Perhaps this is not an issue. The change might be worthwhile simply to clean up how constants are handled.

[1fifoto]

In my opinion, a 'design' is a set of values that are the instances of 'design definition' variables. They need not have anything to do with the computational aspects of the design. That is, they need not be used in or be the result from the equation set. Instead, they are carried with the design to specify it. I feel that all types (for example, float, integer, and string) should be possible.