project expense

Technical Analysis

Inputing and Removing Data
Description
This feature allows users to input new expenses into the system, where each expense is defined by its amount, category, and description. Users can also remove individual expenses or clear all records at once.

Implementation
Inputting: A form with text fields allows users to input the amount, category, and description of each expense. On submission, the data is inserted into the SQLite database. Removing: Users can select an expense from the table and delete it by clicking a button. The selected record is then removed from the database. Deleting All: A separate button allows users to delete all expenses stored in the database, triggering a confirmation prompt before proceeding.

Design Approach
A simple form layout with text fields for entering expense details. The user interface includes buttons for adding new expenses and deleting selected expenses or all records. A table (using Treeview) displays the list of current expenses.

Click for details

×

Adding Expenses
This video demonstrates how users can input an expense by entering an amount, category, and description. Once submitted, the expense is added to the table in real-time, showcasing how new records appear in the list.

Deleting Expenses
This video shows how users can remove individual expenses by selecting a record and clicking "Delete Selected." It also demonstrates the "Delete All" feature, where a confirmation message appears, requiring the user to confirm before all records are erased.

Error Handling in Expense Entry
This video highlights the built-in error handling for common mistakes. It shows error messages when a user attempts to enter a non-numeric value in the amount field or tries to delete a record without selecting it first.
- Code Snippets
  
  Input Data
  
  This snippet allows users to add new expenses by entering an amount, category, and description.
  
  Delete Data
  
  This snippit allows the users to delete individual records removing them from the database
  
  Delete All
  
  This snippit shows how the user can delete all data in the databse with a confirmation prompt to prevent accidental deleteion of the whole database.
Challanges

Ensuring Data Updates in Real-Time

Challange:

When adding, deleting, expenses, the UI might not update immediately, leading to a stale or outdated display.

Solution:

Use the update_expense_list() function after every database modification to refresh the displayed data.

What I Learnt

Working with SQLite for Data Management

This project was my first experience using SQLite as a database for storing and managing user-inputted data. I learned how to create tables, insert, retrieve, filter, and delete records efficiently. Understanding SQL queries and ensuring data persistence between sessions was a key takeaway. Additionally, I gained insights into handling auto-incrementing IDs, preventing errors when deleting records, and resetting the database properly when needed.

Building a GUI with Tkinter and ttk

Using Tkinter and ttk for GUI development was a completely new experience. I learned how to structure a user-friendly interface, use Treeview tables to display dynamic data, and implement interactive elements like buttons, input fields, and message boxes. Styling elements and ensuring proper layout alignment across different window sizes were also valuable learning points.

Error Handling and User Experience Enhancements

One of the major lessons from this project was implementing proper error handling. I had to ensure users received appropriate feedback when they entered incorrect data (e.g., non-numeric values in the amount field) or attempted invalid actions (like deleting a record without selecting one). Adding confirmation dialogs before critical actions, such as deleting all expenses, improved the user experience and prevented accidental data loss.

Retrospective

Challenges and Future Improvements

Looking back, one of the biggest challenges was ensuring that the expense list updated in real time whenever a new expense was added or deleted. Initially, changes didn’t reflect instantly, which made the app feel unresponsive. By calling the update_expense_list() function after each database operation, I was able to solve this issue. Another challenge was managing category-based filtering in an efficient way. Initially, searches were case-sensitive, meaning "Food" and "food" were treated differently. Implementing case-insensitive filtering improved usability.

Input Data

Delete Data

Delete All

Total Spend Calculation

Get and Display the Date

Data Persistence