From e6f180ae2d13a19aa4b3dec18b16af3e4a9794c0 Mon Sep 17 00:00:00 2001
From: Tony Bark <35226681+tonytins@users.noreply.github.com>
Date: Mon, 24 Aug 2026 01:16:32 -0400
Subject: [PATCH] Brought back changelog

Updated the app bundle identifier and version for the 0.2.101 release, refreshed the README link to SwiftCrossUI, and added a changelog documenting the rewrite and previous release history.
---
 Bundler.toml |  4 ++--
 README.md    |  4 ++--
 changelog.md | 19 +++++++++++++++++++
 3 files changed, 23 insertions(+), 4 deletions(-)
 create mode 100644 changelog.md

diff --git a/Bundler.toml b/Bundler.toml
index a42c273..6c84fb4 100644
--- a/Bundler.toml
+++ b/Bundler.toml
@@ -1,9 +1,9 @@
 format_version = 2
 
 [apps.AmtrakStatus]
-identifier = 'com.example.AmtrakStatus'
+identifier = 'com.tonybark.AmtrakStatus'
 product = 'AmtrakStatus'
-version = '0.1.0'
+version = '0.2.101'
 icon = "./assets/icon.png"
 
 
diff --git a/README.md b/README.md
index 848686a..b132b6e 100644
--- a/README.md
+++ b/README.md
@@ -36,9 +36,9 @@ swift-bundler bundle -c (release|debug)
 
 This was intended to solve a rather awkward dilemma. I turned a bunch of online Amtrak status boards made by [Dixieland Software](http://dixielandsoftware.net/Amtrak/status/StatusMaps/) into PWAs (standalone web apps) for stations that I viewed on Virtual Railfan. While it was convenient - don't get me wrong - I had to create a new web app for each and every station, and it was becoming overwhelming.
 
-So I created simple frontend that mapped to Dixieland Software's API using Tauri. You could type in simple station code and it'd take you their status board from within the app. Simple, right? Unfortunately, I didn't know how to get it go back to change the station, my attempted UI redesigns kept failing, and I accidentally botched a migration to Tauri 2.0.
+So I created simple frontend that mapped to Dixieland Software's API using Tauri. You could type in simple station code and it'd take you their status board from within the app. Simple, right? Unfortunately, I didn't know how to get it go back to change the station, my attempted UI redesigns kept failing, and I accidentally botched a migration to Tauri 2.0. I'm just not that good with Node.
 
-So it sat abandoned until I discovered SwiftCrossUI. Now it directly makes use of [Amtraker](https://amtraker.com/)'s API.
+So it sat abandoned until I discovered [SwiftCrossUI](https://github.com/moreSwift/swift-cross-ui). Now it directly makes use of [Amtraker](https://amtraker.com/)'s API.
 
 ## ⚖️ License
 
diff --git a/changelog.md b/changelog.md
new file mode 100644
index 0000000..01f377a
--- /dev/null
+++ b/changelog.md
@@ -0,0 +1,19 @@
+# Change Log
+
+## 0.2.101
+
+Completely rewrote from scratch (except the ported models) using [SwiftCrossUI](https://github.com/moreSwift/swift-cross-ui). This new version now adopts to whatever system it was compiled for. A huge step above from pointing to a web page. While this did involve a lot of work to get it back up to speed, it was wroth it.
+
+## 0.1.104
+
+- New buttons for major terminals and rail cams.
+- Version displayed above credits.
+
+## 0.1.102
+
+- Redesigned icons
+- Added banner above form
+
+## 0.1.101
+
+- First public prototype
\ No newline at end of file