Author: jonesde
Date: Tue Jul 22 22:37:09 2008
New Revision: 678997
URL: http://svn.apache.org/viewvc?rev=678997&view=rev
Log:
Removed/commented auto-complete for type/status; those are neat and work fine
but make these screens practically unusable unless you know which first
character to type for the option you want, left commented for demo/test purposes
Modified:
ofbiz/trunk/framework/example/widget/example/ExampleForms.xml
Modified: ofbiz/trunk/framework/example/widget/example/ExampleForms.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/framework/example/widget/example/ExampleForms.xml?rev=678997&r1=678996&r2=678997&view=diff
==============================================================================
--- ofbiz/trunk/framework/example/widget/example/ExampleForms.xml (original)
+++ ofbiz/trunk/framework/example/widget/example/ExampleForms.xml Tue Jul 22
22:37:09 2008
@@ -102,7 +102,7 @@
<field use-when="example==null&&exampleId!=null"
name="exampleId" title="${uiLabelMap.ExampleExampleId}"><display
description="${uiLabelMap.CommonCannotBeFound}: [${exampleId}]"
also-hidden="false"/></field>
<field name="exampleTypeId" title="${uiLabelMap.CommonType}"
id-name="exampleTypeId">
<drop-down allow-empty="false">
- <auto-complete/>
+ <!-- this is a neat feature, but not good for the type because
the user would have to know the possible types in order to enter at least the
first letter, so leaving it out by default; just uncomment to enable:
<auto-complete/> -->
<entity-options entity-name="ExampleType"
description="${description}">
<entity-order-by field-name="description"/>
</entity-options>
@@ -146,7 +146,6 @@
<alt-target use-when="example==null" target="createExampleAjax"/>
<field name="statusId" use-when="example==null"
title="${uiLabelMap.CommonStatus}" id-name="statusId">
<drop-down allow-empty="false">
- <auto-complete/>
<entity-options entity-name="StatusItem"
description="${description}">
<entity-constraint name="statusTypeId"
value="EXAMPLE_STATUS"/>
<entity-order-by field-name="sequenceId"/>
