Team:Berkeley Software/Eugene Implementation

From 2009.igem.org

(Difference between revisions)
(New page: {{Template:BerkeleySoftwareHeader}} <br><br> <table align=center> <tr> <td>'''Content:''' <li>Intro <li>[[Team:Berkeley_Software/Eugene#Language_Definitio...)
Line 6: Line 6:
<li>[[Team:Berkeley_Software/Eugene#Language_Definition|Language Definition]]
<li>[[Team:Berkeley_Software/Eugene#Language_Definition|Language Definition]]
<li>[[Team:Berkeley_Software/Eugene#Examples|Examples]]
<li>[[Team:Berkeley_Software/Eugene#Examples|Examples]]
-
<li>[[#Implementation|Implementation]]</td>
+
<li>[[#Implementation|Implementation]]
 +
<li>[[Team:Berkeley_Software/Eugene_Results#Conclusions|Conclusions]]</td>
<td>&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;</td>
<td>&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;</td>
<td><center>[[Image:Eugene.png|112px]]</center></td>
<td><center>[[Image:Eugene.png|112px]]</center></td>

Revision as of 03:17, 17 October 2009



Content:
  • Intro
  • Language Definition
  • Examples
  • Implementation
  • Conclusions
  •           
    Eugene.png


    Implementation

    Diagram to tie everything

    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 ????.