Team:SUSTC-Shenzhen-A/Notebook1

From 2012.igem.org

(Difference between revisions)
Line 215: Line 215:
</table>
</table>
-
<table width="899" border="0" cellspacing="10" cellpadding="10">
+
<table width="899" border="0" cellspacing="10" cellpadding="10" align="center">
   <tr>
   <tr>
     <td><div id="talkbubble_c1">
     <td><div id="talkbubble_c1">

Revision as of 12:57, 19 September 2012

Abstruct

image 2

  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:

  • 7.9~7.16

All of our teammates enjoyed learning object c and using Xcode to program some necessary parts of our user interface(e.g. combo box).

  • 7.17

In the first meeting, our group divided into two parts:UI & data. The main structure and initial division of work had been confirmed.

  • 7.18

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.

  • 7.21

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.

  • 7.23

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.

  • 7.25

The work of searching part (list and result) had been done!

  • 7.27

All parts of our project had been combined and tested. Now we're trying to optimize the user interface with unified style.

Footbar.jpg