That is only simple because you assume you only have to switch on the complex implementation that was already done by someone else. The number of lines needed to implement this in general (i.e. give every piece type a configurable size, 1x1 by default) is not very large.
I refer to it as "simple" as "simple from the user's perspective." I actually figured it would be a PITA to implement, and that the needed amount of code "is not very large" is a bit of a surprise to me.
Since the betzaNew.js file is still considered experimental, the xxxTinker routine is not officially documented yet. (Exept perhaps burried in the Comments).
I'll wait for this, then. Perhaps there can be a bigpiece.js in the future (whoever decides to write it; I'm going to try to learn enough Javascript to write a weirdmoves.js for this).
I refer to it as "simple" as "simple from the user's perspective." I actually figured it would be a PITA to implement, and that the needed amount of code "is not very large" is a bit of a surprise to me.
I'll wait for this, then. Perhaps there can be a bigpiece.js in the future (whoever decides to write it; I'm going to try to learn enough Javascript to write a weirdmoves.js for this).