Hi all,
I first came across TicketsCAD sometime around 2010-2011. Back then there was an installer that packaged the whole thing — web server included — onto a machine.
I've been trying to find any history on it (why it was pulled or discontinued, or just quietly left behind) and haven't turned up much online, unless I'm just missing it. Not trying to stir anything up or suggest it should come back exactly as it was — I'm mostly just curious, and reflecting on how far the project has come since I first used it.
For context: I used TicketsCAD as my "spreadsheet" for logging what I heard on my local police scanner, so I could track and visualize activity in my area — it was a pretty busy area, so yes, some would call it overkill, but it's been a hobby of mine ever since (and still is). I also use it for testing purposes these days.
If anyone has history on the old installer or knows why it fell off, I'd love to hear it.
Thanks!
--
You received this message because you are subscribed to the Google Groups "Open Source CAD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-source-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/8124434e-b1d6-4fa0-87b0-abf5d8d43d6bn%40googlegroups.com.
Thanks for the context, Arnie! Your mention of WAMP and XAMPP actually helped connect the dots for me and jogged my memory on how it was put together.
The Windows .exe installer I was thinking of was a custom-packaged bundle called "TicketsGo" (distributed as ticketsgo.exe). Drafted by Kevin Bednar (K2KMB)
It wasn't built by the core project as a standalone application, but was a wrapper put together back around 2010–2011 to solve the exact barrier you mentioned—the headache of manually setting up Apache, PHP, and MySQL for non-technical users.
From what I recall of that installer bundle:
• The "Go" Bundle: It silently bundled a lightweight, pre-configured WAMP/Apache environment so a dispatcher or hobbyist could run a single installer file and go live.
• Automated Setup: It handled the file extraction directly into the local web directory, built the initial "Tickets" database tables, and configured basic firewall rules for port 80.
• Desktop Shortcuts: It generated a desktop shortcut labeled "Launch Tickets Go" that automatically pointed the user's browser straight to http://localhost/tickets.
Because it was a third-party installation package rather than the core code itself, it makes sense why it quietly faded away as web stack environments changed, dependencies aged out, and the project transitioned over to its current Git-based, collaborative structure.
It’s great to see how far the project has come since the days of manual zip extractions and legacy local server bundles!