[
https://issues.apache.org/jira/browse/OFBIZ-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bilgin Ibryam updated OFBIZ-3541:
---------------------------------
Attachment: widgetMacrosInFtlImprove.patch.diff
Bruno,
I made some improvements to your code in order to add autocompleter support in
ftl lookups.
To achieve this, I introduced the initial template file you created and set
there all the default values needed by htmlFormMacroLibrary.ftl. This gives
more possibilities to get the default values in case they are not fixed strings
(like autocompleter url) and keeps the rendering ftl cleaner.
I attached the patch here, in case you (or someone else) wants to check it,
before committing. Next strep would be to replace all the lookup fields (around
70) in ftl files with new lookup macro.
Bilgin
> Using Widgets html form templates in FTL files
> ----------------------------------------------
>
> Key: OFBIZ-3541
> URL: https://issues.apache.org/jira/browse/OFBIZ-3541
> Project: OFBiz
> Issue Type: Improvement
> Reporter: Bruno Busco
> Assignee: Bruno Busco
> Attachments: widgetMacrosInFtl.patch, widgetMacrosInFtl.patch,
> widgetMacrosInFtl.patch, widgetMacrosInFtlImprove.patch.diff
>
>
> The attached patch introduces a way to let developers to use the templates
> defined in htmlMacroFormLibrary.ftl in the FTL files.
> This was discussed in the mailing list and it seems that we all agree that
> having this feature could be a good thing.
> In the patch I used the renderLookupField in the main.ftl file of the catalog
> application. By doing this the two lookups that are included in this ftl are
> now rendered similar to how they are from a form widget.
> This allows the Tomahawk theme to render these lookups in the supposed way
> (with the card icon).
> Doing this I changed the macro in the htmlMacroFormLibrary.ftl to have all
> parameters with a default value so that only the relevant ones must be
> specified in the FTL.
> A new template.ftl file has been added but this only includes the
> htmlMacroFormLibrary.ftl. I do not know if there is a better way to have the
> macro available in the FTL file.
> Please fill free to comment any of the choise I did so that we could then
> commit this and extend to other macros.
> I guess the next one I will address is the renderNextPrev so that all
> paginations will look the same in all forms/FTL screens.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
