"
Team:SUSTC-Shenzhen-A/Notebook1
From 2012.igem.org
| Line 82: | Line 82: | ||
} | } | ||
#talkbubble_b { | #talkbubble_b { | ||
| - | + | width: 544px; | |
| - | + | height:400px; | |
// background:#EFEFEF; | // background:#EFEFEF; | ||
| - | + | background:#ffffff; | |
| - | + | position: relative; | |
| - | + | -moz-border-radius: 0px; | |
| - | + | -webkit-border-radius: 0px; | |
| - | + | border-radius: 10px; | |
| - | + | font-family: Tahoma, Geneva, sans-serif; | |
| - | + | font-size: 13px; | |
| - | + | color:#333; | |
} | } | ||
#talkbubble_c1 { | #talkbubble_c1 { | ||
| Line 168: | Line 168: | ||
<img src="https://static.igem.org/mediawiki/2012/f/f1/Devidingline.jpg"> | <img src="https://static.igem.org/mediawiki/2012/f/f1/Devidingline.jpg"> | ||
<div> | <div> | ||
| - | + | <div id="talkbubble_b"> | |
<p class="title">Summerized Process</p> | <p class="title">Summerized Process</p> | ||
| - | <p> | + | <p><strong>Biosearch section1:</strong></p> |
| - | + | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.9~7.16</li> |
</ul> | </ul> | ||
<p>All of our teammates enjoyed learning object c and using Xcode to program some necessary parts of our user interface(e.g. combo box).</p> | <p>All of our teammates enjoyed learning object c and using Xcode to program some necessary parts of our user interface(e.g. combo box).</p> | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.17</li> |
</ul> | </ul> | ||
<p>In the first meeting, our group divided into two parts:UI & data. The main structure and initial division of work had been confirmed.</p> | <p>In the first meeting, our group divided into two parts:UI & data. The main structure and initial division of work had been confirmed.</p> | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.18</li> |
</ul> | </ul> | ||
<p>In this day we determined three parts of our work: categories, search list, and search results. We also disgusted the search methods. From now, all the members started our group-work with clear aims.</p> | <p>In this day we determined three parts of our work: categories, search list, and search results. We also disgusted the search methods. From now, all the members started our group-work with clear aims.</p> | ||
| Line 206: | Line 205: | ||
<p> week 7</p> | <p> week 7</p> | ||
<div class="sidebar_box_bottom"></div> | <div class="sidebar_box_bottom"></div> | ||
| - | + | </div> | |
</td> | </td> | ||
</tr> | </tr> | ||
| - | + | </table> | |
<table width="899" border="0" cellspacing="10" cellpadding="10"> | <table width="899" border="0" cellspacing="10" cellpadding="10"> | ||
| Line 215: | Line 214: | ||
<td><div id="talkbubble_c1"> | <td><div id="talkbubble_c1"> | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.21</li> |
</ul> | </ul> | ||
<p>Members of data group in search results broke through the main problem of data base. By loading data directly from xml file which provided by partsregistry.org (It couldn't be loaded only if it was changed some parts of the form) and send into mysql, we could easily get partname-based-data from our database. With this optimized new database, UI group could test their work with high efficiency.</p> | <p>Members of data group in search results broke through the main problem of data base. By loading data directly from xml file which provided by partsregistry.org (It couldn't be loaded only if it was changed some parts of the form) and send into mysql, we could easily get partname-based-data from our database. With this optimized new database, UI group could test their work with high efficiency.</p> | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.23</li> |
</ul> | </ul> | ||
<p>Discussing with Shenzhen Team, we were given a lot of advice of search methods and user interface. Knowing what users really needed, we got the ability to optimize the completed parts and improve the design of parts which would be added.</p> | <p>Discussing with Shenzhen Team, we were given a lot of advice of search methods and user interface. Knowing what users really needed, we got the ability to optimize the completed parts and improve the design of parts which would be added.</p> | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.25</li> |
</ul> | </ul> | ||
<p>The work of searching part (list and result) had been done!</p> | <p>The work of searching part (list and result) had been done!</p> | ||
<ul> | <ul> | ||
| - | <li | + | <li>7.27</li> |
</ul> | </ul> | ||
<p>All parts of our project had been combined and tested. Now we're trying to optimize the user interface with unified style.</p> | <p>All parts of our project had been combined and tested. Now we're trying to optimize the user interface with unified style.</p> | ||
| Line 237: | Line 236: | ||
| - | + | <!-- end of header --> | |
</body> | </body> | ||
</html> | </html> | ||
[[file:footbar.jpg]] | [[file:footbar.jpg]] | ||
Revision as of 08:40, 22 August 2012
Abstruct  The weekly notebook includes the work process of every teammate everyday. Here you can see the detailed steps of finishing the two projects for iGEM competition, and go through the days that our projects grow up with us together. 
Summerized Process Biosearch section1:
All of our teammates enjoyed learning object c and using Xcode to program some necessary parts of our user interface(e.g. combo box).
In the first meeting, our group divided into two parts:UI & data. The main structure and initial division of work had been confirmed.
In this day we determined three parts of our work: categories, search list, and search results. We also disgusted the search methods. From now, all the members started our group-work with clear aims. |
Notebook 
Abstruct Xcode Torial(week 1) Biosearch No.1(week2,3) week 2 week 3 Biosearch No.2(week4,5) Tinker Cell(week,6,7) week 6 week 7 |
Members of data group in search results broke through the main problem of data base. By loading data directly from xml file which provided by partsregistry.org (It couldn't be loaded only if it was changed some parts of the form) and send into mysql, we could easily get partname-based-data from our database. With this optimized new database, UI group could test their work with high efficiency.
Discussing with Shenzhen Team, we were given a lot of advice of search methods and user interface. Knowing what users really needed, we got the ability to optimize the completed parts and improve the design of parts which would be added.
The work of searching part (list and result) had been done!
All parts of our project had been combined and tested. Now we're trying to optimize the user interface with unified style. |
