[jira] [Commented] (OFBIZ-11809) Access to the current screen from any widget element

["Nicolas Malin (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262837#comment-17262837 ] 

Nicolas Malin commented on OFBIZ-11809:
---------------------------------------

After a new test, I discover a regression for rendering fop screen and xml screen.
The problem came from use the macro renderScreenBegin and renderScreenEnd not to start a screen but for start the rendering in global process.

I solve it with the last patch  [^OFBIZ-11808-OFBIZ-11809.patch]  with dedicate two new macro renderBegin and renderEnd for indicate to start or end  a page rendering and keep renderScreenBegin and renderScreenEnd.
This avoid any confusion with the xml screen definition and the 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)