Great! Thanks! ;-)
2008/6/23 Adrian Crum <[EMAIL PROTECTED]>:
> Done. Rev 670705.
>
> No additional screen widget code is needed to implement the Find screen
> search results default behavior.
>
> -Adrian
>
>
> Adrian Crum wrote:
>
>> On second thought, it would be better to put it in the FindServices.java
>> file.
>>
>> -Adrian
>>
>> Adrian Crum wrote:
>>
>>> Will do!
>>>
>>> David E Jones wrote:
>>>
>>>>
>>>> Yeah, good point. I guess in that case the ScreenRenderer class is
>>>> probably the best place to put it.
>>>>
>>>> This would be the default value for "noConditionFind", and of course if
>>>> anything specifies it manually then it will override the setting initially
>>>> in the context.
>>>>
>>>> -David
>>>>
>>>>
>>>> On Jun 23, 2008, at 12:10 PM, Adrian Crum wrote:
>>>>
>>>> I thought of that too. Problem is, the decorator is called after the
>>>>> field value is needed.
>>>>>
>>>>> I'll keep scratching my head...
>>>>>
>>>>> -Adrian
>>>>>
>>>>> David E Jones wrote:
>>>>>
>>>>>> Is there anywhere in a decorator or something where we could put this?
>>>>>> Perhaps even right into the ScreenRenderer class where it prepares the
>>>>>> context. Especially if it is coming from a properties file in the widget
>>>>>> component we might as well make it official/automatic/etc.
>>>>>> -David
>>>>>> On Jun 23, 2008, at 11:22 AM, Adrian Crum wrote:
>>>>>>
>>>>>>> This has been implemented in rev 670676.
>>>>>>>
>>>>>>> Basically, all Find screens need to have this line:
>>>>>>>
>>>>>>> <set field="noConditionFind" value="Y"/>
>>>>>>>
>>>>>>> replaced with these lines:
>>>>>>>
>>>>>>> <property-to-field field="initialResultsProp" resource="widget"
>>>>>>> property="widget.findscreen.initial.results"/>
>>>>>>> <set field="noConditionFind" from-field="parameters.noConditionFind"
>>>>>>> default-value="${initialResultsProp}"></set>
>>>>>>>
>>>>>>> -Adrian
>>>>>>>
>>>>>>> Bruno Busco wrote:
>>>>>>>
>>>>>>>> If you guys think that having initially the list empty is better we
>>>>>>>> could
>>>>>>>> make it configurable like proposed by Adrian. But I suggest to have
>>>>>>>> a GLOBAL
>>>>>>>> property to control this so that we have all the UI on an
>>>>>>>> installation
>>>>>>>> consistent.
>>>>>>>>
>>>>>>>
>>>>
>>>>
>>>
>>
