"
Team:Warsaw/Software
From 2010.igem.org
(Difference between revisions)
m (AGPL) |
|||
| Line 29: | Line 29: | ||
Biobrick manager is the first program that uses biobrick XML representation. It allows user | 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 | to download bricks from partsregistry.org, connect them, save resulting bricks as XML files | ||
| - | and get protocol for creating the new brick. | + | and get protocol for creating the new brick. It's a web application, so you only need a browser |
| + | and internet connection to use it. | ||
<div class="note">Our vision</div> | <div class="note">Our vision</div> | ||
| Line 46: | Line 47: | ||
<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 <a href=http://code.google.com/intl/en-EN/webtoolkit/>Google Web Toolkit</a> and | ||
<a href="http://code.google.com/intl/en-EN/appengine/">Google App Engine (Java)</a>. Those technologies enable | <a href="http://code.google.com/intl/en-EN/appengine/">Google App Engine (Java)</a>. 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>Source code is available <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 | ||
Revision as of 21:56, 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. It's a web application, so you only need a browser and internet connection to use it.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 - 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.
