-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find someone to take over QST #247
Comments
Are you using the software yourself? |
Not anymore, I'm using the official tray icon that comes with the macOS bundle. |
Opened a topic on the syncthing forum. |
Awesome, thanks for taking the initiative! |
Sorry, but I like your software more 😛 That one is over-featured. |
In theory it would be possible to add a simplified GUI to my Syncthing Tray. But I've created it mainly because QSyncthingTray lacked a lot of features I like. Still, I'm wondering what's actually bothering you. If it is the dependency for Qt WebEngine/WebKit: You can disable it at build time. |
@Martchus When I judge the usefulness of a software I do through the eyes of someone not very tech savvy. On one hand because I want it to be usable to as much people as possible, on the other because the amount of options a software has tells something about how much work there has been in simplifying its internals. The more streamlined a software is the less technical options it has, cause the software is able to make those decisions automatically and because it is selective in what to include and exclude. The software only provides options related to the user work itself, but not about the technical aspects of it. The simpler the API and interface is the more advance the internals usually are. The oposite is wanting the software to do everything and cover any possible situation, by making the user decide about corner cases that will rarely happen. Aka 90% of the time it works every time. When I develop software it usually has very few features, very little code, and very few tools. But what people don't see is how much improvement took me to reach that point, that so little does the work perfectly. Is not what I have left in, is what I have been able to left out without that having consequences. |
@sieren I could maintain qsyncthingtray if it's only on Linux. I would delay a little bit in the beginning, buy once I finish what I'm working on I would be able to properly maintain it. |
Ok, so you don't like the "advanced" configuration options. These are definetly something I'm not going to simplify so I guess Syncthing Tray will never be an alternative for you then. Considering these different preferences it is actually good that I decided against contributing to QSyncthingTray and rather started my own project. I don't quite get why you think Syncthing Tray would let the user decide about corner cases, though. The options of Syncthing Tray are mostly about enabling/disabling features you want or don't want to use and about tweaking the appearance to your taste. The configurable intervals might be a bit odd, indeed. However, QSyncthingTray has this kind of configuration, too. I also disagree on the "few feature" philosophy in general. You will for sure end up with something that works perfectly (or at least quite well). However, the scope of that program will be rather limited, too. For instance QSyncthingTray does not help me to quickly pause/unpause a device or directory simply because that feature is missing. But it is still nice that you might maintain QSyncthingTray. Syncthing's API and Qt's API are very stable in my experience so that is actually not going to be that much work - especially since QSyncthingTray only uses a small fraction of these APIs. |
What's the purpose of pausing? |
I can tell you my use cases: I usually use it if I have only a limited internet connection and therefore want temporarily exclude a (large) directory completely. I occasionally use it to prevent rescans of large but rarely changing directories completely on slow devices (setting the rescan interval to zero does not prevent the initial rescan on startup). |
@sieren Could you at least for the time being make a release of the current code, so downstream packages can update to it? |
@sieren seems like the latest version of syncthing handles mac pretty well natively, should this project be archived? or at least point out that people can just install syncthing and run it? |
@jcrben yeah, I've actually moved on to the mac version myself. We have a few Linux users in the community though, but there are other projects worth using in the meantime (@Martchus 's https://github.com/Martchus/syncthingtray for example) that are much more extensive and better written (this was my first Qt project ever). I'll consider sunsetting this for good or at least updating the README and pointing people to better alternatives. |
I think those alternatives suck. I know how this ends: me eventually coding the alternative. |
This package is abandoned upstream and depends on the insecure and abandoned QtWebKit. Upstream abandonment: sieren/QSyncthingTray#247 See <https://issues.guix.gnu.org/53289> for more information about this change * gnu/packages/sync.scm (qsyncthingtray): Move this variable ... * gnu/packages/syncthing.scm (qsyncthingtray): ... to here. And make it into a deprecated-package that points to syncthing-gtk.
Since I have limited time to take care of QST, I'd like for someone to step in and take over leading this project.
If anyone is interested, please drop me a line here or send an email to matthias (at) s-r-n.de
The text was updated successfully, but these errors were encountered: