[
https://issues.apache.org/jira/browse/OFBIZ-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264187#comment-17264187 ]
Jacques Le Roux edited comment on OFBIZ-11809 at 1/13/21, 2:36 PM:
-------------------------------------------------------------------
bq. With Gil we tried to resume all concepts on slides here
https://10031.pages.nereide.fr/slides/yolande.html.
Great stuff thanks guys :)
was (Author: jacques.le.roux):
>With Gil we tried to resume all concepts on slides here
https://10031.pages.nereide.fr/slides/yolande.html.
Great stuff thanks guys :)
> 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)
Locked
