Team:SUSTC-Shenzhen-A/week2

From 2012.igem.org

(Difference between revisions)
Line 1: Line 1:
-
{{Template:SUSTC/pd_template}}
+
{{Template:SUSTC_A3}}
<html>
<html>
<head>
<head>
Line 83: Line 83:
#talkbubble_b {
#talkbubble_b {
width: 544px;
width: 544px;
-
height:400px;
+
height:510px;
//  background:#EFEFEF;
//  background:#EFEFEF;
background:#ffffff;
background:#ffffff;
Line 122: Line 122:
#talkbubble_c3 {
#talkbubble_c3 {
   width: 862px;  
   width: 862px;  
-
   height:200px;  
+
   height:1400px;  
//  background:#EFEFEF;
//  background:#EFEFEF;
   background:#ffffff;
   background:#ffffff;
Line 137: Line 137:
   height:560px;  
   height:560px;  
//  background:#FAF0E6;
//  background:#FAF0E6;
-
  background:#f2eada;
+
//  background:#f2eada;
 +
background:#EfFFFF;
   position: relative;
   position: relative;
   -moz-border-radius:    10px;  
   -moz-border-radius:    10px;  
Line 160: Line 161:
<body >
<body >
-
<table width="899" border="0" cellspacing="10px" cellpadding="10px">
+
<table width="899" border="0" cellspacing="10px" cellpadding="10px" align="center">
        <tr>
        <tr>
          <td valign="top">
          <td valign="top">
<div id="talkbubble_b">
<div id="talkbubble_b">
-
               <p class="title">Week1: Torial of X-code</p>
+
               <p class="title">Week2</p>
-
              <p><strong>Biosearch section1:</strong></p>
+
               <ul>
               <ul>
-
                 <li>7.9~7.16</li>
+
                 <li>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>&nbsp;&nbsp;&nbsp;&nbsp;We chose mySQL as our database management system for its search functions. A program which could connect mySQL database and load data as well as using mySQL's search funcions was gotten. .</p>
               <ul>
               <ul>
                 <li>7.17</li>
                 <li>7.17</li>
               </ul>
               </ul>
-
               <p>In the first meeting, our group divided into two parts:UI &amp; data. The main structure and initial division of work had been confirmed.</p>
+
               <p>&nbsp;&nbsp;&nbsp;&nbsp;In the first meeting, our group divided into two parts:UI(part leader: Xiao Tong)& data(part leader:Mubing Zhou). UI members and data members works in pair. All the members made a draft of our project one--Bosearch and looked through partsregistry.org part by part carefully, so that we could choice the functions needed.</p>
-
              <ul>
+
              <ul> <li>7.18</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>&nbsp;&nbsp;&nbsp;&nbsp;In this day we determined three parts of our work: categories, search engine, and search result. We also disgusted the search methods. From now, all the members started our group-work with clear aims. </p>
-
                
+
               <p>&nbsp;&nbsp;&nbsp;&nbsp;Search Engine group included two members: Xiao Tong and Mubing Zhou. Their main work was to search keywords (or some other functions) which were input by user in the database and passed the summarized results to them. When user clicked one of the results for more details, the part-name was sent to Search Result group.</p>
 +
              <p>&nbsp;&nbsp;&nbsp;&nbsp;Search Result group included six members: group leader Xin Yang, Deng Pan, Jingyao Guo, Qijia Cheng, Yidan Pan, Yujun Zhao. The main goal of this group was to create an interface to accept the result(part name) of bio-brick searching (which was sent by the SE group),showing the details of this part. In this part, loading database was the most important thing . </p>
 +
              <p>&nbsp;&nbsp;&nbsp;&nbsp;Category group included four members: Chenchen Lv, Junqiu Zhang, Yiqi Jiang and Zili Fan. They would work on building category-formed-interface to show all the data in partsregistry.org, which simplifys the long spreadsheet into keyword-showing tables. </p>
 +
 
 +
 
</div>
</div>
Line 191: Line 194:
<img src="http://2012.igem.org/wiki/images/c/c9/Devidingline_side.jpg">
<img src="http://2012.igem.org/wiki/images/c/c9/Devidingline_side.jpg">
<p><a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/Notebook"><strong>Abstruct</strong></a></p>
<p><a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/Notebook"><strong>Abstruct</strong></a></p>
 +
<p><a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/JC"><strong>Journal Club</strong></a></p>
 +
<p><a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/FP"><strong>Final Project</strong></a></p>
<p><a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week1"><strong>Xcode Torial(week 1)</strong></a></p>
<p><a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week1"><strong>Xcode Torial(week 1)</strong></a></p>
<p><strong>Biosearch section1(week2,3)</strong></p>
<p><strong>Biosearch section1(week2,3)</strong></p>
Line 199: Line 204:
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week6">week 6</a></p>
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week6">week 6</a></p>
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 7</a></p>
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 7</a></p>
-
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 8</a></p>
+
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week8">week 8</a></p>
-
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 9</a></p>
+
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week9">week 9</a></p>
-
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 10</a></p>
+
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week10">week 10~12</a></p>
-
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 11</a></p>
+
 
-
<p>&nbsp;&nbsp;<a href="http://2012.igem.org/Team:SUSTC-Shenzhen-A/week7">week 12</a></p>
+
<div class="sidebar_box_bottom"></div>                     
<div class="sidebar_box_bottom"></div>                     
           </div>
           </div>
Line 209: Line 213:
             </tr>
             </tr>
</table>
</table>
-
 
+
<table width="899" border="0" cellspacing="10px" cellpadding="10px" align="center">
-
<table width="899" border="0" cellspacing="10" cellpadding="10">
+
<tr><td><div id="talkbubble_c3">
-
  <tr>
+
-
    <td><div id="talkbubble_c1">
+
<ul>
<ul>
-
                 <li>7.21</li>
+
                 <li>7.19</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>&nbsp;&nbsp;SE:Members discussed about the searching methods and searchstring. A picker was chosen for user to select the searching part(part name, discription and so on). </p>
-
              <ul>
+
<p>&nbsp;&nbsp;Xiao Tong: Designed the user interface included the form of spinner and the options it showed.</p>
-
                <li>7.23</li>
+
<p>&nbsp;&nbsp;Mubing Zhou: Tested the search methods (accurate search and fuzzy search).</p>
 +
<p>&nbsp;&nbsp;</p>
 +
<p>&nbsp;&nbsp;Category:Analyzing the target website, members determined to provide four kinds of showing type:parts by type;parts by function; parts by chassis and devices by type. Then members collected informations and codes ,in order to show a user friendly interface. </p>
 +
<p>&nbsp;&nbsp;Chenchen Lv:Attempted category's overall arrangement as table-formed.</p>
 +
<p>&nbsp;&nbsp;Junqiu Zhang: Designed the tone of category view.</p>
 +
<p>&nbsp;&nbsp;Yiqi Jiang: Attempted category's overall arrangement as folder-formed.</p>
 +
<p>&nbsp;&nbsp;Zili Fan: Designed the tone of category view.</p>
 +
<p>&nbsp;&nbsp;</p>
 +
<p>&nbsp;&nbsp;Search result: The team in charge of the database started to analyse the mysql files and collect all the titles. By comparing the database and the website, we found that the database was incomplete, which didn't contain the description written by different authors, and the structure was totally different from the website. In order to build a part-name-based search result, we needed to search the whole database again when SE returned us the part name and collected the result.   </p>
 +
<p>&nbsp;&nbsp;Xin Yang: Selected important parts of the 13 tables.</p>
 +
<p>&nbsp;&nbsp;Deng Pan: Designed the interface of search result</p>
 +
<p>&nbsp;&nbsp;Jingyao Guo: Tried to show details from several tables in one page as table form.</p>
 +
<p>&nbsp;&nbsp;Qijia Cheng:on vacation</p>
 +
<p>&nbsp;&nbsp;Yidan Pan: Tried to show details from several tables in one page as table form.</p>
 +
<p>&nbsp;&nbsp;Yujun Zhao: Tested to combine all the tables of the database.</p>
 +
<ul> <li>7.13</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>&nbsp;&nbsp;&nbsp;&nbsp;Achieved picture dragging and spinning functions. Also built a simple program that could show the coordinate of touched place when user touched the screen.</p>
-
              <ul>
+
<ul> <li>7.14</li>
-
                <li>7.25</li>
