added html for subbooks, made up/down buttons that work too. Also put back reference from subbook to parent book, via ORM data - need to investigate more, but it all works

README

@@ -25,9 +25,9 @@ python3 main.py
 
 
 ### TODO: 
-- ORM:
-	- saving a book with the ORM is probably the last oddity... probably time to try it (in a sense, the book edit page is the only time we change things, maybe we mess with that book-query as its too slow, and for book edit, if we don't allow editing items like author/publisher, then may only need to set the objects we want to change... I'm sort of curious can you save a book table based on id, without saging its author table, seems that should be okay, but how do I save both, just create 2 objects and do it, but what if the ORM has auto-connected bunches of stuff, how do I update the connected stuff.... MAYBE, I need to get say loan or something first, then try all this? (make a pop-up for stuff like loans, but what about series or sub-book editing????)
-	- have no html for sub_book
+	- ORM: okay, could have child and parent references in book, would that remove need for hand-sql of subs?
+		* see code for subbooks_for_book ('parent')... 
+		* if so, book.html has books (from schema.dump(book), could just be book with parent/child?)
 	- need to save a book
 	- need to create all classes (green + button)
 	- need to delete all classes (and watch for referential integrity)