Reply to thread

Message

<blockquote data-quote="Janx" data-source="post: 5905675" data-attributes="member: 8835">ah yes, that's Dependency checking in developer parlance.&nbsp; the inifinite loop test helps detect that.&nbsp; Because we can collate the entire chain of tags an Asset has relations to, we can then verify that they all exist.Additionally, we can allow for the Parser to ignore tags that it cannot resolve (find an Assset for).&nbsp; So if it found [JanxTable1] in the text, but no such table existed, it would leave that tag in place in the output.&nbsp; It'll be pretty obvious to the user what happened.For a developer specification, I think you'll need:<ul>
<li data-xf-list-type="ul">glossary of terms</li>
<li data-xf-list-type="ul">DB table definitions</li>
<li data-xf-list-type="ul">screen explanations and sketches</li>
<li data-xf-list-type="ul">use case/user stories of usage examples</li>
<li data-xf-list-type="ul">syntax of Tags/Scripts</li>
<li data-xf-list-type="ul">syntax for Tables in Asset Body (what are the delimiters, structure for defining a table, similar to TableSmith or other tools</li>
<li data-xf-list-type="ul">syntax for Blocks in Asset Body (does it allow html or vBulletin formatting, etc) 
Parser flow chart/ pseudo-code explanation of its process</li>
</ul>For the parser, here's the basic pseudo code:[code]function string ParseText(string Input) {&nbsp; string Output = Input;&nbsp; List&lt;Tag&gt; arrTags = GetAllTags(Input);&nbsp; foreach(Tag t in arrrTags) {&nbsp; &nbsp; Output = t.ExecuteTag(Output);&nbsp; } //end of looping on arrTags&nbsp; return Output ;}class Tag {&nbsp; //properties and stuff would be defined here.&nbsp; function string ExecuteTag(string Output) {&nbsp; &nbsp; string result = this.TagValue;&nbsp; &nbsp; switch (Tag.Type) {&nbsp; &nbsp; &nbsp; case &quot;Asset&quot;:&nbsp; &nbsp; &nbsp; &nbsp; result = this.ExecuteAsset();&nbsp; &nbsp; &nbsp; &nbsp; break;&nbsp; &nbsp; &nbsp; case &quot;Script&quot;:&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; result = this.ExecuteScript();&nbsp; &nbsp; &nbsp; &nbsp; break; &nbsp; &nbsp; } //end of switching on tag type&nbsp; &nbsp; &nbsp; &nbsp; this.UpdateOutputforTag(result,Output);&nbsp; &nbsp; return Output;&nbsp; }}function string ExecuteAsset() {&nbsp;&nbsp; string result = this.GetAssetResult();&nbsp;&nbsp; &nbsp;&nbsp; result = ParseText(result);&nbsp;&nbsp; return result;}[/code]the ExecuteAsset() function would go look up the Asset in the asset library, and do a table result or block result and call ParseText() on that result before returning it.the ExecuteScript would be similar, but do whatever script parsing meant.This is all just pseudo-code.&nbsp; Not entirely correct, but shows the gist of the process for a programmer to follow.</blockquote>

[QUOTE="Janx, post: 5905675, member: 8835"] ah yes, that's Dependency checking in developer parlance. the inifinite loop test helps detect that. Because we can collate the entire chain of tags an Asset has relations to, we can then verify that they all exist. Additionally, we can allow for the Parser to ignore tags that it cannot resolve (find an Assset for). So if it found [JanxTable1] in the text, but no such table existed, it would leave that tag in place in the output. It'll be pretty obvious to the user what happened. For a developer specification, I think you'll need: [LIST] [*]glossary of terms [*]DB table definitions [*]screen explanations and sketches [*]use case/user stories of usage examples [*]syntax of Tags/Scripts [*]syntax for Tables in Asset Body (what are the delimiters, structure for defining a table, similar to TableSmith or other tools [*]syntax for Blocks in Asset Body (does it allow html or vBulletin formatting, etc) Parser flow chart/ pseudo-code explanation of its process [/LIST] For the parser, here's the basic pseudo code: [code]function string ParseText(string Input) { string Output = Input; List<Tag> arrTags = GetAllTags(Input); foreach(Tag t in arrrTags) { Output = t.ExecuteTag(Output); } //end of looping on arrTags return Output ; } class Tag { //properties and stuff would be defined here. function string ExecuteTag(string Output) { string result = this.TagValue; switch (Tag.Type) { case "Asset": result = this.ExecuteAsset(); break; case "Script": result = this.ExecuteScript(); break; } //end of switching on tag type this.UpdateOutputforTag(result,Output); return Output; } } function string ExecuteAsset() { string result = this.GetAssetResult(); result = ParseText(result); return result; } [/code] the ExecuteAsset() function would go look up the Asset in the asset library, and do a table result or block result and call ParseText() on that result before returning it. the ExecuteScript would be similar, but do whatever script parsing meant. This is all just pseudo-code. Not entirely correct, but shows the gist of the process for a programmer to follow. [/QUOTE]

Verification