Reply to thread

Message

<blockquote data-quote="PaleMage" data-source="post: 6197441" data-attributes="member: 34768">An example does more than thousend words.My Library generator loops $Quantity times until it reaches the amount of books desired, BUT it has to check also if the Running $Total of books produced has been exceeded. Currently I have no way to say to the loop to stop looping, because the second condition (Running Total) could happen before I generated all the $Quantity books. If I reach a condition while looping, I need a statement like {/exitloop} (usually is {/exit}) to say to the loop to stop and let me exit from looping. Currently I'm forced to run the remaining loops times (and, more important of all, use SERVER CPU TIME) to produce books that I will never show to users. This is what's for the {/exitloop} statement: save SERVER CPU TIME.Yes that's it. If You run the Great Knowledge Books generator, You get a $variable not set warning, because this generator is meant only to be called by the Great Knowledge Library generator, not for direct users use. You got the point, anyway.Definetely YES. Both Contents field and the new Operations field has to be able to run scripts, call tables and the like, but the only field that produces output will be, as currently is, Contents. The presence of the new Operations field give developers a place where to make calculation and $variables operations aside of user output, leaving all more clean and understandable.Feel free to continue asking for clarifications. PaleMage</blockquote>

[QUOTE="PaleMage, post: 6197441, member: 34768"] An example does more than thousend words. My Library generator loops $Quantity times until it reaches the amount of books desired, BUT it has to check also if the Running $Total of books produced has been exceeded. Currently I have no way to say to the loop to stop looping, because the second condition (Running Total) could happen before I generated all the $Quantity books. If I reach a condition while looping, I need a statement like {/exitloop} (usually is {/exit}) to say to the loop to stop and let me exit from looping. Currently I'm forced to run the remaining loops times (and, more important of all, use SERVER CPU TIME) to produce books that I will never show to users. This is what's for the {/exitloop} statement: [B]save SERVER CPU TIME[/B]. Yes that's it. If You run the [B]Great Knowledge Books[/B] generator, You get a $variable not set warning, because this generator is meant only to be called by the [B]Great Knowledge Library[/B] generator, not for direct users use. You got the point, anyway. Definetely YES. Both [I]Contents[/I] field and the new [I]Operations[/I] field has to be able to run scripts, call tables and the like, but the only field that produces output will be, as currently is, [B]Contents[/B]. The presence of the new [B]Operations[/B] field give developers a place where to make calculation and $variables operations aside of user output, leaving all more clean and understandable. Feel free to continue asking for clarifications. PaleMage [/QUOTE]

Verification