"
Team:Berkeley Software/Eugene Implementation
From 2009.igem.org
(Difference between revisions)
Lbilitchenko (Talk | contribs) |
Adam z liu (Talk | contribs) |
||
| Line 15: | Line 15: | ||
----- | ----- | ||
<span id="Implementation"><H3>Implementation</H3></span> | <span id="Implementation"><H3>Implementation</H3></span> | ||
| - | Diagram | + | [[Image:Eugene_Overview.jpg|800px|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><br> |
<b><font size="3">Header File Creation</font></b><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 | + | 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. |
Revision as of 11:47, 18 October 2009
| Content:
|
 |
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.
