Skip to content

Roadmap

Thomas Di Grégorio edited this page Sep 22, 2016 · 2 revisions

Roadmap (draft)

core

  • XML namespace implementation
    • In XML and XHTML documents
      • xmlns resolution is native
    • In HTML5 documents
      • xmlns are not resolved a polyfill is needed
      • HTML link rel="import"
    • Node xmlns <> class lookup
  • Native elements heritage
    • Special classes shim
      • Node
      • Element
      • Document
    • runtime node extension
  • Custom tag
  • Attribute bindings
  • Document import
  • ES6 writen classes
  • E4X implementation

Tests (lack of)

  • Tests
    • QUnit tests
      • Classes presence
      • Node parsing
      • Native parser test
      • Define a lot more tests
    • Unit tests
      • Browsers support, old and recent
        • Blink family
          • Chrome 52
          • Opera
          • electron/NW.js
          • NodeJS
        • Firefox
        • Edge
        • Legacy (IE, old browser) (not a priority), must rely on transpilation
    • Create an automatised test environment

Project

  • Make repository a publishable npm package
  • Create task files for popular task runners: Gulp, ...
  • Create environement for Babel transpilation
  • Autogenerated API jsdoc
  • Namespace server
  • Actionscript to ES6 transpiler
    • Transpile custom as3
    • Transpile Flex 3+ framework classes
      • Make polyfill for flash's internals
  • Cook a GitHub project page presentation of the framework
  • Make a Awesome Jilex (not a priority)

Samples

  • Create sample use cases
    • In the browser
    • In runtimes: electron / NW.js
    • In server side: Nodejs
    • Against or using other frameworks
      • THREE.js
      • Polymer
      • React
      • Angular
      • (add others)
  • Create demo components in libraries for demonstration
    • AppKit
    • Flex 3+4 Components
    • Node representation of json objects with binding + storage