[28.07.2015] Protocol

General

• We will switch all of our projects to io.js and wait until the merge of NodeJS & IO.js is completed.
• We will use JSDoc in future, at most the following tags: @private (if necessary), afterwards the description of the method/function as well as @param and @returns.
• We strive to find a solution for namespacing and or addressing of packages/instances in the future. (Matrix, )

Build-Tools

• Since we had severe issues with the babel/register hook, we will transpile the build-tools ES6 code and reference the ES5 version for the binary. Since the Mocha API doesn't offer any methods for adding compilers, we also need to use the compiled versions in our unit tests.

ToDo's & Upcoming releases

Assembler

• Namespaces should be integrated
• Issue #14 is accepted/solved. register(MyConstructor) as well as register(MyConstructor, ’MySpecialName’) will be integrated.
• We should also integrate a registerAll({ ‘MyComponent’ : Component }) method for batch registrations.
• The method boot() will be renamed into run()
• In the future, we should check out the DOM Observer API(Performance issues with big client-side apps?)
• As well as the Observer API, a plugin interface could be integrated.

Component

• The Event API should be rewritten, and follow the syntax of Promises. Maybe ES6 generators could be a solution for this.
• setState() should always take an object as the first and only argument. This object will internally be merged with the previous state object.
• We need to integrate DOM Events - The declarative decoator approach could also come in handy here.

Nitpick

• We should move the propType validators as soon as possible into it's new package!
• Issues should also be moved #15 #18

Matrix

• Will be written and published - Infos are coming soon.

Registry

• Will be written and published - Infos are coming soon.
• In the future we should find a way to automatically create von indices (Integrational Layer)

Logger

• We should also move the logger logic out of the component and setup an re-usable package out of it.

Integrational Layer (Reduct)

• Soon we should setup an integrational layer which will merge all packages into one framework.