Hi Bilgin, Sounds interesting I'll be sure to take a look within the next few days.
As coincidences would have it I've also been working on a POC for ajax autocompletion which takes a different approach. I'm not done yet but should hopefully have something this weekend.
The form definition would look like this: <field name="country><autocompleter result-field="countries" result-value-name="geoId" result-description-name="geoName">
<field-event>
<set field="geoName" value="${parameters.country}%"/>
<entity-condition entity-name="Geo" list="countries">
<condition-list>
<condition-expr field-name="geoName" operator="like" from-
field="geoName" ignore-case="true"/>
<condition-expr field-name="geoTypeId" value="COUNTRY"/>
</condition-list>
<order-by field-name="geoName"/>
</entity-condition>
</field-event>
</autcompleter>
</field>
The field-event is then stored in the session and accessed via a
generic request which runs the actions and returns a json result. The
field-event tag allows the same elements as the actions and row-
actions element so you can call scripts or services or whatever so
long as at the end of it the field specified by result-field contains
a list of maps.
Regards Scott HotWax Media http://www.hotwaxmedia.com On 18/11/2009, at 3:17 AM, Bilgin Ibryam wrote:
Hi all, I'd like to propose a way to add ajax support for lookup fields. For that purpose I created a small POC code, where you can test it https://issues.apache.org/jira/browse/OFBIZ-3211The idea is to add ajax autocompleter by default to all lookup fields (generated from form widgets), which gets activated whenever the user types some letters in the lookup field. To retrieve the data is used the same url and screen as the lookup, but with an extra parameter indicating that it is an ajax request.Then on the server side, the only needed change is to add 4 lines of code to each lookup screen which we want to have ajax support. This extension doesn't affect the current usage of lookup button, which still can be used for advanced searches.There are still things to fix and tune up, but the code is stable enough to see it in action. To demonstrate that I added the 4 lines to LookupPartyName lookup screen. So after applying the patch, you can go to any screen using LookupPartyName lookup(this lookup is used in most of the party lookups, like accounting-> invoices, payments) and type some letters in party id fields.I'd be glad to hear your opinion on this. Regards, Bilgin Ibryam
smime.p7s
Description: S/MIME cryptographic signature
