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

Jacques Le Roux edited comment on OFBIZ-12002 at 9/21/20, 10:25 AM:
--------------------------------------------------------------------

Also again, I believe we should have OOTB: widget.dev.namedBorder=false. 
Because off the necessary latency (5 sec) which is too long by default and 
can't be much less because you need time to spot and click the link/s you are 
interested in.

Maybe not related (I'm on Windows and it's OK at 
https://github.com/apache/ofbiz-framework/blob/trunk/framework/widget/config/widget.properties)
 but I had to change the encoding of widget.properties to UTF8 


was (Author: jacques.le.roux):
Also again, I believe we should have OOTB: widget.dev.namedBorder=false. 
Because off the necessary latency (5 sec) which is too long by default and 
can't be much less because you need time to spot and click the link/s you are 
interested in.

Maybe not related (I'm on Windows) but I had to change the encoding of 
widget.properties to UTF8 

> Show border and file name for content rendered from ftl
> -------------------------------------------------------
>
>                 Key: OFBIZ-12002
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12002
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: base
>    Affects Versions: Upcoming Branch
>            Reporter: James Yong
>            Assignee: James Yong
>            Priority: Minor
>             Fix For: Upcoming Branch
>
>         Attachments: OFBIZ-12002.patch
>
>
> Currently there are before and after comments in the page source to mark the 
> begin and end of FTL template. Easier for development to display FTL file 
> name and boundary on screen for a short time.
> Only works for FTL files outside of theme folders, and when 
>  -1) print.verbose=true and- widget.dev.namedBorder=true
>  -2) widget.verbose=true-



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to