Reply to thread

Message

<blockquote data-quote="Janx" data-source="post: 5905446" data-attributes="member: 8835">We're making stuff up on the fly.&nbsp; Technically, Generator is a good word for what I called asset.&nbsp; Both tables and blocks are generators.And the List screen is closer to what you envisioned as &quot;pick a thing and click the Generate!&quot; button.the Main screen i describe is what most table-engines have as their UI to generate content.&nbsp; It's like the command-line interface to make the beast work.&nbsp; Let's call it the Console screen, and defer the details to later.The list and edit screen are REALLY what you need, no matter what.As you surmised, the GridView example is just to demonstrate what I'm talking about.&nbsp; It's a list with columns that you can sort by, filter, etc.&nbsp; if vBulletin has similar, great!to recap on current terminology I propose:<ul>
<li data-xf-list-type="ul">Generator: a table or a block.&nbsp; It has a name, and the user can run it to get results back.&nbsp; A Tag that names a Generator can be embedded in another table or block, enabling generation of complex things</li>
<li data-xf-list-type="ul">Table: A type of generator that rolls a dice result and looks up the result on a chart and returns that result.&nbsp; The result MAY have Tags in it to use other tables or blocks</li>
<li data-xf-list-type="ul">Block: a potentially large bit of formatted text that MAY have Tags in it to use other tables or blocks.&nbsp; Useful to define monster stat blocks with random hit points and treasure from the treasure tables, or room descriptions or even an entire adventure, and randomly generated each time based on using Tags.</li>
<li data-xf-list-type="ul">Tag: the markup in text that the Parser will find and run the named Generator to replace the Tag with its results.&nbsp; Tags begin and end with a square bracket [].</li>
<li data-xf-list-type="ul">Parser: the engine that interpret text content sent to it to identify Tags and run the appropriate Generator.</li>
<li data-xf-list-type="ul">Script: like a tag, but using curly braces {}.&nbsp; Script can be dice notation or other advanced functions.</li>
<li data-xf-list-type="ul">Dice Notation: the standard nomenclature for saying roll 2 six sided dice, add them up, then add 4.&nbsp; Ex: 2d6+4.&nbsp; Dice Notation enclosed ina&nbsp; Script tag will be executed and the script tag will be replaced with the results.</li>
</ul></blockquote>

[QUOTE="Janx, post: 5905446, member: 8835"] We're making stuff up on the fly. Technically, Generator is a good word for what I called asset. Both tables and blocks are generators. And the List screen is closer to what you envisioned as "pick a thing and click the Generate!" button. the Main screen i describe is what most table-engines have as their UI to generate content. It's like the command-line interface to make the beast work. Let's call it the Console screen, and defer the details to later. The list and edit screen are REALLY what you need, no matter what. As you surmised, the GridView example is just to demonstrate what I'm talking about. It's a list with columns that you can sort by, filter, etc. if vBulletin has similar, great! to recap on current terminology I propose: [LIST] [*]Generator: a table or a block. It has a name, and the user can run it to get results back. A Tag that names a Generator can be embedded in another table or block, enabling generation of complex things [*]Table: A type of generator that rolls a dice result and looks up the result on a chart and returns that result. The result MAY have Tags in it to use other tables or blocks [*]Block: a potentially large bit of formatted text that MAY have Tags in it to use other tables or blocks. Useful to define monster stat blocks with random hit points and treasure from the treasure tables, or room descriptions or even an entire adventure, and randomly generated each time based on using Tags. [*]Tag: the markup in text that the Parser will find and run the named Generator to replace the Tag with its results. Tags begin and end with a square bracket []. [*]Parser: the engine that interpret text content sent to it to identify Tags and run the appropriate Generator. [*]Script: like a tag, but using curly braces {}. Script can be dice notation or other advanced functions. [*]Dice Notation: the standard nomenclature for saying roll 2 six sided dice, add them up, then add 4. Ex: 2d6+4. Dice Notation enclosed ina Script tag will be executed and the script tag will be replaced with the results. [/LIST] [/QUOTE]

Verification