[
https://issues.apache.org/jira/browse/OFBIZ-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264022#comment-17264022
]
Nicolas Malin commented on OFBIZ-11809:
---------------------------------------
Of course no problem Michael.
This issue is a base to simplify and homogenize the screen development and it's
the reason it's a sub task of the OFBIZ-11808.
Alone, the most valuable of this issue isn't clear and will become clearer with
issue OFBIZ-11813 and OFBIZ-11811.
First improvement visible for developer is that the dynamic refresh for a list
(when you sort or paginate) will be directly managed by OFBiz without
informations of the area to refresh. We separated the definition of the area
that a form can update from the screen that include the form.
Typically a facility list will be simplify like this :
{code:xml}
<form name="FindFacility" paginate-target="FacilitySearchResults"
extend="CommonDynamicList"
extend-location="component://common-theme/widget/CommonForms.xml">
<actions>...</actions>
<field name="facilityId" sort-field="true">...
<field name="facilityName" sort-field="true">...
</form>
{code}
and this definition will support all theme specifications and all form
dynamism. But for this we have the constraint to found how the form can know
the screen who include it. This is an example with a form but it can be
extended to other element like menu, links, layered-modal and some other
element that we currently not imagine :)
With Gil we tried to resume all concepts on slides here
https://10031.pages.nereide.fr/slides/yolande.html.
Don't hesitate if some you have some doubts, imagine an other solution to do
that or see potential regression that we missed.
> Access to the current screen from any widget element
> ----------------------------------------------------
>
> Key: OFBIZ-11809
> URL: https://issues.apache.org/jira/browse/OFBIZ-11809
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework/widget
> Affects Versions: Trunk
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Major
> Labels: screen, widget
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-11808-OFBIZ-11809.patch,
> OFBIZ-11808-OFBIZ-11809.patch, OFBIZ-11808-OFBIZ-11809.patch
>
>
> During the rendering process, an element have no information on the screen
> that it depend. This not really help to automatism some refresh treatment and
> force the developer to know the screen structure where is the element.
> To solve this situation we implement a new class, ScreenStack that permit at
> every time for an element to identify who it depend. This help to resolve the
> unique Id that the screen take and can be exploit by the theme.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
