Django has several generations of quite different clever mechanisms to make creating HTML forms "easier". Yes, making them might be easier, but maintaining this opinionated stuff is a nightmare without adequately educating yourself how the architecture works. This will take time: do not hurry. -
WARNING: when reading the Django documentation on Forms (unbound and bound) and ModelForms, do not get diverted into looking at Formsets or ModelFormsets. We do not use any formsets in troggle - of any kind. +
WARNING: when reading the Django documentation on Forms (unbound and bound) and ModelForms, do not get diverted into looking at Formsets or ModelFormsets. We do not use any formsets in troggle - of any kind[*].
Hah, that was a nasty shock wasn't it? OK, most of that stuff is not the stuff which manages the data entry form. Concentrate on just the bits between the <form> ....</form> tags. -
It might help you at this point to remind yourself how an ordinary webapge works, without a form. So look at a logbook entry which just displays the data and the corresponding template logbookentry.html... OK, not such a good idea: that is quite complicated. See For loop below. +
It might help you at this point to remind yourself how an ordinary webpage works, without a form. So look at a logbook entry which just displays the data and the corresponding template logbookentry.html... OK, not such a good idea: that is quite complicated. See For loop below.
<form> ....</form> tag works, and how fields and labels and stuff works, and "input" and "textarea" and "submit", and how tag attributes such as "disabled" or "required" work.
@@ -54,7 +54,8 @@ But if you haven't worked with HTML forms before, then you actually have For the relationship between LogBookEntry and PersonLogEntry click on
the Class diagram on the right.
-
+ Yes there is one FormSet, sorry. The joint Cave-and-Entrance thing.