Skip to content

kmann3/EtherpunksMoneyRegister

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

439 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

EtherpunksMoneyRegister

General

This is a program I plan on using personally. It's more of an ongoing project using whatever framework I'm in the mood for.

Versions

v1-v-whatever are simply varying things I'm toying with. They aren't incremental. It's just "oh, that sounds neat, I want to check that out".

  • ✅ v15 : Swift/SwiftUI/SwiftData
  • v13 : Swift/SwiftUI/SwiftData
  • v14 : Swift/SwiftUI/SwiftData
  • v12 : Swift/SwiftUI/SwiftData
  • v11 : C# / WPF
  • v10 : C# / WPF
  • v9 : C# / WPF
  • v8 : ??? I don't remember
  • v7 : C# / Blazor
  • v6 : C# / Blazor
  • v5 : C# / Blazor
  • Deleted previous versions because I didn't think I'd care.
  • v4 : C# / WinUI
  • v3 : C# / WPF
  • v2 : C# / WinForms
  • v1 : C# / WinForms

Currently on v15 - which is Apple focused. MacOS, first. Followed by iOS (mostly iPhone and then iPad), and then by apple Watch.

Apple focused because I bring my Macbook when I travel instead of a Windows or Linux laptop.

Rough order:

  • 🟠 Read views
    • 🟢 Account
    • 🟢 Tag
    • 🟢 Transaction
    • 🟢 Recurring Group
    • 🟢 Recurring Transaction
    • 🟢 Files
    • 🔴 Search
    • 🔴 Reports
      • 🔴 Tax related
  • 🟠 Edit Views
    • 🟠 Account
    • 🔴 Tag
    • 🔴 Recurring Group
    • 🔴 Recurring Transaction
    • 🔴 Transaction
    • 🔴 Files
  • 🔴 Reports
    • Tax related
  • 🔴 Search
  • 🔴 Polish : (note: Expect a LOT of visual changes here. Prior it's a: 'just get it working, look pretty later')
    • 🔴 Dashboard
    • 🔴 Account
    • 🔴 Transaction
    • 🔴 Files
    • 🔴 Recurring Group
    • 🔴 Recurring Transaction
    • 🔴 Search
    • 🔴 Report

Various notes / ideas

  • Alternate sort methods
  • Export/Import: Test: file data, lookups, and link tables
  • Unit Testing
  • Hard deletes or soft deletes? Currently everything is a hard delete.
  • Logging: Should there be a history table which talks about all db changes? This might allow for hard deletes while preserving information
  • Session history tracking
    • Recoring changes
    • Back and forward button support

  • Encrypting important things / encrypting everything / encrypting nothing
  • Globalization / Locatlization
  • Background service to run bill processing on if something is late?

* Do I need to copyright the code? Does it really matter?

Help Request

  • Unit testing. I have no experience here. :(

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published