Team:Tec-Monterrey/projectdescription

From 2011.igem.org

(Difference between revisions)
 
(92 intermediate revisions not shown)
Line 1: Line 1:
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 +
 +
<title>wiki</title>
<title>wiki</title>
<style type="text/css">
<style type="text/css">
<!--
<!--
#top-section {
#top-section {
-
  background-color: #ffffff;
+
      height: 100px;
-
  height: 100px;
+
   border: none;
   border: none;
-
 
   height:20px
   height:20px
}
}
Line 15: Line 15:
   position: absolute;
   position: absolute;
   display: none;
   display: none;
-
   background-color:#000000;
+
    
 +
}
 +
#footer-box {
 +
display:none;
 +
}
 +
 
 +
 
 +
#catlinks {
 +
    display:none;
}
}
#search-controls {
#search-controls {
   display: none;
   display: none;
-
}
 
-
  #menubar.left-menu {
 
-
  position: absolute;
 
-
  top:0px;
 
-
  left:0px;
 
-
  display:none; 
 
}
}
-
#menubar.right-menu {
+
#menubar { background: none repeat transparent; }
-
  background-color: #FFFFFF;
+
 
-
  position: absolute;
+
 
-
  top:0px;
+
#menubar ul li a { color: white; }
-
  right:0px;
+
-
}
 
.right-menu li a {
.right-menu li a {
-
    background-color: #FFFFFF;
+
color: black;
-
    color: #002BB8;
+
background: none repeat transparent;
-
    padding: 0 15px 0 0;
+
}
}
-
.left-menu li a {
+
 
-
     background-color: #FFFFFF;
+
#content {
-
     color: #002BB8;
+
     background: none repeat scroll 0 0 transparent;
-
     padding: 0 15px 0 0;
+
     border-left: 0 solid;
 +
     border-right: 0 solid;
 +
}
 +
#content{
 +
    width: 80%;
}
}
-
 
#headover ul{
#headover ul{
Line 60: Line 62:
body {
body {
-
font: 11px Tahoma, Geneva, sans-serif;
+
font: 12px Tahoma, Geneva, sans-serif;
-
background-image: url(
+
background-image: url(https://static.igem.org/mediawiki/2011/4/43/Lefondoleposter.png);
-
 
+
        background-repeat:no-repeat;
-
 
+
      background-size: 100%;
-
https://static.igem.org/mediawiki/2011/f/f4/Fondo03.png);
+
margin: 0;
margin: 0;
padding: 0;
padding: 0;
margin-left: 10%;
margin-left: 10%;
margin-right: 10%;
margin-right: 10%;
-
color: #013469;
+
color: #FFFFF;
}
}
/* ~~ Element/tag selectors ~~ */
/* ~~ Element/tag selectors ~~ */
-
ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
+
ul, ol, dl {
padding: 0;
padding: 0;
margin: 0;
margin: 0;
}
}
h1, h2, h3, h4, h5, h6, p {
h1, h2, h3, h4, h5, h6, p {
-
margin-top: 0; /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
+
margin-top: 0;
padding-right: 10px;
padding-right: 10px;
-
padding-left: 10px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
+
padding-left: 10px;  
}
}
-
a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
+
a img {  
border: none;
border: none;
}
}
-
/* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
+
 
a:link {
a:link {
-
text-decoration: underline; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
+
color: #F90;
color: #F90;
}
}
Line 95: Line 96:
text-decoration: underline;
text-decoration: underline;
}
}
-
a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
+
a:hover, a:active, a:focus {  
text-decoration: none;
text-decoration: none;
}
}
-
/* ~~ this container surrounds all other divs giving them their percentage-based width ~~ */
+
 
.container {
.container {
-
width: 90%;
+
width: 100%;
-
max-width: 1260px;/* a max-width may be desirable to keep this layout from getting too wide on a large monitor. This keeps line length more readable. IE6 does not respect this declaration. */
+
max-width: 1260px;
-
min-width: 780px;/* a min-width may be desirable to keep this layout from getting too narrow. This keeps line length more readable in the side columns. IE6 does not respect this declaration. */
+
min-width: 780px;
-
background: #FFF;
+
overflow: hidden;  
-
margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout. It is not needed if you set the .container's width to 100%. */
+
  color:#FFF;
-
overflow: hidden; /* this declaration makes the .container clear all floated columns within it. */
+
}
}
-
/* ~~ These are the columns for the layout. ~~
 
-
1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
 
-
 
-
2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
 
-
 
-
3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
 
-
 
-
4) If you prefer your nav on the right instead of the left, simply float these columns the opposite direction (all right instead of all left) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
 
-
 
-
*/
 
.sidebar1 {
.sidebar1 {
float: left;
float: left;
-
width: 20%;
+
width: 15%;
-
background: #FFF;
+
        padding-bottom: 10px;
-
padding-bottom: 10px;
+
background-color:#04191d;
 +
-moz-border-radius: 8px;
 +
-webkit-border-radius: 8px;
}
}
.content {
.content {
-
padding: 10px 0;
+
padding: none;
width: 80%;
width: 80%;
float: left;
float: left;
-
background: #FFF;
+
}
}
-
/* ~~ This grouped selector gives the lists in the .content area space ~~ */
+
 
.content ul, .content ol {  
.content ul, .content ol {  
padding: 0 15px 15px 40px;
padding: 0 15px 15px 40px;
-
/* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
 
}
}
-
/* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
+
 
ul.nav {
ul.nav {
-
list-style: none; /* this removes the list marker */
+
list-style: none;  
-
border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
+
border-top:none;  
-
margin-bottom: 15px; /* this creates the space between the navigation on the content below */
+
margin-bottom: 15px;
 +
 
}
}
ul.nav li {
ul.nav li {
-
border-bottom: 1px solid #FFF; /* this creates the button separation */
+
border-bottom: 0px solid #04191d;  
 +
 
}
}
-
ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
+
ul.nav a, ul.nav a:visited {  
 +
 
padding: 5px 5px 5px 15px;
padding: 5px 5px 5px 15px;
-
display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
+
display: block;  
text-decoration: none;
text-decoration: none;
-
background: #FFF;
+
color:#FFF;
-
color:#013469;;
+
}
}
ul.nav a:hover, ul.nav a:active, ul.nav a:focus {  
ul.nav a:hover, ul.nav a:active, ul.nav a:focus {  
-
background: #f6af1b; /*float amarillo*/
+
background: #339dff; /*float amarillo*/
color: #FFF;
color: #FFF;
}
}
-
/* ~~miscellaneous float/clear classes~~ */
+
.frame {
-
.fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
+
font:12px arial;
 +
width:700;
 +
height:350;
 +
max-height: 350px;
 +
border:none;
 +
overflow:auto;
 +
border:0px solid black;
 +
padding:5;
 +
}
 +
.fltrt {   
float: right;
float: right;
margin-left: 8px;
margin-left: 8px;
}
}
-
.fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
+
.fltlft {  
float: left;
float: left;
margin-right: 8px;
margin-right: 8px;
}
}
-
.clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the overflow:hidden on the .container is removed */
+
.clearfloat {  
clear:both;
clear:both;
height:0;
height:0;
Line 183: Line 185:
.panel, .panelcollapsed  
.panel, .panelcollapsed  
{
{
-
margin: 5px;
+
margin: 3px;
width: auto;
width: auto;
-moz-border-radius: 4px;
-moz-border-radius: 4px;
-webkit-border-radius: 4px;
-webkit-border-radius: 4px;
-
border-top-width: 1px;
+
border-top-width: 10px;
-
border-right-width: 1px;
+
border-right-width: 0px;
-
border-bottom-width: 1px;
+
border-bottom-width: 10px;
-
border-left-width: 1px;
+
border-left-width: 3px;
padding-bottom: 5px;
padding-bottom: 5px;
 +
        color: #FFF;
}
}
 +
 +
 +
table {
 +
    background: none repeat scroll 0 0 transparent}
 +
/* panel heading */
/* panel heading */
.panel h2, .panelcollapsed h2  
.panel h2, .panelcollapsed h2  
{
{
 +
        color: #FFF;
font-weight: normal;
font-weight: normal;
margin: 0px;
margin: 0px;
-
padding: 4px;
+
padding: 0px;
-moz-border-radius: 3px;
-moz-border-radius: 3px;
-webkit-border-radius: 3px;
-webkit-border-radius: 3px;
 +
border-bottom: 0px solid #04191d;
 +
}
}
/* panel heading on rollover */
/* panel heading on rollover */
.panel h2:hover, .panelcollapsed h2:hover {
.panel h2:hover, .panelcollapsed h2:hover {
-
background-color: #FC3;
+
background-color: #339dff;
color: #FFF;
color: #FFF;
}
}
Line 222: Line 233:
{
{
overflow: hidden;
overflow: hidden;
-
font-size: 12px;
+
font-size: 14px;
}
}
Line 231: Line 242:
</style><!--[if lte IE 7]>
</style><!--[if lte IE 7]>
<style>
<style>
-
.content { margin-right: -1px; } /* this 1px negative margin can be placed on any of the columns in this layout with the same corrective effect. */
+
.content { margin-right: -1px; }
-
ul.nav a { zoom: 1; }  /* the zoom property gives IE the hasLayout trigger it needs to correct extra whiltespace between the links */
+
ul.nav a { zoom: 1; }   
</style>
</style>
<![endif]-->
<![endif]-->
Line 238: Line 249:
<script type="text/javascript">
<script type="text/javascript">
<!--
<!--
 +
i = 0
 +
var speed = 10
-
function changeImg(n) {
+
function scrollDown() {
-
+
i = i + speed
-
//url goes here
+
var div = document.getElementById("frame1")
-
var imgname = new Array();
+
div.scrollTop = i
-
imgname[0] = "/a.jpg";
+
if (i > div.scrollHeight - 300) {i = 350}
-
imgname[1] = "/b.jpg";
+
t1=setTimeout("scrollDown()",100)
-
imgname[2] = "/c.jpg";
+
}
-
imgname[3] = "/d.jpg";
+
function scrollUp() {
-
imgname[4] = "/e.jpg";
+
i = i - speed
-
+
var div = document.getElementById("frame1")
-
var name = imgname[n];
+
div.scrollTop = i
-
document.getElementById('imagered').src=name;
+
if (i < 0) {i = 0}
 +
t1=setTimeout("scrollUp()",100)
}
}
Line 338: Line 352:
var stepHeight = contentHeight / PANEL_ANIMATION_STEPS;
var stepHeight = contentHeight / PANEL_ANIMATION_STEPS;
var direction = (!expanding ? -1 : 1);
var direction = (!expanding ? -1 : 1);
-
+
if (direction > 0)
 +
collapseAll();
setTimeout(function(){animateStep(panelContent,1,stepHeight,direction)}, PANEL_ANIMATION_DELAY);
setTimeout(function(){animateStep(panelContent,1,stepHeight,direction)}, PANEL_ANIMATION_DELAY);
}
}
Line 454: Line 469:
</script>
</script>
-
</head><body>
 
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
</head>
 +
<body>
<div class="container">
<div class="container">
   
   
<div class="topbar">  
<div class="topbar">  
-
     <div style="background-color:#FFF;">
+
     <div style="filter:alpha(opacity=70);opacity:.7;">
-
 
+
   
-
<!--this will hold the search bar languages and logos -->
+
 
-
    <p> <img src="https://static.igem.org/mediawiki/igem.org/2/20/Logotec.png" alt="ITESM" name="teclogo" width="146" height="52" id="teclogo">  
+
<img src="https://static.igem.org/mediawiki/2011/2/20/Logotec.png" alt="ITESM" name="teclogo" width="146" height="52" id="teclogo">  
-
    <a href="https://2011.igem.org/Main_Page"><img src="https://static.igem.org/mediawiki/igem.org/7/73/Logoigemsmall.png" alt="iGEM" name="logoigem" width="70" height="61" id="logoigem"></a> </p>
+
      <a href="https://2011.igem.org/Main_Page"><img src="https://static.igem.org/mediawiki/2011/7/73/Logoigemsmall.png" alt="iGEM" name="logoigem" width="70" height="61" id="logoigem"></a>
-
</div>  
+
    <p>&nbsp;</p>
-
+
    <p>&nbsp;</p>
-
+
  </div>
 +
 
   <div class="sidebar1">
   <div class="sidebar1">
     <ul class="nav">
     <ul class="nav">
       <p>&nbsp;</p>
       <p>&nbsp;</p>
-
       <!--this is our menu! D: hurrfff durrff herpa derpa-->
+
       <!--this is our menu! D: -->
       <li>
       <li>
       <div class="panelcollapsed">
       <div class="panelcollapsed">
Line 476: Line 503:
     <div class="panelcontent" style="">
     <div class="panelcontent" style="">
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">home</a></p>
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">home</a></p>
-
<p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectdescription">abstract</a></p>
+
    <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectdescription">abstract</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">videos</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/video">videos</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">step by step</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/stepbystep">step by step</a></p>
            
            
          
          
Line 489: Line 516:
   <h2>PROJECT</h2>
   <h2>PROJECT</h2>
     <div class="panelcontent" style="">
     <div class="panelcontent" style="">
-
<p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectdescription">description</a></p>
+
   
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">parts</a></p>
+
                  <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectoverview">overview</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">modeling</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectparts">parts</a></p>
 +
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectmodeling">genetic frame</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectresults/methods">methods</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectresults">results</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/teamha">human approach</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectprotocols">protocols</a><p>
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/safetypage">safety</a></p>
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/safetypage">safety</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">notebook</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/projectnotebook">notebook</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">results</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/sampledata">sample data</a></p>
-
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey">achievements</a></p>
+
 
-
    </div>
+
          </div>
</div>
</div>
       </li>
       </li>
Line 505: Line 537:
   <h2>TEAM</h2>
   <h2>TEAM</h2>
     <div class="panelcontent">
     <div class="panelcontent">
-
<p><a href="https://2011.igem.org/Team:Tec-Monterrey">members</a></p>
+
 
-
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey">gallery</a></p>
+
    <p><a href="https://2011.igem.org/Team:Tec-Monterrey/teammembers">members</a></p>
-
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey">profile</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/teaminstallations">headquarters</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">installations</a></p>
+
-
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey">human approach</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/microcongreso">micro congress</a></p>
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/microcongreso">micro congress</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">friends</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/teamfriends">friends</a></p>
-
    </div>
+
 
 +
</div>
</div>
</div>
-
       </li><li>
+
       </li>
 +
  <li>
       <div class="panelcollapsed">
       <div class="panelcollapsed">
-
  <h2>EXTRAS</h2>
+
        <h2>EXTRAS</h2>
     <div class="panelcontent">
     <div class="panelcontent">
-
<p><a href="https://2011.igem.org/Team:Tec-Monterrey">site map</a></p>
+
<p><a href="https://2011.igem.org/Team:Tec-Monterrey/sitemap">site map</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">sponsors</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/sponsorsplatinum">sponsors platinum</a></p>
-
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey">follow us!</a></p>
+
             <p><a href="https://2011.igem.org/Team:Tec-Monterrey/sponsorsgold">sponsors gold</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/sponsorssilver">sponsors silver</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/specialthanks">special thanks</a></p>
 +
            <p><a href="https://2011.igem.org/Team:Tec-Monterrey/followus">follow us!</a></p>
     </div>
     </div>
-
</div>
+
  </div>
       </li>
       </li>
-
    </ul>
+
 
-
    <p>&nbsp;</p>
+
</ul>
-
    <p>&nbsp;</p>
+
 
-
    <p>&nbsp;</p>
+
-
<p>&nbsp;</p>
+
-
    <p>&nbsp;</p>
+
-
    <p>&nbsp;</p>
+
-
<p>&nbsp;</p>
+
-
<p>&nbsp;</p>
+
</div>
</div>
    
    
<div class="content">
<div class="content">
-
  <!--in sub pages, this divisions should be comments! :D-->
+
<div style="
-
 
+
text-align:center;">
-
  <div class="banner">  
+
-
          
+
<!--in sub pages, this divisions should be comments! :D-->
-
    <div style="text-align: right;background-color:#FFF;">
+
         <div style="  
-
    <p>&nbsp;</p>
+
padding:25px 50px;
-
    <p><a href="https://2011.igem.org/Team:Tec-Monterrey"><img src="https://static.igem.org/mediawiki/igem.org/4/4f/Renderbanner2.png" alt="tec monterrey 2011" name="banner" width="513" height="155" id="banner"></a></p>
+
background-color:#04191d;
-
   
+
color:#333;
-
    </div>
+
text-align:left;
-
   
+
margin:5px 30px;">
-
  </div> 
+
   
   
-
 
+
</head>
 +
 
 +
<body>
 +
<div align="justify">
 +
<div style="-moz-border-radius: 4px;-webkit-border-radius: 4px;">
 +
<div class="frame" id="frame1" style="background-color:#e5e5e5;">
 +
<br>
      
      
-
 
 
-
 
 
-
 
 
-
  <div class="contenido">
 
-
       
 
-
    <div style="
 
-
  text-align: center;
 
-
  background:url(https://static.igem.org/mediawiki/igem.org/e/ec/Topquicklink.png);
 
-
  background-repeat:no-repeat;
 
-
        background-position:top;
 
-
  background-color:#FFF;">
 
-
   
 
-
   
 
-
    <p>PROJECT DESCRIPTION</p>
 
-
<p>&nbsp;</p>
 
-
    <p class="textojustif"> text will be here soon! :D <br />
 
-
      </p>
 
-
</div>
 
-
 
 
-
 
 
-
  <!--uncomment this part in sub pages so you may edit properly-->
 
-
  <!--
 
-
  <h1>Instructions</h1>
 
-
<p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the liquid layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
 
-
    <h2>Clearing</h2>
 
-
    <p>Because all the columns are floated, this layout uses overflow:hidden on the .container. This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If you have a large element that protrudes outside the .container, it will appear to be cut off. You also won't be able to use negative margins or absolute positioning with negative values to pull elements outside the .container or they will also won't display outside the .container.</p>
 
-
    <p>If you need to use these properties, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
 
-
    <h3>Footer</h3>
 
-
    <p>Adding a footer following the columns, yet still inside the .container, will cause this overflow:hidden clearing method to fail. You can place a .footer into a second .container outside the first one with no detrimental effects. The simplest choice may be to start with a layout containing headers and footers and remove the header to utilize the clearing methods in that layout type.</p>
 
-
    <h4>Internet Explorer Conditional Comments</h4>
 
-
    <p>These liquid layouts contain an Internet Explorer Conditional Comment (IECC) to correct two issues. </p>
 
-
    <ol>
 
-
      <li>Browsers are inconsistent in the way they round div sizes in percent-based layouts. If the browser must render a number like 144.5px or 564.5px, they have to round it to the nearest whole number. Safari and Opera round down, Internet Explorer rounds up and Firefox rounds one column up and one down filling the container completely. These rounding issues can cause inconsistencies in some layouts. In this IECC there is a 1px negative margin to fix IE. You may move it to any of the columns (and on either the left or right) to suit your layout needs.</li>
 
-
      <li>The zoom property was added to the anchor within the navigation list since, in some cases, extra white space will be rendered in IE6 and IE7. Zoom gives IE its proprietary hasLayout property to fix this issue.</li>
 
-
    </ol>
 
-
    <h4>Backgrounds</h4>
 
-
    <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.end .content </p>-->
 
-
</div>
 
-
  <!-- end .container --></div>
 
 +
-
</div></div></body></html>
+
<center><img src="https://static.igem.org/mediawiki/2011/9/94/Abstractimg01.png" alt="" name="" width="200" height="50" id="tgo"> </center>
 +
<br>
 +
    <p class="textojustif">  Production of sugarcane used to be a high profit activity in the Mexican industry. Nonetheless, the increasing demand of high fructose syrup has become a rising threat to most sugar companies. Our project expects to apply synthetic biology to use sugar obtained from sugarcane in an industrial sugar-fructose process, intending to make it simpler and more profitable. The new genetic construct will be able to immobilize invertase by fusing it to bacterial natural membrane protein fragments through a technique for cell surface display. This system will catalyze the transformation of sucrose into fructose directly, without the need of any chemical or mechanical purification process to obtain the enzyme, reducing the amount of unit operations, and cutting production costs. Also, we will use the same principle to immobilize cellulase, converting cellulose from bagasse into useful substrate for biofuel production.
 +
<br>
 +
<br>
 +
 
 +
</p>
 +
</div>
 +
<hr>
 +
<br/>
 +
<input type="button" value="  Up  " onmouseover="scrollUp()" onmouseout="clearTimeout(t1)">
 +
<input type="button" value=" Down " onmouseover="scrollDown()" onmouseout="clearTimeout(t1)">
 +
</div></body></html>

Latest revision as of 20:48, 20 October 2011

wiki

iGEM

 

 



Production of sugarcane used to be a high profit activity in the Mexican industry. Nonetheless, the increasing demand of high fructose syrup has become a rising threat to most sugar companies. Our project expects to apply synthetic biology to use sugar obtained from sugarcane in an industrial sugar-fructose process, intending to make it simpler and more profitable. The new genetic construct will be able to immobilize invertase by fusing it to bacterial natural membrane protein fragments through a technique for cell surface display. This system will catalyze the transformation of sucrose into fructose directly, without the need of any chemical or mechanical purification process to obtain the enzyme, reducing the amount of unit operations, and cutting production costs. Also, we will use the same principle to immobilize cellulase, converting cellulose from bagasse into useful substrate for biofuel production.


Retrieved from "http://2011.igem.org/Team:Tec-Monterrey/projectdescription"