Page History

The idea for the prototype is to get experience with AngularJS and to verify if this would be an valid replacement for WebClient

Prototype objectives:

...

• default servoy field should be webcomponents as well

...

NGClient is web based Servoy client technology, which depends on AngularJS framework for all form elements. It futher more depends heavily on the HTML5 specification and upcoming webcomponent specification. Every form element in the NGClient is a webcomponent which can be modified or forms can utilize your own webcomponents.

A webcomponent is an isolated piece of UX which is reusable in forms/pages. Servoy does require a specification file for a webcomponent in order to make it usable in the form designer

...

• 3-way binding includes calling from server to client, which requires websocket support

...

• should be able to read specification files and load beans in pallete
• should be able to map servoydefault form elements back and forward to existing (form/element) persist model (to keep compatibility with existing webclient)
• WYSIWYG (bring formeditor in client?)

...

• default set of webcomponents to be exact match for existing elements in webclient
• include a paging tableview/portal component
• enforce scripting api methods on default servoy elements, like elements.xxx.requestFocus()

...

• serialize solutions inside the war

 . The specification file is therefor Servoy specific and additional to AngularJS.

For details see: 

For details on NGClient deployment and browsers compatibility see NGClient deployment.

From 8.4 on for NGClient we use by default a different absolute positioning system, the anchored positioning is replaced with pure CSS Positioning