Yes, you are correct. There is a scope of improvement in this feature, we
need to introduce functionality to render all the autocomplete options if user wants to see them. On Wed, Jul 23, 2008 at 11:07 AM, <[hidden email]> wrote: > 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"/> > > > -- Thanks & Regards Mridul Pathak Hotwax Media http://www.hotwaxmedia.com [hidden email] |
It might be even better to just come up with a better example, like an additional form for adding ExampleFeatures to Examples by typing in the name in an auto-complete box or something. -David On Jul 23, 2008, at 12:20 AM, Mridul Pathak wrote: > Yes, you are correct. There is a scope of improvement in this > feature, we > need to introduce functionality to render all the autocomplete > options if > user wants to see them. > > On Wed, Jul 23, 2008 at 11:07 AM, <[hidden email]> wrote: > >> 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"/> >> >> >> > > > -- > Thanks & Regards > Mridul Pathak > Hotwax Media > http://www.hotwaxmedia.com > [hidden email] |
I tryed the InPlaceEditor in the demo server:
https://demo.hotwaxmedia.com/example/control/authview/findExampleAjax It seems to me that when there are more records in the form only the first one has the feature enabled and when clicked many editing rows are shown. Do you confirm? -Bruno 2008/7/23 David E Jones <[hidden email]>: > > It might be even better to just come up with a better example, like an > additional form for adding ExampleFeatures to Examples by typing in the name > in an auto-complete box or something. > > -David > > > > On Jul 23, 2008, at 12:20 AM, Mridul Pathak wrote: > > Yes, you are correct. There is a scope of improvement in this feature, we >> need to introduce functionality to render all the autocomplete options if >> user wants to see them. >> >> On Wed, Jul 23, 2008 at 11:07 AM, <[hidden email]> wrote: >> >> 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"/> >>> >>> >>> >>> >> >> -- >> Thanks & Regards >> Mridul Pathak >> Hotwax Media >> http://www.hotwaxmedia.com >> [hidden email] >> > > |
Bruno,
I see the problem. Thanks for reporting. I'll work on fixing it. Regards Anil Patel On Jul 23, 2008, at 1:11 PM, Bruno Busco wrote: > I tryed the InPlaceEditor in the demo server: > https://demo.hotwaxmedia.com/example/control/authview/findExampleAjax > > It seems to me that when there are more records in the form only the > first > one has the feature enabled and when clicked many editing rows are > shown. > Do you confirm? > > -Bruno > > 2008/7/23 David E Jones <[hidden email]>: > >> >> It might be even better to just come up with a better example, like >> an >> additional form for adding ExampleFeatures to Examples by typing in >> the name >> in an auto-complete box or something. >> >> -David >> >> >> >> On Jul 23, 2008, at 12:20 AM, Mridul Pathak wrote: >> >> Yes, you are correct. There is a scope of improvement in this >> feature, we >>> need to introduce functionality to render all the autocomplete >>> options if >>> user wants to see them. >>> >>> On Wed, Jul 23, 2008 at 11:07 AM, <[hidden email]> wrote: >>> >>> 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"/> >>>> >>>> >>>> >>>> >>> >>> -- >>> Thanks & Regards >>> Mridul Pathak >>> Hotwax Media >>> http://www.hotwaxmedia.com >>> [hidden email] >>> >> >> smime.p7s (3K) Download Attachment |
Free forum by Nabble | Edit this page |