Version 2.0 poll (Planning & Discussion) #29
Replies: 6 comments 14 replies
-
|
Personally, I'm leaning more towards improving the looks, even if it means moving away from the single-file executable. Sure, it might feel less like a straightforward tool and more like a full-fledged app, but it would give us way more room for UI customization. Plus, the performance hit isn't that big of a deal. |
Beta Was this translation helpful? Give feedback.
-
|
Just a quick update - it's not abandoned, but I had some stuff going on, so couldn't really pay much attention to this tool. Hopefully I'll get to it soon |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
The bad news: I ditched the "v2". Not going to work towards this implementation, as I am extremely unhappy with what I was getting, and problems that final product would have no matter what I try. The good news: v3 is about to be finished. Also, I am publishing new version on Microsoft Store, and a bunch of features are to be bundled:
Windows Store version will be paid (maybe someone will support my work). However, I am still going to publish app in release page here. |
Beta Was this translation helpful? Give feedback.
-
I like the new menu, will there be an option to add additional metadata fields? Street and other street would be very useful for adding crossroads |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thank you so much!
…On Fri, Jan 23, 2026, 2:26 AM Jamminroot ***@***.***> wrote:
Why not, sure, I can add that
—
Reply to this email directly, view it on GitHub
<#29 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALQ2KYR5EYN2JSCYASJRLGT4IHSLXAVCNFSM6AAAAABOLCTGASVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNJXHEZDKNI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone!
I've been thinking about a few features I'd love to add to the app, but they don't quite fit with the current setup/UI. That got me thinking about and planning for version 2.0.
I've been looking at a few different languages/frameworks that might work well for the new version, but some of the design principles we used in v1 might not mesh with them as smoothly. For instance, we could swap the single-file executable for a nicer-looking interface, or we could further simplify the UI to shrink the executable size. Another option is to consider a background (always-in-memory) app—though it's not my first choice, it could be something worth exploring for some of you.
With that said, I'd love to get your thoughts on the design principles (not features) you feel are most important for this next version. This will help guide me in choosing the right framework for us.
Feel free to drop your thoughts in the poll or share any extra opinions in the comments!
Note that
always-in-memoryvsuse as little RAM\CPU as possibleis a different vote which is not yet in poll, but can be discussed here too.11 votes ·
Beta Was this translation helpful? Give feedback.
All reactions