Difference between revisions of "2017 Winter Project Week/SimplePowerfulBeautifulMedicalVisualizerWithAMI"
| Line 11: | Line 11: | ||
==Project Description== | ==Project Description== | ||
| + | Many tools and libraries exist to build powerful '''web medical visualizers''' but the learning curve can be to steep for new comers. | ||
| + | This project aims to provide simple interface for AMI [1], at different levels. | ||
| + | |||
| + | ==== Simple JS interface ==== | ||
| + | A simple Javascript XTK-like [2] API | ||
| + | |||
| + | ==== Web components ==== | ||
| + | A collection of web components [3] (via Polymer [4]) will be designed and implemented. | ||
| + | |||
| + | Why Polymer? (and not React [5] or Angular [6]) | ||
| + | Because it is meant to '''disappear'''! Polymer just add very little 'sugar' on top of the web '''standards'''. It mostly adds support for some features that are not available on simple platforms '''yet'''. Ultimatly all browser vendors will implement all the standards and the Polymer library that aims to poly-fill all the gaps will disappear. Accessibility is very important too: one can use web components for its app no matter which framework is used. Using React/Angular elements from another framework is not necessarily possible. | ||
| + | |||
{| class="wikitable" | {| class="wikitable" | ||
! style="text-align: left; width:27%" | Objective | ! style="text-align: left; width:27%" | Objective | ||
| Line 18: | Line 30: | ||
| | | | ||
<!-- Objective bullet points --> | <!-- Objective bullet points --> | ||
| − | * | + | * Design/Implement XTK like API for AMI |
| + | * Define/Design/Implement AMI-based web components for medical imaging | ||
| + | * Implement Lesson 10 and 14 from XTK with new JS API | ||
| + | * Build Slicer/Slicedrop/Cornerstone like viewer leveraging web components | ||
| | | | ||
<!-- Approach and Plan bullet points --> | <!-- Approach and Plan bullet points --> | ||
| − | * | + | * Write helpers functions in AMI to hide low-level JS implementation details |
| + | * Mockup basic quad-view to define most web components | ||
| + | * Implement web components | ||
| | | | ||
<!-- Progress and Next steps bullet points (fill out at the end of project week) --> | <!-- Progress and Next steps bullet points (fill out at the end of project week) --> | ||
Revision as of 11:00, 9 January 2017
Home < 2017 Winter Project Week < SimplePowerfulBeautifulMedicalVisualizerWithAMI
Key Investigators
- Jorge Luis Bernal Rusiel, Boston Children's Hospital
- Nicolas Rannou, Eunate Technology S.L.
- Rudolph Pienaar, Boston Children's Hospital
Project Description
Many tools and libraries exist to build powerful web medical visualizers but the learning curve can be to steep for new comers. This project aims to provide simple interface for AMI [1], at different levels.
Simple JS interface
A simple Javascript XTK-like [2] API
Web components
A collection of web components [3] (via Polymer [4]) will be designed and implemented.
Why Polymer? (and not React [5] or Angular [6]) Because it is meant to disappear! Polymer just add very little 'sugar' on top of the web standards. It mostly adds support for some features that are not available on simple platforms yet. Ultimatly all browser vendors will implement all the standards and the Polymer library that aims to poly-fill all the gaps will disappear. Accessibility is very important too: one can use web components for its app no matter which framework is used. Using React/Angular elements from another framework is not necessarily possible.
| Objective | Approach and Plan | Progress and Next Steps |
|---|---|---|
|
|
|
