My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
Roadmap  
Feature roadmap for future development
Updated Aug 17, 2011 by janne.la...@gmail.com
  • Show more sample metadata, for example depth and location
    • Current sample .fasta files do not contain this data, so there is no db field/table for it
  • Selection of specific hits (worst, upwards from specified bitscore...)
  • Multiple graphs (and canvases) on the screen at the same time
    • Propably requires large amount of refactoring on JavaScript side, as things are not encapsulated properly
  • Graph-search for the best connections between two nodes
    • Metrics could be length, bitscores
    • Department propably has some ongoing research about the subject, check that out
    • Should not be done on database/webserver, or at least care must be taken that such operations do not hoard resources.
    • Doing operation client-side is also problematic, amount of data sent would be large
  • Connections
    • Show information about multiple connections between nodes
    • Show more connection data, such as match start- and endpoint
      • Necessary data is already in the database, but is not added to JSONs. Modifications to graph_JSON should be simple, bigger problem is visualization of the data without making the screen too crowded.
  • Make more efficient undo, current implementation is a quick hack
    • Current version saves the entire graph on each undo level, operation based undo would be more efficient
  • Make graphical indicator to show which nodes have not been opened yet
    • On complex graphs it is not obvious which nodes have not been opened
    • Should be easily noticeable without interfering with tag visualization
  • Replacing PostgreSQL with something else.
    • Modify BulkInserter to handle the new database system OR use the generic django code (not recommended, it would be unacceptably slow)
      • Use the new database system's backup/bulk importing feature similar to Postgres' COPY FROM
      • Change the primary key assignment logic from Postgres's sequences
    • Change the run-psql script to use the new database system.
    • Change all the PostgreSQL-specific inline SQL in the scripts.
  • Adding test data for qunit tests
    • A method for adding this data is already available in file 'add_and_remove_test_data', but the data it creates is probably not sufficient for extensive testing.
    • Currently qunit tests use data that may change when new data is inserted to the database.

Known bugs

  • Using refresh function (or function that calls refresh()) after centering graph causes the graph to flip around a bit
    • Modify the library centering function onClick or create new better function for it
  • Making a query with multiple parameters(e.g. read and dbentry), the side menu is not shown right
  • If graph right-click menu is closed by clicking elsewhere, next click does not register correctly
  • The graph menu opens when clicking on the dropdownmenus in settings

Other notes

Powered by Google Project Hosting