Difference between revisions of "2017 Winter Project Week/SimplePowerfulBeautifulMedicalVisualizerWithAMI"
| Line 20: | Line 20: | ||
A collection of web components [3] (via Polymer [4]) will be designed and implemented. | A collection of web components [3] (via Polymer [4]) will be designed and implemented. | ||
| + | ===== Why Polymer? (and not React [5] or Angular [6]) ===== | ||
| + | Because Polymer is meant to '''disappear'''! | ||
| − | '' | + | Polymer adds very little 'sugar' on top of the web '''standards'''. It mostly adds support for some features that are not available '''yet''' on some platforms'. Eventually, 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. | |
| + | |||
| + | - and it is a Google backed project! | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 11:06, 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 steep for new comers. This project aims to provide simple interfaces for AMI [1].
Simple JS interface
A simple Javascript XTK-like [2] API. The key to the XTK success was its simple interface that lets people just dive in without worrying about the details.
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 Polymer is meant to disappear!
Polymer adds very little 'sugar' on top of the web standards. It mostly adds support for some features that are not available yet on some platforms'. Eventually, 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.
- and it is a Google backed project!
| Objective | Approach and Plan | Progress and Next Steps |
|---|---|---|
|
|
|
