Team:Berkeley Software/Eugene Implementation

From 2009.igem.org

(Difference between revisions)

Revision as of 21:12, 19 October 2009

Contents:

Implementation

Figure 1: Eugene Flow Diagram

Header File Creation
Header files give the language the functionality to access many already predefined Parts in the databases. For the purpose of convenient data exchange over the Internet, XML could be used to read information from a database. Then the data is converted into Eugene syntax to represent the header files. As a result the language definitions are not just abstract statements but are tied to existing designs. There are three main header files: PropertyDefintion.h, PartDefiniton.h and PartDeclaration.h shown in Figure 1.

back to Contents

Eugene Main File

The main .eug file can include the header files, which need to be specified at the top:

include PropertyDefintion.h, PartDefinition.h, PartDeclaration.h;

The main file will generally consist of custom Part definitions/declarations, device constructs, rule implementations and control statements.

back to Contents

@@ Line 2: / Line 2: @@
 <table align=center>
 <tr>
-<td>'''Contents:'''
+<td>'''<span id="contentMenu">Contents</span>''':
 <li>[[Team:Berkeley_Software/Eugene#Introduction|Introduction]]
 <li>[[Team:Berkeley_Software/Eugene#Language_Definition|Language Definition]]
@@ Line 18: / Line 18: @@
 [[Image:Eugene_Overview.jpg|900px|thumb|center|<p style="text-align: center;"><font size = "2"><span style="font-family: Georgia, serif;">Figure 1: Eugene Flow Diagram</span></font></p>]]<br>
 <b><font size="3">Header File Creation</font></b><br>
-Header files give the language the functionality to access many already predefined Parts in the databases. For the purpose of convenient data exchange over the Internet, XML could be used to read information from a database. Then the data is converted into Eugene syntax to represent the header files. As a result the language definitions are not just abstract statements but are tied to existing designs. There are three main header files: PropertyDefintion.h, PartDefiniton.h and PartDeclaration.h shown in Figure 1.<br><br>
+Header files give the language the functionality to access many already predefined Parts in the databases. For the purpose of convenient data exchange over the Internet, XML could be used to read information from a database. Then the data is converted into Eugene syntax to represent the header files. As a result the language definitions are not just abstract statements but are tied to existing designs. There are three main header files: PropertyDefintion.h, PartDefiniton.h and PartDeclaration.h shown in Figure 1.
+<br><p style="text-align: right;">[[#contentMenu|back to Contents]]</p>
-<b><font size="3">Eugene Main File</font></b><br>
+-----
+<span id="Conclusions"><H3>Eugene Main File</H3></span>
 The main .eug file can include the header files, which need to be specified at the top:
 <pre>
@@ Line 26: / Line 28: @@
 </pre>
 The main file will generally consist of custom [[Team:Berkeley_Software/Eugene#Part_Definition Part | Part definitions]]/[[Team:Berkeley_Software/Eugene#Part_Declaration |declarations]], [[Team:Berkeley_Software/Eugene#Devices| device constructs]], [[Team:Berkeley_Software/Eugene#Rules | rule implementations]] and [[Team:Berkeley_Software/Eugene#ConditionalSt| control statements]].
+<br><p style="text-align: right;">[[#contentMenu|back to Contents]]</p>