Refactoring

It is time to do some refactoring to get a better structure and improve extensibility. In this issue I want to collect ideas and wishes from you to get the best from this huge step (which will result in JSXC v4.0). It will probably last a couple of month and every line of code will be touched. My goals for this project are the following in descending importance:

1. Make the code testable (fix #191 )
2. Smaller files
3. Improve tab communication (fix #328)
4. Improve security (XSS, …)
5. Easy & durable integration
6. Easy extensibility

To reach the goals I propose the following changes:

• Use TypeScript with modules
• Use more objects (stricter encapsulation and smaller functions)
• Use promises instead of callbacks
• Create new tab communication
• Create public API with versions (e.g. jsxc.api.v1.start)
• Create message pipes for incoming and outgoing messages

Additionally I would like to think about the following points:

• Is Grunt still state of the art? I feel comfortable with it, but maybe there is a better solution which fits our needs. (Gulp, webpack,…)
• The css naming is quiet uncommon and inconsistent. I am inclined to something like jsxc-roster-toggle instead of jsxc_rosterToggle.

I would love to hear your thoughts @LEDfan @MarcelWaldvogel @Zauberstuhl @johangm90 @dimaursu @nitmir @ChristianTacke @dteleguin @skyfox675

[krazyjakee]

I won’t argue, but I will say that I was VERY wrong about coffeescript and that crap can burn in hell.

[mmoqui]

In the way of improving the code: a better decoupling between the UI and the engine by using, for example, the events.