+
               </ul>
               </ul>
-
               <p>The work of searching part (list and result) had been done!</p>
+
               <p>&nbsp;&nbsp;&nbsp;&nbsp;Learned to create a table whose every row one-to-one corresponded to a particular key (and the key could be used to search the column). We also achieved the navigation function that we could went to different page by clicking different row of the table.</p>  
-
              <ul>
+
<ul> <li>7.15</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>&nbsp;&nbsp;&nbsp;&nbsp;Learned about memory management. We studied the way to load data from XML files, and add search function to the table we built before. That day we completed with the primary knowledge needed, then our project was started!</p>
-
</div>
+
</div></td></tr>
-
</td>
+
-
  </tr>
+
</table>
</table>
-
 
-
 
<!-- end of header -->
<!-- end of header -->
Line 240: Line 251:
</body>
</body>
</html>
</html>
-
[[file:footbar.jpg]]
+
[[file:footbar.jpg|center]]

Revision as of 03:48, 23 September 2012

Week2

  • 7.16

    We chose mySQL as our database management system for its search functions. A program which could connect mySQL database and load data as well as using mySQL's search funcions was gotten. .

  • 7.17

    In the first meeting, our group divided into two parts:UI(part leader: Xiao Tong)& data(part leader:Mubing Zhou). UI members and data members works in pair. All the members made a draft of our project one--Bosearch and looked through partsregistry.org part by part carefully, so that we could choice the functions needed.

  • 7.18

    In this day we determined three parts of our work: categories, search engine, and search result. We also disgusted the search methods. From now, all the members started our group-work with clear aims.

    Search Engine group included two members: Xiao Tong and Mubing Zhou. Their main work was to search keywords (or some other functions) which were input by user in the database and passed the summarized results to them. When user clicked one of the results for more details, the part-name was sent to Search Result group.

    Search Result group included six members: group leader Xin Yang, Deng Pan, Jingyao Guo, Qijia Cheng, Yidan Pan, Yujun Zhao. The main goal of this group was to create an interface to accept the result(part name) of bio-brick searching (which was sent by the SE group),showing the details of this part. In this part, loading database was the most important thing .

    Category group included four members: Chenchen Lv, Junqiu Zhang, Yiqi Jiang and Zili Fan. They would work on building category-formed-interface to show all the data in partsregistry.org, which simplifys the long spreadsheet into keyword-showing tables.

  • 7.19

  SE:Members discussed about the searching methods and searchstring. A picker was chosen for user to select the searching part(part name, discription and so on).

  Xiao Tong: Designed the user interface included the form of spinner and the options it showed.

  Mubing Zhou: Tested the search methods (accurate search and fuzzy search).

  

  Category:Analyzing the target website, members determined to provide four kinds of showing type:parts by type;parts by function; parts by chassis and devices by type. Then members collected informations and codes ,in order to show a user friendly interface.

  Chenchen Lv:Attempted category's overall arrangement as table-formed.

  Junqiu Zhang: Designed the tone of category view.

  Yiqi Jiang: Attempted category's overall arrangement as folder-formed.

  Zili Fan: Designed the tone of category view.

  

  Search result: The team in charge of the database started to analyse the mysql files and collect all the titles. By comparing the database and the website, we found that the database was incomplete, which didn't contain the description written by different authors, and the structure was totally different from the website. In order to build a part-name-based search result, we needed to search the whole database again when SE returned us the part name and collected the result.

  Xin Yang: Selected important parts of the 13 tables.

  Deng Pan: Designed the interface of search result

  Jingyao Guo: Tried to show details from several tables in one page as table form.

  Qijia Cheng:on vacation

  Yidan Pan: Tried to show details from several tables in one page as table form.

  Yujun Zhao: Tested to combine all the tables of the database.

  • 7.13

    Achieved picture dragging and spinning functions. Also built a simple program that could show the coordinate of touched place when user touched the screen.

  • 7.14

    Learned to create a table whose every row one-to-one corresponded to a particular key (and the key could be used to search the column). We also achieved the navigation function that we could went to different page by clicking different row of the table.

  • 7.15

    Learned about memory management. We studied the way to load data from XML files, and add search function to the table we built before. That day we completed with the primary knowledge needed, then our project was started!

Footbar.jpg