I tested out multiselect, and while I didn't bother with the query end of things, knowing the return value is an array is enough to know what I'll need to do to accomodate.
Objective: Create an Amazon/SharePoint style user experience with filtering on the side (desktop), and adapt to slideout for mobile. Design pending.
Converting from Select to Multi-Select on the surface is fairly straight forward. Bulk of the time will be spend ironing out and adapting the queries to accept multiple values. We can already detect value changes and show results accordingly. We can a "clear" X button/icon to reset a single field. Estimated 5-7 hours for functionality adjustments and creation of range selection and counts (like SharePoint).
Adjust layout to have filters on side and map results on the other. Desktop won't take too much time, but fabricating a completely new mobile version would take some to perfect. I'm thinking 3-5 hours for that end of things.
Ryan R.
I tested out multiselect, and while I didn't bother with the query end of things, knowing the return value is an array is enough to know what I'll need to do to accomodate.
https://dioceseofvenice.diocesanweb.org/find-a-parish/
Objective: Create an Amazon/SharePoint style user experience with filtering on the side (desktop), and adapt to slideout for mobile. Design pending.
Converting from Select to Multi-Select on the surface is fairly straight forward. Bulk of the time will be spend ironing out and adapting the queries to accept multiple values. We can already detect value changes and show results accordingly. We can a "clear" X button/icon to reset a single field. Estimated 5-7 hours for functionality adjustments and creation of range selection and counts (like SharePoint).
Adjust layout to have filters on side and map results on the other. Desktop won't take too much time, but fabricating a completely new mobile version would take some to perfect. I'm thinking 3-5 hours for that end of things.
Total, 8-12 hours.