Practical?

Maybe it's just me, but this multiple page thing seems like a pretty important thing to improve. I'm looking at either making improvements to our doc generator or implementing FMSpark, and there are many things I like about Spark...perhaps most importantly the fact that users never need to leave Browse mode.
...or so I thought...
I really think it's important that the user not have to worry about changing or adding Layouts depending on how long the letter is. That's not something I want my user having to even consider.
I'm wondering if it is possible to do the following. Seems pretty simple to me... (been out of FM programming mode for over a year now, bear with me!...)
1. Create multiple letter layouts: 1 page, 2 page, 3 page, ... 11 page
2. Insert script step in the merge and preview scripts (don't know exactly what they're called, I'm playing with the Demo) that figures out how long the layout content field is...
3. Insert series of if/thens that, based on the math, would chose the appropriate layout that would have the required number of pages to accomodate the length of the layout content field, and the signature block
User never even knows it is switching layouts to accomodate length. All he is thinking about is creating the template (the way it should be, in my opinion)
If this would work, I think this would be a very simple change to the product that would make it much more user friendly, and eliminate an issue that will continue to come up for your users (and potential buyers)...
Whatchu think, John?
...or so I thought...
I really think it's important that the user not have to worry about changing or adding Layouts depending on how long the letter is. That's not something I want my user having to even consider.
I'm wondering if it is possible to do the following. Seems pretty simple to me... (been out of FM programming mode for over a year now, bear with me!...)
1. Create multiple letter layouts: 1 page, 2 page, 3 page, ... 11 page
2. Insert script step in the merge and preview scripts (don't know exactly what they're called, I'm playing with the Demo) that figures out how long the layout content field is...
3. Insert series of if/thens that, based on the math, would chose the appropriate layout that would have the required number of pages to accomodate the length of the layout content field, and the signature block
User never even knows it is switching layouts to accomodate length. All he is thinking about is creating the template (the way it should be, in my opinion)
If this would work, I think this would be a very simple change to the product that would make it much more user friendly, and eliminate an issue that will continue to come up for your users (and potential buyers)...
Whatchu think, John?