Note that there are some explanatory texts on larger screens.

plurals
  1. POAdvice on best possible architecture / solution for following project
    primarykey
    data
    text
    <p>How would you go about architecting following requirement.</p> <ol> <li>A shopping website in which user selects one of the <strong>'customizable'</strong> product. However instead of directly adding a cart, a user can <strong>'CONFIGURE'</strong> the product as per his/her choices. </li> <li>Customizable prducts are very limited and non-dynamic. i.e. Suits, Jacket, Shirt, Pant, Waistcoat. </li> <li>User selects one such product e.g. 'Jacket' and is forwarded to 'configuration' page where there may be large number of configuration settings (e.g. 30-40 settings in case of jacket, ~100 settings in shirt etc.) he may set e.g. style, fabric, color, number of buttons &amp; pockets.</li> <li>Post-configuration, user proceeds to 'measurement' section where again there are very large number of body measurement fields to be stored.</li> <li>Once above is done user proceeds to shopping cart. </li> </ol> <p>Need advice on following:</p> <ol> <li>I am planning to use Wizard like interface. Each step will accept about 10-50 settings usng normal form controls like radiobutton, checkboxes &amp; dropdowns. I should be able disable fortcoming steps till all inputs in current steps are provided. I assume wizard will allow this.</li> <li><strong>The most important question</strong>, how do I go about saving such large number of settings (persistent data) - preferably in some systematic/logical object like list. It need not go to DB till user actually confirms the order. As per this <a href="http://msdn.microsoft.com/en-us/magazine/cc300437.aspx" rel="nofollow"> link </a>'cache' control is best</li> <li>I am new to OOP. but understand that CLASS based approach may be best and is willing to learn the intricacies. However I will appreciate if any experienced people can adivise the best possible approach. </li> </ol> <p>Update 1 : I have experince with webforms (not MVC) </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload