🚀 go-pugleaf

Are many of you putting textFrames in your Masters? I thought it would
make sense to put them there, so that I could control the design of my
document in one central place, but since I must override each of these
frames in my pages, it seems to make little sense. In fact I had one
"base" master and several other masters which inherited from the base,
but it actually turned in to a giant mess because I needed to override
the objects (in script) and you must deal with overriding your the
PageItems of your MasterSpread's MasterSpread! It was a nightmare
because of how there is a very odd and shifting relationship between
the pageitem index numbers (which seem to be shared between my master
and the master that it was based on) however the pageitem index
numbers shift once I override one pageitem and all the indexes shifted
into some kind of random correspondance. The design of this object
model (in this rest) is a perfect example of one of the worst ways it
could have been designed.

ANYWAY, I have a document that has 6 different types of pages. All six
types of pages have come common textframes and tables, but all 6 also
have a different set of objects in one area. I'll be using scripts to
populate the data for this textframes, so what is a good way to
organize the document? One master for the common elements (textframes
and tables, and some rectangles) and a separate master for each of the
six pages, which are based on the first master? Or some clever use of
layers? Or should i just generate each page ENTIRELY from code (which
might make the best sense, because then I CAN actually control the
design from a single source (my code) since overriding masterpageitems
seems to defeat the purpose of having them...Or should I just create
the 6 pages as "templates" and then duplicate them (in script) as
needed?

(to complicate things even more, I must use VB.NET because I'm working
with Japanese and the VB6 controls don't support unicode.)

TIA!

Max Hodges
www.maxconsulting.us