The FindFacility screen only has a single dropdown box to select a
facility. We have +1000 facilities so need the "standard" way of searching enities. Is there any specific reason not to have a full-blow search form? Jeroen van der Wal |
On Apr 16, 2010, at 9:20 AM, Jeroen van der Wal wrote: > The FindFacility screen only has a single dropdown box to select a > facility. We have +1000 facilities so need the "standard" way of > searching enities. Is there any specific reason not to have a > full-blow search form? > This is an interesting subject. I guess that the main motivation for the drop down vs lookup was that most users use Facility to model a warehouse, and most companies that use OFBiz don't have too many of them. However it is true that Facility could be something else (like an office room) and there are distribution companies with several warehouses. I see here room for an enhancement to the framework to enable more flexible decisions; two options I can see are: a) create a new field widget type that renders as a drop down if the num of records is less than X; if greater than X then renders as lookup b) introduce the concept of a form field widget: the form field, e.g. "facilityId" is defined somewhere and then the field definition is referenced by all form definitions; a custom application could override the central definition of the field (e.g. from drop down to lookup) and all the forms using it will render the new one. Jacopo > Jeroen van der Wal |
Or we could use the standard FindScreenDecorator for this screen too. This
would increase consistency all over the applications. -Bruno 2010/4/16 Jacopo Cappellato <[hidden email]> > > On Apr 16, 2010, at 9:20 AM, Jeroen van der Wal wrote: > > > The FindFacility screen only has a single dropdown box to select a > > facility. We have +1000 facilities so need the "standard" way of > > searching enities. Is there any specific reason not to have a > > full-blow search form? > > > > This is an interesting subject. > I guess that the main motivation for the drop down vs lookup was that most > users use Facility to model a warehouse, and most companies that use OFBiz > don't have too many of them. > However it is true that Facility could be something else (like an office > room) and there are distribution companies with several warehouses. > I see here room for an enhancement to the framework to enable more flexible > decisions; two options I can see are: > a) create a new field widget type that renders as a drop down if the num of > records is less than X; if greater than X then renders as lookup > b) introduce the concept of a form field widget: the form field, e.g. > "facilityId" is defined somewhere and then the field definition is > referenced by all form definitions; a custom application could override the > central definition of the field (e.g. from drop down to lookup) and all the > forms using it will render the new one. > > Jacopo > > > Jeroen van der Wal > > |
In reply to this post by Jeroen van der Wal
Yes consider for instance a education campus with many facilities within
facilities as well. ========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Jacopo Cappellato sent the following on 4/16/2010 12:32 AM: > On Apr 16, 2010, at 9:20 AM, Jeroen van der Wal wrote: > >> The FindFacility screen only has a single dropdown box to select a >> facility. We have +1000 facilities so need the "standard" way of >> searching enities. Is there any specific reason not to have a >> full-blow search form? >> > > This is an interesting subject. > I guess that the main motivation for the drop down vs lookup was that most users use Facility to model a warehouse, and most companies that use OFBiz don't have too many of them. > However it is true that Facility could be something else (like an office room) and there are distribution companies with several warehouses. > I see here room for an enhancement to the framework to enable more flexible decisions; two options I can see are: > a) create a new field widget type that renders as a drop down if the num of records is less than X; if greater than X then renders as lookup > b) introduce the concept of a form field widget: the form field, e.g. "facilityId" is defined somewhere and then the field definition is referenced by all form definitions; a custom application could override the central definition of the field (e.g. from drop down to lookup) and all the forms using it will render the new one. > > Jacopo > >> Jeroen van der Wal > > |
In reply to this post by Jacopo Cappellato-4
This is an issue where I work. We have many facilities and a drop-down list is very inconvenient.
-Adrian --- On Fri, 4/16/10, Jacopo Cappellato <[hidden email]> wrote: > From: Jacopo Cappellato <[hidden email]> > Subject: Re: FindFacitilty screen is limited and inconsistent > To: [hidden email] > Date: Friday, April 16, 2010, 12:32 AM > > On Apr 16, 2010, at 9:20 AM, Jeroen van der Wal wrote: > > > The FindFacility screen only has a single dropdown box > to select a > > facility. We have +1000 facilities so need the > "standard" way of > > searching enities. Is there any specific reason not to > have a > > full-blow search form? > > > > This is an interesting subject. > I guess that the main motivation for the drop down vs > lookup was that most users use Facility to model a > warehouse, and most companies that use OFBiz don't have too > many of them. > However it is true that Facility could be something else > (like an office room) and there are distribution companies > with several warehouses. > I see here room for an enhancement to the framework to > enable more flexible decisions; two options I can see > are: > a) create a new field widget type that renders as a drop > down if the num of records is less than X; if greater than X > then renders as lookup > b) introduce the concept of a form field widget: the form > field, e.g. "facilityId" is defined somewhere and then the > field definition is referenced by all form definitions; a > custom application could override the central definition of > the field (e.g. from drop down to lookup) and all the forms > using it will render the new one. > > Jacopo > > > Jeroen van der Wal > > |
In reply to this post by Bruno Busco
Yes, this is the very first thing to do for sure.
But there will be still several drop down fields around in other screens. Jacopo On Apr 16, 2010, at 9:54 AM, Bruno Busco wrote: > Or we could use the standard FindScreenDecorator for this screen too. This > would increase consistency all over the applications. > > -Bruno > > 2010/4/16 Jacopo Cappellato <[hidden email]> > >> >> On Apr 16, 2010, at 9:20 AM, Jeroen van der Wal wrote: >> >>> The FindFacility screen only has a single dropdown box to select a >>> facility. We have +1000 facilities so need the "standard" way of >>> searching enities. Is there any specific reason not to have a >>> full-blow search form? >>> >> >> This is an interesting subject. >> I guess that the main motivation for the drop down vs lookup was that most >> users use Facility to model a warehouse, and most companies that use OFBiz >> don't have too many of them. >> However it is true that Facility could be something else (like an office >> room) and there are distribution companies with several warehouses. >> I see here room for an enhancement to the framework to enable more flexible >> decisions; two options I can see are: >> a) create a new field widget type that renders as a drop down if the num of >> records is less than X; if greater than X then renders as lookup >> b) introduce the concept of a form field widget: the form field, e.g. >> "facilityId" is defined somewhere and then the field definition is >> referenced by all form definitions; a custom application could override the >> central definition of the field (e.g. from drop down to lookup) and all the >> forms using it will render the new one. >> >> Jacopo >> >>> Jeroen van der Wal >> >> |
In reply to this post by Jeroen van der Wal
if i remember well have more than 5 and you will see your find
screen..... On Fri, 2010-04-16 at 09:20 +0200, Jeroen van der Wal wrote: > The FindFacility screen only has a single dropdown box to select a > facility. We have +1000 facilities so need the "standard" way of > searching enities. Is there any specific reason not to have a > full-blow search form? > > Jeroen van der Wal -- Ofbiz on twitter: http://twitter.com/apache_ofbiz Myself on twitter: http://twitter.com/hansbak Antwebsystems.com: Quality services for competitive rates. |
sorry more than 10....
On Fri, 2010-04-16 at 16:16 +0700, Hans Bakker wrote: > if i remember well have more than 5 and you will see your find > screen..... > > On Fri, 2010-04-16 at 09:20 +0200, Jeroen van der Wal wrote: > > The FindFacility screen only has a single dropdown box to select a > > facility. We have +1000 facilities so need the "standard" way of > > searching enities. Is there any specific reason not to have a > > full-blow search form? > > > > Jeroen van der Wal Ofbiz on twitter: http://twitter.com/apache_ofbiz Myself on twitter: http://twitter.com/hansbak Antwebsystems.com: Quality services for competitive rates. |
In reply to this post by hans_bakker
Oops, you're totally right Hans! My apologies for not fact-checking
this and wasting everybody's time. In our demo system it shows the drop down but in our production system with 1206 facilities it's correct. -- Jeroen van der Wal Stromboli b.v. +31 655 874050 On Fri, Apr 16, 2010 at 11:16 AM, Hans Bakker <[hidden email]> wrote: > if i remember well have more than 5 and you will see your find > screen..... > > On Fri, 2010-04-16 at 09:20 +0200, Jeroen van der Wal wrote: >> The FindFacility screen only has a single dropdown box to select a >> facility. We have +1000 facilities so need the "standard" way of >> searching enities. Is there any specific reason not to have a >> full-blow search form? >> >> Jeroen van der Wal > -- > Ofbiz on twitter: http://twitter.com/apache_ofbiz > Myself on twitter: http://twitter.com/hansbak > Antwebsystems.com: Quality services for competitive rates. > > |
In reply to this post by hans_bakker
.. so I'll add 11 facilities to my demo data ...
Thanks, -Jeroen On Fri, Apr 16, 2010 at 11:20 AM, Hans Bakker <[hidden email]> wrote: > sorry more than 10.... > > > On Fri, 2010-04-16 at 16:16 +0700, Hans Bakker wrote: >> if i remember well have more than 5 and you will see your find >> screen..... >> >> On Fri, 2010-04-16 at 09:20 +0200, Jeroen van der Wal wrote: >> > The FindFacility screen only has a single dropdown box to select a >> > facility. We have +1000 facilities so need the "standard" way of >> > searching enities. Is there any specific reason not to have a >> > full-blow search form? >> > >> > Jeroen van der Wal > -- > Ofbiz on twitter: http://twitter.com/apache_ofbiz > Myself on twitter: http://twitter.com/hansbak > Antwebsystems.com: Quality services for competitive rates. > > |
In reply to this post by hans_bakker
cool, thanks Hans
Jacopo On Apr 16, 2010, at 11:20 AM, Hans Bakker wrote: > sorry more than 10.... > > > On Fri, 2010-04-16 at 16:16 +0700, Hans Bakker wrote: >> if i remember well have more than 5 and you will see your find >> screen..... >> >> On Fri, 2010-04-16 at 09:20 +0200, Jeroen van der Wal wrote: >>> The FindFacility screen only has a single dropdown box to select a >>> facility. We have +1000 facilities so need the "standard" way of >>> searching enities. Is there any specific reason not to have a >>> full-blow search form? >>> >>> Jeroen van der Wal > -- > Ofbiz on twitter: http://twitter.com/apache_ofbiz > Myself on twitter: http://twitter.com/hansbak > Antwebsystems.com: Quality services for competitive rates. > |
Free forum by Nabble | Edit this page |