Yep, you can already do it, check out the screens.render line
#if collectionSummary?has_content>
<div class="screenlet-body">
<table width="100%" border="0" cellspacing="5">
<tr>
<td width="50%">
${screens.render("component://ar/widget/opentaps/collections/screens/Collect
ionScreens.xml#collectionWorkArea")}
</td>
<td width="50%">
<#if chartURL?has_content>
<img src="${chartURL}" style="vertical-align:middle;
margin-left:35px"/>
<#else>
No chart Image
</#if>
</td>
</tr>
</table>
</div>
<#else>
${uiLabelMap.PartyNoPartyFoundWithPartyId}:
${parameters.partyId?if_exists}
</#if>
-----Original Message-----
From: Jonathon -- Improov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 04, 2007 1:02 AM
To: user@ofbiz.apache.org
Subject: Re: Any plan to allow field widgets like <drop-down> inside
<screen>?
Skip,
Do you mean it can currently be done already? Didn't know this.
Or you mean it's a good step forward?
Right now, whenever widgets are inadequate, a common practice (maybe the
only feasible one) is to
jump right into FTL and forget about widgets.
(But if you can do all-widget forms and all-ftl forms, they do mix. I
replied to your post about
the "screens as building blocks" thing.)
The lack of widgets (like convenient <drop-down>) in FTL is possibly the
main motivation behind Si
Chen's (opentaps) route with FreeMarker macros. Was mine too, at one time. I
had a library of
macros (sold, privatized, again, sigh).
Jonathon
[EMAIL PROTECTED] wrote:
> Widgets in FTL is the only way currently to get some things done if you
want
> to use widgets.
>
> Skip
>
> -----Original Message-----
> From: Jonathon -- Improov [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 03, 2007 5:36 PM
> To: user@ofbiz.apache.org
> Subject: Re: Any plan to allow field widgets like <drop-down> inside
> <screen>?
>
>
> Actually, this isn't going backwards. It's going forward.
>
> Some screens are best done in ftl. This was discussed countless times
> before.
>
> In getting ftl screens to use field widgets, we reuse more of OFBiz's
> widgets in more places. This
> will bring us closer to using more of widgets.
>
> Jonathon
>
> BJ Freeman wrote:
>> seems your going backwards.
>> remove the ftl and use screen widgets that include formwidgets.
>> add a class (style) and use the css for aligning tables.
>>
>> Jonathon -- Improov sent the following on 12/2/2007 8:48 PM:
>>> The problem I'm facing now is that form widgets always have the start
>>> and end wrappers (<table cellspacing...> and </table). It is not
>>> possible to mix fields from one form into another form done in ftl.
>>>
>>> Attributes skip-start and skip-end only remove the <form> wrapper.
>>>
>>> Getting form widgets to say skip-table could solve this problem, though
>>> it's not intuitive to use form widgets as field widgets. Better to use
>>> field widgets in screen widgets instead. However, this approach could be
>>> a quick interim fix.
>>>
>>> Another problem is the colspan for <td>. Maybe we can make that
variable.
>>>
>>> Field widgets like <drop-down> are fantastic. It's a pity we can't use
>>> them inside of creative displays written in ftl.
>>>
>>> Si Chen did some FreeMarker macros for these, I believe. But if we're
>>> gonna strongly advocate widget usage, I think we need to fill that void
>>> in screen widgets. Going the FreeMarker macros route would basically
>>> rewrite much of what is already provided by field widgets.
>>>
>>> Maybe have a generic "group of fields" widget via <fields>?
>>>
>>> Jonathon
>>>
>>>
>>>
>>
>
>
>
