/web-component-sample

Experiments and samples using web components and Object.observe to replace an MVC framework.

Primary LanguageJavaScript

Sample application using web components

This is a sample application that uses web components and the new Object.observe method. A web-components sample application without the use of complex frameworks (ported from an Angular application called Kolab)

This is a sample application that uses web components and the new Object.observe method. The application is a port of an Angular JS application called Kolab. The original kolab project is built in NodeJS, Socket.io and AngularJS. This version is for experimental and example purposes only. The goal will be to enhance the design paterns around the use of the web-components for use in the original application. As this work continues this repository will be updated with further experiments and examples of web compnent design paterns. The original applciaiton will be placed into a public repository here on git-hub in the near future.

As patterns and best practices are still emerging in this space you may expect the code to change as new experiments are conducted. For a more complete writeup of the expirements and learnings contained herein please refer to the the following blog post. http://malignantgenius.com/2015/01/04/a-first-look-at-web-components-and-object-observe/

How to run the applciation

While the data is static, and this port does not include full functionality, the application can be run from any web server capable of serving staic content. No other backend is required.

Chrome

At the time of upload the code will only run in an up to date version ofthe Chrome web browser. This project contains code that is not in the final W3C recommondation and is therefore not implemented in all browsers. It woudl be possible to provide the needed functionality of the code in other browsers using polyfils, but this has not been tested and the polyfils are not included in the code.

Disclaimer

This code is provided as is. There is no gurantee that futures updates of the specification and/or implementaiton by browswers will not break the functionality.