"
Team:Warsaw/Software
From 2010.igem.org
| (19 intermediate revisions not shown) | |||
| Line 4: | Line 4: | ||
</script> | </script> | ||
</html> | </html> | ||
| + | |||
| + | |||
| + | |||
| + | {{TemplateTop}} | ||
| + | {{UpperTabs}} | ||
| + | {{LowerTabsTeam}} | ||
| + | <html> | ||
| + | |||
<style type="text/css"> | <style type="text/css"> | ||
| - | + | ||
img.screenshot { | img.screenshot { | ||
| - | margin-left: | + | margin-top: 20px; |
| + | margin-bottom: 5px; | ||
| + | margin-left: -20px; | ||
padding-left: 0px; | padding-left: 0px; | ||
} | } | ||
| - | |||
</style> | </style> | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | <h2> | + | <h2>BioBrick manager </h2> |
| - | + | ||
| - | to download | + | <br/> |
| - | and get protocol for creating the | + | <div class="note">What can I use it for?</div> |
| + | |||
| + | <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 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> | ||
| + | <br/> | ||
| + | |||
| + | <div class="note">Why is it so special?</div> | ||
| + | |||
| + | <p> | ||
| + | BioBrick Manager is the <b>first program that uses biobrick XML representation</b>! We hope that this XML will spread all over the world and make bioinformatic work in synthetic biology easier and more enjoyable. | ||
| + | </p> | ||
| + | <br/> | ||
| + | |||
| + | <div class="note">Wow! I want to try it, but how...?</div> | ||
| + | |||
| + | <p> | ||
| + | It's a web application, so <b>you only need a browser and internet connection</b> to use it. | ||
| + | </p> | ||
| + | <p> | ||
| + | What's more, a lot of our effort went into designing BioBrick Manager to be as <b>user-friendly</b> as possible: | ||
| + | </p> | ||
| - | |||
<img class="screenshot" src="https://static.igem.org/mediawiki/2010/9/92/Instruction.png" alt="Screenshot with numbers" width="944px" /> | <img class="screenshot" src="https://static.igem.org/mediawiki/2010/9/92/Instruction.png" alt="Screenshot with numbers" width="944px" /> | ||
<ol> | <ol> | ||
| Line 38: | Line 62: | ||
<li>Tabs for switching between information, sequence and XML editor for currently selected brick</li> | <li>Tabs for switching between information, sequence and XML editor for currently selected brick</li> | ||
</ol> | </ol> | ||
| - | + | <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. | + | easy web application development by "compiling" Java code (client-side) to JavaScript.</p> |
| - | Almost everything is done by client | + | <p>Almost everything is done by client - XML operations, drawing bricks, connecting them. Server is |
| - | 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 < | + | 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
BioBrick manager
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!
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.
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:
- Widgets for downloading brick by name or uploading local file
- Panel for connecting bricks (confirmation window is displayed)
- Information about current operation or errors
- List of loaded bricks
- Information about currently selected brick and its graphical representation
- Buttons for saving work
- Tabs for switching between information, sequence and XML editor for currently selected brick
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.
