2012-03-22

Feature Hitlist


Based upon initial feedback from a small group of friends here is the list of features we will be working on over the coming months. These are in order of priority

1. World co-ordinate based browsing

This will allow us to display multiple datasets in parallel

2. Mobile device support

Yes, iPads, Droid tablets, phones, etc.

The main issue that will need solving here is the ability to drag via a touchscreen, odds are via a two finger drag.

3. Colour maps

Initially this should include the "standard" imaging maps. Gray, Hotmetal and Spectral.

# gray
# idx r g b
0.0 0.0 0.0 0.0
1.0 1.0 1.0 1.0


# hotmetal
# idx r g b
0.00 0.0 0.0 0.0
0.25 0.5 0.0 0.0
0.50 1.0 0.5 0.0
0.75 1.0 1.0 0.5
1.00 1.0 1.0 1.0


# spectral
# idx r g b
0.00 0.0000 0.0000 0.0000
0.05 0.4667 0.0000 0.5333
0.10 0.5333 0.0000 0.6000
0.15 0.0000 0.0000 0.6667
0.20 0.0000 0.0000 0.8667
0.25 0.0000 0.4667 0.8667
0.30 0.0000 0.6000 0.8667
0.35 0.0000 0.6667 0.6667
0.40 0.0000 0.6667 0.5333
0.45 0.0000 0.6000 0.0000
0.50 0.0000 0.7333 0.0000
0.55 0.0000 0.8667 0.0000
0.60 0.0000 1.0000 0.0000
0.65 0.7333 1.0000 0.0000
0.70 0.9333 0.9333 0.0000
0.75 1.0000 0.8000 0.0000
0.80 1.0000 0.6000 0.0000
0.85 1.0000 0.0000 0.0000
0.90 0.8667 0.0000 0.0000
0.95 0.8000 0.0000 0.0000
1.00 0.8000 0.8000 0.8000

4. Multiple datasets

Ability to display multiple datasets at once that are synced, this is predicated on feature #1.

5. Everything else

From here on in the list of features to add are whole lot less organised, but here are some of the grand schemes

Federation of data

Currently the data that is displayed in TissueStack is on the local server, we need the ability to be able to pull this data from remote TissueStack repositories such that you can overlay atlas data from a remote site over your own data that is stored locally. In effect this means that the source of data in TissueStack should be done via a URI (or URL) rather than via a filename. Local files can still be handled in this via the file:///.... syntax.

Remove the need to pre-cache data tiles

This is a biggie as it will then allow a user to upload their own data (quickly) to a TissueStack web instance. This process is currently lengthy as it involves a manually initiated tile generation routine.

Contributors