Client side widgets have to interact with the backend, fire events that have to be routed and handled, and fit in the UI. Wisej integrates just about any widget and presents a consistent component/event model to the developer. It takes care of loading, optimizing, initializing, routing, styling, and managing the widgets as server-side components and client-side widgets.
Instead of trying to rebuild charting libraries, treemaps, dashboards, knobs, editors, etc. we use the best component for the job in a fully integrated and consistent framework.
Integrated widgets are much (much!) easier to use. Ever tried to use – really use: handle events, update the state, connect to server code – polymer widgets in a web application? With Wisej it’s as easy as dragging the component to the page, set the properties and attach the events.
The same goes for other browser features: Speech Synthesis, Speech Recognition, and Geolocation are other examples of Wisej integration.
With Wisej all those technologies are integrated as extenders: drop the Speech Recognition component on a page and all the components on the page can now react on speech events from the browser; drop the Geolocation extender and receive events on the server; drop the Speech Synthesis component on a page to add speech capabilities to all the controls on the page.
But what if you can’t find the widget you need? Or what if you need a highly vertical control that simply doesn’t exist in the web world? An example could be a live data mapping widget that shows in real time the performance of an assembly-line machine, or a live ticker that displays data streaming in from a secure server behind a strict company firewall.