Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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:

  • Bring html templating to browser with AngularJS (opposed to Wicket which does html templating at server)
  • Make all form elements beans/webcomponents
    • default servoy field should be webcomponents as well
  • An webcomponent should be an angular directive packaged in a zip living in solution media
    • 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
  • Introduce 3-way binding, which means: element to scope, scope with serverside scope representation (element properties)
    • 3-way binding includes calling from server to client, which requires websocket support
  • Form designer has to be able to work with flow layout
    • 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
  • Have compatibility with existing webclient (except style at form)
    • 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
  • Bind solution JS method at component events (like onAction) at server side to be executed from an browser button click for example
  • Have a war export option
    • serialize solutions inside the war

See research structure for actual cases and progress

 

  • No labels