Having already rewritten most of my pages, and having discussed rewriting them again, I struggle to see how anyone could think that time is my issue! Any improvement takes longer than doing nothing. In any case, I now have enough practice writing virtual multi-cell images to cut and paste within the master document and replace the middle bit correctly than to paste the raw string of braces, tildes, and exclamation marks into the Diagram Designer. Nor only that, I can do the former entirely offline save for uploading the whole. I am currently adding movement diagrams to Man and Beast without even looking at them online. If I find errors when I do upload them the quickest way to correct them is by seeing how the page appears and changing the master document accordingly.
What I meant by inefficient was the problems that I have learned always accompany duplicate code. Over the last few years one of my major tasks at work has been refactoring and centralising tracts of duplicate code. The issues that I know of are that duplication takes up more space, is more susceptible to errors such as typos, and makes extra work if a sudden change is made. The first two I can see applying similarly to substituting another long piece of code. Single-array page will certainly use a single piece set for the array diagram, piece images, and (if any) movement diagrams, and I find it hard to imagine even a multi-array page (be it 3d or multi-subvariant) doing otherwise.
If my idea really is impossible, say so and I will live with it, but don't suggest ways of addressing an imaginary time issue by doing something even more time-consuming.
What I meant by inefficient was the problems that I have learned always accompany duplicate code. Over the last few years one of my major tasks at work has been refactoring and centralising tracts of duplicate code. The issues that I know of are that duplication takes up more space, is more susceptible to errors such as typos, and makes extra work if a sudden change is made. The first two I can see applying similarly to substituting another long piece of code. Single-array page will certainly use a single piece set for the array diagram, piece images, and (if any) movement diagrams, and I find it hard to imagine even a multi-array page (be it 3d or multi-subvariant) doing otherwise.
If my idea really is impossible, say so and I will live with it, but don't suggest ways of addressing an imaginary time issue by doing something even more time-consuming.