Difference between revisions of "2015 Summer Project Week:CTK for the web and touch devices"
From NAMIC Wiki
Line 23: | Line 23: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
− | * | + | *Polymer seems to be the right solution: |
+ | ** reponsive | ||
+ | *** 1 component for all platforms (phone, tablet, desktop) | ||
+ | ** easy to hook up components to build new components | ||
+ | *** that is polymer's philosophy | ||
+ | ** works everywhere thanks to polyfills | ||
+ | * github organization created | ||
+ | * first components to be implemented: | ||
+ | ** range slider (nicolas) | ||
+ | ** ... | ||
+ | * each component will have to follow polymer's guidelines | ||
</div> | </div> | ||
</div> | </div> |
Revision as of 08:03, 24 June 2015
Home < 2015 Summer Project Week:CTK for the web and touch devicesKey Investigators
- Nicolas Rannou
- Yves Martelli
- Steve Pieper
Project Description
Objective
- Investigate technologies to build a toolkit such as CTK optimized for the web and touch devices.
Approach, Plan
- Working name is ctkjs
- We are looking at using polymer
- Web technologies are still rapidly evolving so picking a good toolset will be tricky.
Progress
- Polymer seems to be the right solution:
- reponsive
- 1 component for all platforms (phone, tablet, desktop)
- easy to hook up components to build new components
- that is polymer's philosophy
- works everywhere thanks to polyfills
- reponsive
- github organization created
- first components to be implemented:
- range slider (nicolas)
- ...
- each component will have to follow polymer's guidelines