Team:Warsaw/Software

From 2010.igem.org

(Difference between revisions)
 
(One intermediate revision not shown)
Line 32: Line 32:
<p>
<p>
-
<b>BioBrick Manager</b> is extremely useful tool which helps you with <b>planning your experiments</b> or <b>preparing printable instructions</b> for others. It allows user to download biobricks from partsregistry.org, connect them in order to obtain new parts, save resulting bricks as XML files and - what is the most important thing - to <b>get protocol for creating that particular biobrick</b>!  
+
<b>BioBrick Manager</b> is extremely useful tool which helps you with <b>planning your experiments</b> or <b>preparing printable instructions</b> for others. It allows the user to download biobricks from partsregistry.org, connect them in order to obtain new parts, save resulting bricks as XML files and - what is the most important thing - to <b>get protocol for creating that particular biobrick</b>!  
</p>
</p>
<br/>
<br/>
Line 49: Line 49:
</p>
</p>
<p>
<p>
-
What's more, a lot of our effort went into designing BioBrick Manager to be as <b>friendly for users</b> as possible:  
+
What's more, a lot of our effort went into designing BioBrick Manager to be as <b>user-friendly</b> as possible:  
</p>
</p>
Line 64: Line 64:
<br/><br/>
<br/><br/>
<div class="note">Implementation and challenges</div>
<div class="note">Implementation and challenges</div>
-
<p>Biobrick manager is implemented in <a href=http://code.google.com/intl/en-EN/webtoolkit/>Google Web Toolkit</a> and  
+
<p>Biobrick manager is implemented in <b><a href=http://code.google.com/intl/en-EN/webtoolkit/>Google Web Toolkit</a></b> and  
-
<a href="http://code.google.com/intl/en-EN/appengine/">Google App Engine (Java)</a>. Those technologies enable  
+
<b><a href="http://code.google.com/intl/en-EN/appengine/">Google App Engine (Java)</a></b>. Those technologies enable  
easy web application development by "compiling" Java code (client-side) to JavaScript.</p>
easy web application development by "compiling" Java code (client-side) to JavaScript.</p>
<p>Almost everything is done by client - XML operations, drawing bricks, connecting them. Server is  
<p>Almost everything is done by client - XML operations, drawing bricks, connecting them. Server is  
used for downloading information from registry or files and saving files.</p>
used for downloading information from registry or files and saving files.</p>
-
<p>Source code is available <a href=http://subversion.assembla.com/svn/brickmanager>via SVN</a>.  
+
<p><b>Source code is available</b> <a href=http://subversion.assembla.com/svn/brickmanager>via SVN</a>.  
Application is hosted using Google infrastructure at  
Application is hosted using Google infrastructure at  
-
<a href=http://brickmanager.appspot.com>http://brickmanager.appspot.com</a>.  
+
<b><a href=http://brickmanager.appspot.com>http://brickmanager.appspot.com</a></b>.  
-
It is licensed under <a href=http://www.gnu.org/licenses/agpl-3.0.html>AGPL</a>.</p>
+
It is <b>licensed under <a href=http://www.gnu.org/licenses/agpl-3.0.html>AGPL</a></b>.</p>

Latest revision as of 21:57, 27 October 2010


Example Tabs

BioBrick manager


What can I use it for?

BioBrick Manager is extremely useful tool which helps you with planning your experiments or preparing printable instructions for others. It allows the user to download biobricks from partsregistry.org, connect them in order to obtain new parts, save resulting bricks as XML files and - what is the most important thing - to get protocol for creating that particular biobrick!


Why is it so special?

BioBrick Manager is the first program that uses biobrick XML representation! We hope that this XML will spread all over the world and make bioinformatic work in synthetic biology easier and more enjoyable.


Wow! I want to try it, but how...?

It's a web application, so you only need a browser and internet connection to use it.

What's more, a lot of our effort went into designing BioBrick Manager to be as user-friendly as possible:

Screenshot with numbers
  1. Widgets for downloading brick by name or uploading local file
  2. Panel for connecting bricks (confirmation window is displayed)
  3. Information about current operation or errors
  4. List of loaded bricks
  5. Information about currently selected brick and its graphical representation
  6. Buttons for saving work
  7. Tabs for switching between information, sequence and XML editor for currently selected brick


Implementation and challenges

Biobrick manager is implemented in Google Web Toolkit and Google App Engine (Java). Those technologies enable easy web application development by "compiling" Java code (client-side) to JavaScript.

Almost everything is done by client - XML operations, drawing bricks, connecting them. Server is used for downloading information from registry or files and saving files.

Source code is available via SVN. Application is hosted using Google infrastructure at http://brickmanager.appspot.com. It is licensed under AGPL.