Version 2.0 poll (Planning & Discussion) #29
Replies: 3 comments 4 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.
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-memory
vsuse as little RAM\CPU as possible
is a different vote which is not yet in poll, but can be discussed here too.8 votes ·
Beta Was this translation helpful? Give feedback.
All reactions