[
https://issues.apache.org/jira/browse/OFBIZ-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134126#comment-17134126
]
Jacques Le Roux commented on OFBIZ-11809:
-----------------------------------------
Hi Nicolas,
I have reviewed, applied and succesfully compiled the patch. It looks good to
me and I can see this
<div id="30006f15-a10b-49ce-83c6-d10c148d4768" class="contentarea">
when getting to
https://localhost:8443/catalog/control/login?USERNAME=admin&PASSWORD=ofbiz&JavaScriptEnabled=Y
So I guess it's OK (disclaimer: I did not test the areaId thing)
Just a trivial syntax point :) :
* {{if (! context.containsKey("screenStack")) {}} no space after !
I have still to carefully read all the chapters at OFBIZ-1808...
Thank you Nicolas!
> 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
>
>
> 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)
