HTML5 SDK Roadmap

Registered by David Barth on 2014-03-04

Discuss the next priorities for the HTML5 SDK roadmap

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
David Barth
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Notes:
HTML5 layout solution
1. not reinvent the wheel, use media queries when possible / if the developer wants
2. give recommendations for layout techniques, frameworks
3. add a simple system for developers who don't want to learn / invest in a complete framework
    or recommend a simple one if appropriate
 * review html5-blocker bugs to see what needs to be landed still
 * review IRC log of this session for feedback

* IDE compliance reporting on JS API usage mapped to declared click app framework
* eval. jshint for use in the qtcreator support module
JS Ubuntu App Platform APIs coming up:
* app lifecyle/state saver
* content hub refactor
* media service
* download manager
* check status of URL dispatcher, and how it can be bound in JS
* U1 app (Aq says we need download manager and content hub for this)
→ <aquarius> I could probably be talked into writing a U1 HTML5 app.

Work items:
* make html5 core app for 14.10
* drive human language translation story for HTML5 apps forward with requirement to support gettext for integration with LP and community: daker, alex abreu
* Update Cordova template to be more Ubuntu-like (e.g replace the Cordova icon, make it do something useful, can be very simple though); create an Ubuntu Cordova template, for when you cordova create <project>, for example

Work items for ubuntu-14.02:
add support for form-factor SDK API in the JS environement on the html5 app: TODO
define possible html5 apps settings (qml or other): TODO
generalize support for other Platform APIs: TODO

Work items for ubuntu-14.03:
[dholbach] set up html5 feedback meeting

Work items for ubuntu-14.05:
[abreu-alexandre] devtools window in QTC (oxide): TODO
[abreu-alexandre] media service JS API: TODO
[abreu-alexandre/dbarth] grid unit: TODO
[zaspire/abreu-alexandre] research code auto-complete in QTC (eval jshint, other similar): TODO
[zaspire/abreu-alexandre] JS framework validation tool in QTC: TODO
[dbarth] organize test layer 2/3 recommendation / documentation: TODO
[knitzsche] document best practices starting with unit tests/cmake when our recommended apporach ready and in html5 app template on developer.ubuntu.com: TODO
[knitzsche] publish test layer 2/3 recos to d.u.c.: TODO
[knitzsche] document best practices on developer.ubuntu.com, provide testing overview: TODO

Work items for ubuntu-14.06:
[abreu-alexandre] switch to oxide for HTML5 apps: TODO
[abreu-alexandre] investigate web components: TODO
[abreu-alexandre] url dispatcher JS API: TODO

(?)

Work Items

Work items for ubuntu-14.02:
add support for form-factor SDK API in the JS environement on the html5 app: TODO
define possible html5 apps settings (qml or other): TODO
generalize support for other Platform APIs: INPROGRESS

Work items for ubuntu-14.03:
[dholbach] set up html5 feedback meeting (4 Apr, 13 UTC): DONE
[abreu-alexandre] content hub refactor: DONE
[dbarth] find a good example HTML5 app (see with popey): TODO

Work items for ubuntu-14.04:
[ya-bo-ng] (w/ alex-abreu) provide media queries examples showing how to support both tablets and phones form factors: TODO
[ya-bo-ng] (w/ alex-abreu) review daker's branch with the new layout mechanism; research alternatives: INPROGRESS
[ya-bo-ng] (w/ alex-abreu) provide simplified system, declarative way, to support tablets & phones: TODO
[abreu-alexandre] runtime API: DONE
[abreu-alexandre] download manager: INPROGRESS
[abreu-alexandre] state saver: INPROGRESS
[knitzsche] publish layout examples: TODO
[abreu-alexandre] update html5 application template (including tests and using cmake): TODO
[dbarth] organize test layer 1 recommendation / documentation: TODO
[knitzsche] publish test layer 1 recos to d.u.c.: TODO

This blueprint contains Public information 
Everyone can see this information.