Requires issue #12 to be complete

Examples

• "winter's orbit" becomes "Winter'S Orbit" when it should "Winter's Orbit".
• Words like "a", "to", "the", etc. are being capitalised when they shouldn't be.

The solution is probably just to define a custom book_title() function

i.e. RESERVED, OUT, AVAILABLE, etc.

i.e. reserved, out, available w/ color coding.

Also add this to option menu in search window? tbd

Appears to be an issue with the frame not always having the same name, I ideally need to find a way to name it; an alternative solution may be to access it as the frame variable of the scrolled text object which does have a name.

This task falls into three sections, which are:

1. Backend implementation in bookReturn.py and bookCheckout.py
2. GUI implementation in menu.py
3. Cleanup and bug fixing

I haven't yet found the root of the problem, and basic inspection seems to indicate that function itself should work fine; related functions also work fine.

i.e. click on an item to select it.

Not yet rigorously bug-tested.

When a new item is added to the selection, or when switching to and from the other viewport options, the selected element is not coloured correctly.

The expected behaviour is that, when the IO window has finished loading, it will check if the global variable specific_selection is not None, and if so will generate the appropriate event to trigger the callback function select_specific_book.

This could be achieved either in render_io_view or update_selection_view, but I'm concerned that placing the relevant command in render_io_view could fail if it occurred before the specific UI component in question was generated by update_selection_view, given that these callbacks are both triggered by events.

• Title
  • A-Z or Z-A
• Author
  • Alphabetic by first name or alphabetic by last name
• Genre
  • A-Z or Z-A

To be implemented in return-handler

Perhaps needs some change involving generating and binding a custom event, though I feel like there should be something more standard in tkinter to do the same thing.

Fix it, dude.

Something like:

graph TD
    frame --> ml(main label) & sl(minor label)
    ml --> name & author
    sl --> id & genre & pp(purchase price) & pd(purchase date)

Probably an issue with the frame containing selection entries not being always named !frame.

This problem has appeared before, in that case it was solved by iterating over the children of the viewport, and finding the one with the appropriate children — in this case that child would be selection_box.

Partially complete; the remaining steps are:

1. Resolve bugs on the backend
2. Properly implement and test the GUI components

Requires #18 to be completed.

• Suggesting new purchases based on how old certain copies of books are

• Suggesting new purchases based on popularity (as per spec)

• Suggesting new purchases based on underrepresented genres/authors

• Providing UI for selecting how the budget breaks down

• Providing UI for ignoring certain parts of the suggestion calculation