1 = Roadmap = 2 3 Some future objectives for the software. 4 5 == HTML Parsing == 6 7 Parsing of HTML fragments would be done to permit translation into the Moin 8 document tree. This would then allow round-trip conversion: 9 10 ########## A graph showing the process is given below... 11 12 {{{#!graphviz 13 //format=svg 14 //transform=notugly 15 digraph htmlparsing { 16 node [shape=box,fontsize="13.0",fontname="Helvetica",tooltip="The MoinLight architecture"]; 17 edge [tooltip="The MoinLight architecture"]; 18 rankdir=LR; 19 20 moin [label="Moin content",shape=folder,style=filled,fillcolor=cyan]; 21 22 subgraph { 23 rank=same; 24 moinparser [label="Moin parser"]; 25 moinserialiser [label="Moin serialiser"]; 26 } 27 28 subgraph { 29 rank=same; 30 tree1 [label="Document tree",shape=folder,style=filled,fillcolor=cyan]; 31 tree2 [label="Document tree",shape=folder,style=filled,fillcolor=cyan]; 32 } 33 34 subgraph { 35 rank=same; 36 htmlserialiser [label="HTML serialiser"]; 37 htmlparser [label="HTML parser"]; 38 } 39 40 html [label="HTML content",shape=folder,style=filled,fillcolor=cyan]; 41 42 moin -> moinparser -> tree1 -> htmlserialiser -> html -> htmlparser -> tree2 -> moinserialiser -> moin; 43 } 44 }}} 45 46 ######## 47 48 Pages could be retained for storage in Moin format, presented in a Web browser 49 in HTML, edited using HTML editing controls, and then converted back for 50 storage. 51 52 In order to maintain various details of the original document, additional 53 annotations would be employed in the generated HTML. Such annotations would 54 appear within `class` attribute values, encoding details of the original 55 content such as indentation, padding and other aspects of that content which 56 are superfluous or inappropriate to the core HTML representation of the 57 document, but which can be interpreted in order to restore the form of the 58 original document.