"
Team:Warsaw/Software
From 2010.igem.org
(Difference between revisions)
(instruction (or at least something close)) |
|||
| Line 17: | Line 17: | ||
<div class="note">Our vision</div> | <div class="note">Our vision</div> | ||
| - | <img src="https://static.igem.org/mediawiki/2010/9/92/Instruction.png" alt="Screenshot with numbers" width=" | + | <img src="https://static.igem.org/mediawiki/2010/9/92/Instruction.png" alt="Screenshot with numbers" width="944px"/> |
<ol> | <ol> | ||
<li>Widgets for downloading brick by name or uploading local file</li> | <li>Widgets for downloading brick by name or uploading local file</li> | ||
Revision as of 18:42, 26 October 2010
Biobrick manager
Biobrick manager is the first program that uses biobrick XML representation. It allows user to download bricks from partsregistry.org, connect them, save resulting bricks as XML files and get protocol for creating the new brick.Our vision
- 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
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 (including XML operations). 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 SOME FREE LICENSE.
