comments

core/models/caves.py

@@ -25,6 +25,8 @@ Gcave_count = None
 
 todo = """
 - Why do we have CaveAndEntrance objects ? These do not need to be explcit for a many:many relationship these days
+now only used to create a <form> for    entranceletter 
+TO DO move entranceletter to Entrance
   
 - Restore constraint:   unique_together = (("area", "kataster_number"), ("area", "unofficial_number"))
   or replace by a unique 'slug' field, better.
@@ -32,11 +34,11 @@ todo = """
 
 
 class CaveAndEntrance(models.Model):
-    """This class is ONLY used to create a FormSet for editing the cave and all its
-    entrances in one form.
+    """This class is ONLY used to create a FormSet for editing the entranceletter.
     CASCADE means that if the cave or the entrance is deleted, then this CaveAndEntrance 
     is deleted too
     NOT NEEDED anymore if we insist that cave:entrances have 1:n multiplicity.
+    TO DO move entranceletter to Entrance
     """
     cave = models.ForeignKey("Cave", on_delete=models.CASCADE)
     entrance = models.ForeignKey("Entrance", on_delete=models.CASCADE)

core/views/prospect.py

@@ -14,6 +14,8 @@ from troggle.core.views.caves import caveKey
 
 """ Generates the prospecting guide document.
 
+ALL DISABLED SINCE 2017
+
 Also produces the overlay of points on top of a prospecting_image map - to be deleted.
 Not working with recent PIL aka Pillow image package - removed.
 """