| | | |
| | | |
| ** How much duplication was necessary ? (e.g. need | | ** How much duplication was necessary ? (e.g. need |
| to describe the models in the database as well as | | to describe the models in the database as well as |
| in code or xml ? / need to describe attributes of | | in code or xml ? / need to describe attributes of |
| models in models and views ?, etc.) ** | | models in models and views ?, etc.) ** |
| | | |
| well.. for "normal" types it's not all that bad.. | | well.. for "normal" types it's not all that bad.. |
| e.g. if you add a new string .. simply add the mig | | e.g. if you add a new string .. simply add the mig |
| ration file .. and modify the _form.html (no idea | | ration file .. and modify the _form.html (no idea |
| if this is supposed to happen automatically ?) .. | | if this is supposed to happen automatically ?) .. |
| and this should be .. it.. | | and this should be .. it.. |
| t | but once you add a relation or even a many-to-many | t | but once you add a relation or even a many-to-many |
| relation ship this is not that easy anymore.. you | | relation ship this is not that easy anymore.. you |
| have to code it .. in 1. _form.html, 2. the contr | | have to code it .. in 1. \_form.html, 2. the cont |
| oller for create AND update 3. list.html 4. show.h | | roller for create AND update 3. list.html 4. show. |
| tml .. and add it in 5. migration file, 6. BOTH mo | | html .. and add it in 5. migration file, 6. BOTH m |
| dels if it is a 1:n relation (belongs_to and has_m | | odels if it is a 1:n relation (belongs_to and has_ |
| any on the other side) | | many on the other side) |
| | | |
| i don't think this is all that great... | | i don't think this is all that great... |
| | | |
| | | |
| ** How much useless code (code which is the same f | | ** How much useless code (code which is the same f |
| or every application, view, model, ...) was requir | | or every application, view, model, ...) was requir |
| ed ** | | ed ** |
