Reply to thread

Message

<blockquote data-quote="Janx" data-source="post: 5904627" data-attributes="member: 8835">Let's start at this layer:Let's assume there will be 2 kinds of markup, Lookups and Scripts.Lookups are for Tables and Blocks.&nbsp; They are framed with square brackets and the unique name of the table or block is inside. For example:this will lookup a dragon from a table [dragon].Lookups are pretty much exactly what you intended.At present, there are 2 kinds of Lookups:Tablethis does a die roll, looks up the result and returns the result.&nbsp; The result MAY have have markup to be processed for another LookUp or Script.BlockBlocks are rich text formatted, multi-line blobs of content.&nbsp; They can contain markup, and be referenced by tables, etc.&nbsp; These let you define stat blocks, descriptive text, whatever is meaty.Scripts need to be differentiated from Lookups so parsing is easier.&nbsp; Scripts are really for denoting dice rolls and logical/programming statements that clever users can make more powerful things happen.&nbsp; Scripts should use curly braces to define a script section.&nbsp; For example:This will show the result of 1d6 = {1d6}.Whenever the Parsing Engine is given content, it looks for {} or [] and replaces them in the original content with the correct content.&nbsp; If it sees [dragon] then it will find the Dragon table and replace that with the result.The parsing engine applies the same process to every result it returns, so a table result may have markup to indicate further processing is to be done.It is important that all Lookups be treated the same.&nbsp; The editor can easily manage handling renaming of a table because we can search all text in the system including lookup text for [oldname] and replace it with [newname].&nbsp; We can also look for infinite loops because when I am saving a table called &quot;MyTable&quot; I can find all other tables/blocks that mine uses and so on and see if [MyTable] occurs or not.Hopefully this writeup saves, and will be useful to you.</blockquote>

[QUOTE="Janx, post: 5904627, member: 8835"] Let's start at this layer: Let's assume there will be 2 kinds of markup, Lookups and Scripts. Lookups are for Tables and Blocks. They are framed with square brackets and the unique name of the table or block is inside. For example: this will lookup a dragon from a table [dragon]. Lookups are pretty much exactly what you intended. At present, there are 2 kinds of Lookups: Table this does a die roll, looks up the result and returns the result. The result MAY have have markup to be processed for another LookUp or Script. Block Blocks are rich text formatted, multi-line blobs of content. They can contain markup, and be referenced by tables, etc. These let you define stat blocks, descriptive text, whatever is meaty. Scripts need to be differentiated from Lookups so parsing is easier. Scripts are really for denoting dice rolls and logical/programming statements that clever users can make more powerful things happen. Scripts should use curly braces to define a script section. For example: This will show the result of 1d6 = {1d6}. Whenever the Parsing Engine is given content, it looks for {} or [] and replaces them in the original content with the correct content. If it sees [dragon] then it will find the Dragon table and replace that with the result. The parsing engine applies the same process to every result it returns, so a table result may have markup to indicate further processing is to be done. It is important that all Lookups be treated the same. The editor can easily manage handling renaming of a table because we can search all text in the system including lookup text for [oldname] and replace it with [newname]. We can also look for infinite loops because when I am saving a table called "MyTable" I can find all other tables/blocks that mine uses and so on and see if [MyTable] occurs or not. Hopefully this writeup saves, and will be useful to you. [/QUOTE]

Verification