OFBIZ-11756 vue js renderer #169

…-11757) It's now possible to use ${ for area-id

1. add "use-when" management in the xsd and in the modelForm.UpdateArea, 2. add in modelForm a static method to return a valid list of updateArea from a list of updateArea and context 3. duplicate all methods returning a list of updateArea, by same name but with context as parameters which return only valid updateArea list (ex: in formFieldBuilder for getOnClickUpdateAreas and getOnChangeUpdateAreas)

… a updateArea list in json format (OFBIZ-11759)

…a (OFBIZ-11760) In link, added in url-mode and in on-field-event-update-area added in event-type. Add post,put, delete (get is the default)

…ame as for on-event-update-area (OFBIZ-11761) Not necessary to modify model*.java because it's manage by update-area object in the two case

* add attribute watcher-name for tag container * add in link-type enum set-area, refresh-area and set-watcher, refresh-watcher * add in xxx-event-update-area, in event-type enum set-area, refresh-area and set-watcher, refresh-watcher Concept is: 1. container is the main piece of dynamics screen (update a part of screen on event), a new attribute is added watcher-name, and existing one auto-update-target is using as target 2. There are two/four new "action" usable by link - hyperlink * set-area (and refresh-area) * set-watcher (and refresh-watcher) 3. set-area is used to update a containerId, and, most of the time, uses only for included containerId set-watcher put some "parameters" in a watcher-name 4. when the content of a whatcher-name change, all containerId which watch it, use their auto-update-target as target and watcher-name content as parameters to update the container content. 5. refresh-area is similar with set-area but target used will be the auto-update-target define at the container level and, if a watcher-name is define for this container, it's content will be used as parameters (for solving {} in target or as parameters if no {} in target.

…-11764) it's a click event, when click the form is submitted

…type (OFBIZ-11765) it's a click event, when click the field is update, it's useful in lookup form to update field from which the lookup has been call No modification in renderer in this commit

…vent-type (OFBIZ-11766) it's a click event, when click all the screenlet with the areaId are collapse No modification in renderer in this commit area-target can be used to detail action to do toggle, collapse or expand

…s event-type (OFBIZ-11767) it's a click event, when click one or all open modal area closed. it's use for lookup and for modal created with link with layered-modal No modification in renderer in this commit

this tag is used to call vuejs specifics component in the standard vuejs application (the vuejs renderer). vuejs specifics components are similar to ftl files in html standard renderer.

(OFBIZ-11769) two properties files, to be able to use a logical name not a "path"

…FBIZ-11770) When a watcherName is associated to a Portal - Portlet, it's used to created a container (with this watcher) "around" the portlet, and so be able to update it with a set-area, refresh-area, set-watcher, refresh-watcher

…ent-update-area (field and form). auto-parameters-portlet add for parameters in parameters-map: - portalPageId - portalPortletId - portletSeqId - currentAreaId auto-parameters-portlet is used by showPortlet to be able to renderer only one portlet, because often, it's necessary to have the 4 parameters for a future other update (ex: button back)

plugins)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OFBIZ-11756 vue js renderer #169

OFBIZ-11756 vue js renderer #169

Commits on Aug 24, 2021

OFBIZ-11756 vue js renderer #169

Are you sure you want to change the base?

OFBIZ-11756 vue js renderer #169

Commits on Aug 24, 2021