Since a Treeview should work with minimal modification, I think I’ll start there. Likewise, I can probably do all or most of the same things manually with a custom row-column layout. I can also supply the most unique primary key of the record collection as the iid, which has some appeal for unambiguously selecting records. Treeview widgets have the benefit of being able to display hierarchies, which could be convenient for grouping by foreign keys. Tk doesn’t come bundled with an HTML-like element, so that would involve some creativity.Manually create a tabular layout, using labels as table cells.I can browse these records in one of two ways: So, considering my vehicle database, my first “view” of the data ought to be simple: every make, model, and trim that I’ve entered so far. Since I’ve done so much with the GUI lately, this would be a good time to take care of that. I’ve got all the basic parts to put data into the database, but no means of getting it out in a useful way. ![]() Moving on from that subject, and revisiting my new to-do list, I’ve yet to implement a very obvious, if not entirely critical part of a database-backed application: viewing records. ![]() As these included modules and APIs that were new to me, the efforts made were more for learning, and less for development. Though I haven’t fully implemented the configuration settings that I worked on last time, I’ve given it a place to exist alongside the other parts of the application. A lot of items were too general to leverage in-code comments, and I kind of like having a single file of known issues that can be committed with the rest of the code package. Since my last post, I’ve collected most of my notes and comments into a “TODO” file.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |