Hi Scott,
Yes you are right this was not what I was looking for, and BTW it's true by
default.
I remember now that at r936638 Bilgin has activated by default the option (Enabled lookup descriptions) I was looking for (for an
explanation on lookups on user ML).
It's just that sometimes it does not work just because of client-autocomplete-field, sometimes it does (on the same browser), not
sure why, anyway not a big deal.
I removed it, since it's redundant and useless, at r942667
Thanks
Jacques
Scott Gray wrote:
I'm not sure if this affects what you've committed but client-autocomplete is
not ajax autocomplete, it just tells the browser
whether or not to try and autocomplete with values previously entered.
Regards
Scott
HotWax Media
http://www.hotwaxmedia.com
On 10/05/2010, at 6:39 AM, [email protected] wrote:
Author: jleroux
Date: Sun May 9 18:39:03 2010
New Revision: 942576
URL: http://svn.apache.org/viewvc?rev=942576&view=rev
Log:
Show client-autocomplete-field usage
Modified:
ofbiz/trunk/framework/example/config/ExampleUiLabels.xml
ofbiz/trunk/framework/example/widget/example/FormWidgetExampleForms.xml
Modified: ofbiz/trunk/framework/example/config/ExampleUiLabels.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/framework/example/config/ExampleUiLabels.xml?rev=942576&r1=942575&r2=942576&view=diff
==============================================================================
---
ofbiz/trunk/framework/example/config/ExampleUiLabels.xml (original) +++
ofbiz/trunk/framework/example/config/ExampleUiLabels.xml
Sun May 9 18:39:03 2010 @@ -447,8 +447,8 @@
<value xml:lang="fr">Lookup de type layer (only test)</value>
</property>
<property key="ExampleLookupFields">
- <value xml:lang="en">Examples Lookup Fields (first of type popup, second
layered)</value>
- <value xml:lang="fr">Exemples de champs de recherche (le premier de type
popup, le second de type layer)</value>
+ <value xml:lang="en">Examples Lookup Fields (first of type popup using
also autocomplete, second layered and showing
use of set_values underneath, ie returning not only Id but also another value)</value> +
<value xml:lang="fr">Exemples de
champs de recherche (le premier de type popup utilisant aussi
l'autocompletion, le second de type layer avec usage
sous-jacent de set_values qui permet de traiter non seulement une référence
mais aussi une autre valeur)</value>
</property> <property key="ExampleMainPage"> <value xml:lang="en">Example
Main Page</value>
Modified:
ofbiz/trunk/framework/example/widget/example/FormWidgetExampleForms.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/framework/example/widget/example/FormWidgetExampleForms.xml?rev=942576&r1=942575&r2=942576&view=diff
==============================================================================
---
ofbiz/trunk/framework/example/widget/example/FormWidgetExampleForms.xml
(original) +++
ofbiz/trunk/framework/example/widget/example/FormWidgetExampleForms.xml Sun May
9 18:39:03 2010 @@ -285,7 +285,7 @@ under the
License. <!-- Lookup (in a popup windows, old style) -->
<!-- Using separated labels is not recommended (it's better using
sentences than words for translation) but here we use
only Common labels to avoid dependencies from application to framework --> <field
name="partyIdFrom"
title="${uiLabelMap.CommonPartyID} ${uiLabelMap.CommonFrom}"><!-- we use
partyIdFrom here only to differentiate from the other
partyId field we use below, ie partyIdTo--> - <lookup
target-form-name="LookupPartyExample" presentation="window"/> +
<lookup target-form-name="LookupPartyExample" presentation="window"
client-autocomplete-field="true"/> </field>
<!-- Standard Lookup in a layer (new style)-->
<!-- passes the name in one and the id in another field -->
