126 </ul> <p><b>Internal Relationships </b> </p> <p>The Versit libraries are designed |
126 </ul> <p><b>Internal Relationships </b> </p> <p>The Versit libraries are designed |
127 to provide a self contained set of tools. As such, they have no internal dependencies |
127 to provide a self contained set of tools. As such, they have no internal dependencies |
128 with other App-Services components. The diagram below gives an abstract illustration |
128 with other App-Services components. The diagram below gives an abstract illustration |
129 of the internal dependencies of the Versit components themselves. </p> <fig id="GUID-EF3BAA2A-3072-551A-B89C-99AB7F0A70DF"> |
129 of the internal dependencies of the Versit components themselves. </p> <fig id="GUID-EF3BAA2A-3072-551A-B89C-99AB7F0A70DF"> |
130 <title> Abstraction of Versit deliverables </title> |
130 <title> Abstraction of Versit deliverables </title> |
131 <image href="GUID-48D06D0E-C4D6-54F1-B603-7A75DEF669AA_d0e381534_href.png" placement="inline"/> |
131 <image href="GUID-48D06D0E-C4D6-54F1-B603-7A75DEF669AA_d0e375455_href.png" placement="inline"/> |
132 </fig> <p>As the diagram above illustrates, it is possible to make use of |
132 </fig> <p>As the diagram above illustrates, it is possible to make use of |
133 the Versit.dll library on its own. If vCard or vCalendar support is required |
133 the Versit.dll library on its own. If vCard or vCalendar support is required |
134 then the Versit library must be included as both vCard.dll and vCal.dll depend |
134 then the Versit library must be included as both vCard.dll and vCal.dll depend |
135 on it. </p> <p>It is also possible for users to develop their own Versit parsers |
135 on it. </p> <p>It is also possible for users to develop their own Versit parsers |
136 using the base classes provided in Versit.dll and not include the vCard and |
136 using the base classes provided in Versit.dll and not include the vCard and |
142 engine and the documentation associated to each should be referred to for |
142 engine and the documentation associated to each should be referred to for |
143 more detail. The two application engines that make use of Versit are the <xref href="GUID-40E64445-CBA3-59E4-A777-937609B311C9.dita">Contacts Model</xref> and <xref href="GUID-3A6BEF56-ADBF-543E-B70A-52195DE3E92A.dita">Calendar</xref> components. </p> </section> |
143 more detail. The two application engines that make use of Versit are the <xref href="GUID-40E64445-CBA3-59E4-A777-937609B311C9.dita">Contacts Model</xref> and <xref href="GUID-3A6BEF56-ADBF-543E-B70A-52195DE3E92A.dita">Calendar</xref> components. </p> </section> |
144 <section id="GUID-10536254-0D16-475C-82B3-451ADAFEC983"><title>API summary </title> <fig id="GUID-41DFB840-D409-5B34-949E-27E9B62A0F1E"> |
144 <section id="GUID-10536254-0D16-475C-82B3-451ADAFEC983"><title>API summary </title> <fig id="GUID-41DFB840-D409-5B34-949E-27E9B62A0F1E"> |
145 <title> Relationship between different classes of the Versit |
145 <title> Relationship between different classes of the Versit |
146 component </title> |
146 component </title> |
147 <image href="GUID-2A109FEC-5173-55FD-ACA8-3CAE48A93540_d0e381570_href.png" placement="inline"/> |
147 <image href="GUID-2A109FEC-5173-55FD-ACA8-3CAE48A93540_d0e375491_href.png" placement="inline"/> |
148 </fig> <table id="GUID-B009CAB5-2555-5AB2-AF90-41C7E61C2401"> |
148 </fig> <table id="GUID-B009CAB5-2555-5AB2-AF90-41C7E61C2401"> |
149 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
149 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
150 <thead> |
150 <thead> |
151 <row> |
151 <row> |
152 <entry>Class Name</entry> |
152 <entry>Class Name</entry> |