[
https://issues.apache.org/jira/browse/OFBIZ-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263480#comment-17263480
]
ASF subversion and git services commented on OFBIZ-11809:
---------------------------------------------------------
Commit e0a840a0c4928080f7a3e3bdf3a42e327483939c in ofbiz-framework's branch
refs/heads/trunk from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=e0a840a ]
Implemented: Access to the current screen from any widget element
(OFBIZ-11809)
During the rendering process, an element have no information about the screen
which is dependent from. This not really help to automate 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 allow
anytime for any element to identify its direct dependency. This help to resolve
the unique Id that the screen take and can be used by the theme.
At any time a developer can retrieve the screen reference with uel function
screen:id(screenStack)
example:
<container id="${screen:id(screenStack)}">
The object screenStack is always present during a rendering process.
> 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
> Priority: Major
> Labels: screen, widget
> 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)