Skip to content

roadmap.md

Latest commit

 

History

History
161 lines (123 loc) · 8.49 KB

roadmap.md

File metadata and controls

161 lines (123 loc) · 8.49 KB
Raw

Roadmap - What we reached and where we reach out to

Table of Contents

Disclaimer

This roadmap is a guide for me, to track what’s done, what’s in progress, and what’s still ahead.
It is also a promise to you, to show what I’ve envisioned and where the journey leads.

It’s not a timeline. It’s a direction. Some features may be finished in a day.
Others may wait, while I work on different tools or handle things outside of code.
I work in bursts of high focus, driven by clarity and curiosity, not by pressure.
This roadmap exists to capture technical depth and vision, not deadlines.

If you're looking for a more personal and detailed insight into the process,
how things were built, what challenges came up, and what it all meant, you want to read this:

Devlog

Pre Open Beta

This is a list of features that I absolutely want to finish before releasing the first open beta.
(But because of IRL and time reasons they are not done yet)

  • Add Mainplot label logic & UI & UX
  • Fix subfilter remove and then error on analyse
  • Save colors for labels, also in db
  • Save colors for apps, also in db
  • Enable logging in debug mode & hardcore debug mode in GUI
  • Add logics for logging hardcore debug and normal debug
  • Add logger to the newer modules
  • Hook in the day analyzer in main_view, not the static data for tests
  • Minimize all imports in each module to from xyz import methode, methode2 and so on
  • Check for scattered prints or bad raises per module

Post Open Beta

Here you will see my planed features or mechanics I will start implementing after the program is available to install
on the pc. Most of them are not needed for the core functionality, but in my opinion either helping the use of the tool
or visual optimizations or just refactors, to make the code better (but basically won't change how it works).

  • Bug/Issue report area near settings view, linked to GitHub & filtering duplication entrys
  • Window labeling conditions with dynamic timeframes, like weekday(monday, tuesday etc.), or daytime(morning, evening, etc.)
  • ConfigManager & SettingsManager total refactor to implement my better coding style
  • All modules outsource common methods/functions into utility modules for better encapsulation
  • Create Ourbobors UIX Framework and implement it here, to crack open the monolith GUI Views
  • Create better widgets, also as part for Ourbobors UIX
  • Better Validation logic with Ourbobors UIX
  • Add also weekdays, daytime dynamic search for filters
  • Complete rework of ViperDF, including optimizations and initialization handling
  • We should probably split the ViperDF to a pandas(analysis only) and matplot(figure generation only) module
  • Outsource DayAnalyzer in own module
  • Rework the old ViewController
  • Outsource custom exceptions & rework them to have the same standard here
  • Add some small helper function like "smart_copy" and recheck all return values for protection
  • Add privacy protection area, where keywords or applications can be blacklisted to not be tracked

Potential Feature Ideas

What you see here, is a thought collection of stuff, that I would flag as "nice to have" but not "needed to have",
including some future optimizations, mechanics and more.

  • Instead of saving database querrys with dicts/direct values, maybe add some smarter Databaseobject to forward between modules?
  • Database setup rechecking. Maybe some architecture, like locks are not needed in this project context.
  • Tk Scaling, maybe a nice feature for people who have bad eyes, but need further testeing
  • Add a parenting control, because people will so or so use it like that, why not give them proper toolings? Should include a pin to close app, same pin for changing settings (But still we will add here enforced privacy!)
  • Export of analysis, in form of csv or sql, not as 5 seconds frame, but as combined output from pandas.
  • Backup creation & backup import, maybe even adding here the option to upload anyhwere?
  • Maybe some way to enable the user to create "custom" manual label creation in pystray?
    like i want to have many labels for like "meetings" or "tickets" that all should start ticket#<new label name>
    or meeting#daily_scrum, meeting#customerABC+insurance_car

Milestones Completed

A list of major features, systems, and breakthroughs already implemented.
This isn’t just "done", these are key stepping stones that shaped the core of Viper Tracking.

  • Create a smarter DB exception handling
  • Fix reading in GUI themes from config
  • Prevent double opening of main window
  • Make the app closing with a confirmation
  • Fix window process error, which occurs when there is time between process id grab & process analysis(lag or so)
  • Handle no values on plot and analysis(if not fixed so far)
  • Add duplicate registration cooldown logic to prevent redundant style injection
  • Add final GUI polish and UX handling across all tabs
  • Create new helper widgets like FlexFrame, OverlayFrame, ItemSelectFrame
  • Create singleton FontManager and logic for global font application
  • Add internal re-registration system for style persistence on theme switch
  • Wrap Style.configure() and .map() with warnings and protection logic
  • Fix style override bugs on theme changes
  • Begin creation of StyleManager to preserve styles across themes
  • Patch theme_use, theme_create, and mainloop to fire those events
  • Inject custom ttkbootstrap events: <<PostThemeUse>>, <<PreMainloop>> etc.
  • Apply full code cleanup: PEP8, docstrings (reStructuredText), typing everywhere
  • Add fallback image generation for small UI containers
  • Modularize plot containers: MainPlotFrame, LabelPlotFrame, etc.
  • Add GUI and backend logic for combining and reducing filters (OR/AND logic)
  • Create dynamic timeframe system (DynamicTimeframe) for filters
  • Build GUI for filter creation, nesting, deletion, and reuse
  • Add full filter management: DatabaseFilter, filter_catalogue table
  • Optimize pandas usage for time-based analysis (from 7s → 0.02s on test frame)
  • Enable plot interaction: click, hover, keyboard scroll
  • Add matplotlib-based figure generation for plots (label, app, activity)
  • Create color picker helper for plotting
  • Create label, app, and activity analyzers based on usage data
  • Add first daily analysis feature using pandas
  • Add helper methods and structure for pandas-based analysis (ViperDF)
  • Sync input and window logging with shared timestamps and window IDs
  • Implement label logic with many-to-many DB relation (label ↔ window)
  • Add tkinter variable binding fixes in dynamic inputs
  • Refactor view code to reduce hardcoded logic, unify access paths
  • Refactor conditions.py and integrate into window tracking
  • Recreated the one dimensional Condition system: Created base classes: ConditionList, ObjectCondition, and runtime evaluator
  • Improve system tray robustness (safe exit, detach bugs fixed)
  • Add MultiFunction helper to bind multiple functions to one tray menu entry
  • Add per-attribute type checking and auto-init in user settings
  • Create UserSettingsManager with dynamic JSON persistence
  • Refactor GUI into modular files: gui_views.py, gui_controller.py
  • Improve window title sanitization (e.g. remove emojis)
  • Fix bugs with GUI element duplicates on startup
  • Add system tray updates when label changes
  • Build label tab: creation, deletion, manual toggle, DB persistence
  • Add settings tab to allow theme and resolution configuration
  • Add SQLite support and switch from previous database system(MongoDB)
  • Create first GUI for manual label control from tray menu
  • Start layout of main GUI: notebook/tabs system
  • Add input logger and link input entries to windows
  • Add condition system for automatic label assignment using logic chains
  • Add label catalog table and label-to-window linking table
  • Implement invisible root window in gui_controller to act as global GUI anchor for headless execution
    (used for event loop, style patching, tray context, and later GUI startup)
  • Add basic system tray integration with pystray
  • Add graceful shutdown handling for multi-threaded program termination
  • Add logger class and debug logging infrastructure
  • Prototyping functionality to test base behaviour