NON_MOVABLE

[uckelman]

Thus spake Thomas Russ:

I would perhaps prefer positive rather than negative trait names and use

Movable, Selectable, Stacking

and just set the default values for new pieces to have the traits
included/activated.

But that strikes me as somewhat counter to the general method of
creating pieces by adding traits, so this preference may not really
work with the standard piece creation workflow and model.

There’s a performance reason not to do it this way: Movable, Selectable,
and Stacking would be part of almost every piece, which would add three
more decorators to those pieces. Having decorators which handle
exceptional behavior helps minimize decorator depth.

–
J.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[tar]

On Jun 9, 2009, at 4:08 AM, Joel Uckelman wrote:

Thus spake Thomas Russ:

I would perhaps prefer positive rather than negative trait names
and use

Movable, Selectable, Stacking

and just set the default values for new pieces to have the traits
included/activated.

But that strikes me as somewhat counter to the general method of
creating pieces by adding traits, so this preference may not really
work with the standard piece creation workflow and model.

There’s a performance reason not to do it this way: Movable,
Selectable,
and Stacking would be part of almost every piece, which would add
three
more decorators to those pieces. Having decorators which handle
exceptional behavior helps minimize decorator depth.

Sounds eminently reasonable.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)