wjrasmussen
11-05-2012, 11:00 PM
There is a situation which feels like a design pattern would be a good fit.
The application will have 40 or more different forms that users will fill out each with some shared fields and with other unique fields.
There are going to be two other major divs for form processing purposes: organization, {donor,vendor}
The organization div will have 3 buttons:
one for populating the form with the organization's license number and contact information.
one for populating the form with the organization's license number but using the accounting firms contact information.
one for populating the form with the organization's license number but using a lawyers contact information.
The donor or vendor div will also have a populating button which will grab various license numbers and fields and put them into the form.
So with 40+ forms with such similar requirements, this seems like a great place for a pattern. Also, thinking in terms of minimizing the amount of work when changes occur in the future. Any recommendations on this?
The application will have 40 or more different forms that users will fill out each with some shared fields and with other unique fields.
There are going to be two other major divs for form processing purposes: organization, {donor,vendor}
The organization div will have 3 buttons:
one for populating the form with the organization's license number and contact information.
one for populating the form with the organization's license number but using the accounting firms contact information.
one for populating the form with the organization's license number but using a lawyers contact information.
The donor or vendor div will also have a populating button which will grab various license numbers and fields and put them into the form.
So with 40+ forms with such similar requirements, this seems like a great place for a pattern. Also, thinking in terms of minimizing the amount of work when changes occur in the future. Any recommendations on this?