@@ -178,9 +178,11 @@ NOTE: Doing this sort of widget customisation would get tedious
178
178
if we had a much larger, more complex form.
179
179
Check out
180
180
https://django-crispy-forms.readthedocs.org/[django-crispy-forms]
181
- and http://bit.ly/1rR5eyD[django-floppyforms] for some help.
182
181
((("django-crispy-forms")))
183
- ((("django-floppyforms")))
182
+ //CSANAD: crispy forms still seems to be maintained and up-to-date, floppyforms
183
+ // not so much. Some comments on floppyforms' issues say that its
184
+ // functionality is built into Django as of 2020. I'm not sure if it's true for
185
+ // crispyforms as well.
184
186
185
187
186
188
[role="pagebreak-before less_space"]
@@ -535,8 +537,9 @@ the logic change:
535
537
[subs="specialcharacters,quotes"]
536
538
----
537
539
$ *git diff* # review changes in base.html, views.py and its tests
538
- $ *git commit -am "use new form in home_page, simplify tests . NB breaks stuff"*
540
+ $ *git commit -am "use new form in home_page. NB breaks stuff"*
539
541
----
542
+ // CSANAD: we didn't simplify the tests in this step. What's NB?
540
543
541
544
542
545
Let's fix the functional tests.
@@ -613,6 +616,8 @@ $ *grep -r id_new_item src/lists/*
613
616
----
614
617
615
618
Good, there are no references to `id_new_item` left.
619
+ // CSANAD: we could mention *.pyc files under __pycache__ would probably still
620
+ // show up in the results.
616
621
What about `name`/ `item_text`?
617
622
618
623
[subs="specialcharacters,macros"]
@@ -1029,8 +1034,6 @@ or spin up the site manually with `manage.py runserver` if you prefer
1029
1034
(see <<html5_popup_screenshot>>).
1030
1035
1031
1036
1032
- // todo: update screenshot
1033
-
1034
1037
[[html5_popup_screenshot]]
1035
1038
.HTML5 validation says no
1036
1039
image::images/twp2_1401.png["The input with a popup saying 'please fill out this field'"]
0 commit comments