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
Similar naming:
- Bean==WebComponent
- BeanInfo==WebComponent specification
Prototype objectives:
...
- default servoy field should be webcomponents as well
...
- such a zip/jar can contain multiple webcomponents
- all existing servoy form elements should also be such a package
- an webcomponent should have a specification/BeanInfo to make it usable in form designer and properties view
- webcomponents need to include a couple of bootstrap3 example elements
- webcomponents need to include a JIRA alike example inline edit field
- webcomponents need to include a tab panel
...
- 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?)
- absolutelayout is only supported via old form editor
...
- 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()
- include form navigation
...
See research structure for actual cases and progress
new Servoy client technology
Overview
Content Tools
Activity