Where do you put your scripts?

[Scott Rossi]

>> Ideally, one should only have to maintain one instance of any
>> control or handler, if that instance is placed in the right spot
>> in the message hierarchy.
> 
> I'm not sure how to do that in many cases.
> 
> Suppose I have cards as maps of several buildings.  Suppose I have
> thermostat "controls" spread all over the maps.  It would be nice
> to be able to maintain one group for all, but I don't know of an
> easy way.

If the same thermostat is present across multiple cards, place the
thermostat in a group with background behavior set to true.  If the readout
of the thermostat is different across multiple cards but the controls that
affect the thermostat are the same, setup the controls as previously
described, but use a card-local readout for each card.


> I might have one thermostat control library and it might be good to
> keep a master thermostat group on a card there.  But what if
> thermostats are used by a variety of control libraries.

Separate what can be used commonly across multiple applications and what
needs to be localized for a specific instance.


> Suppose a couple of those thermostats are modified for controlling
> ovens or for controlling humidity.

Use a general thermostat routine that has subroutines for different
applications (ovens, humidity, etc).


> Suppose I use thermostats in several standalones.

The keep your thermostat routine in an external stack and access it as
needed.


Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design
-----
E: scott at tactilemedia.com
W: http://www.tactilemedia.com