SyMenu Forum

SyMenu

 

Home ▶ SyMenu Plugins

Everything related to SyMenu plugins: discussion, development, documentation and release

Github SPS Updater - Updates & Add apps Messages in this topic - RSS

Gianluca
Gianluca
Administrator
Posts: 1409


4 days ago
Gianluca
Gianluca
Administrator
Posts: 1409
I completely disagree.
The solution is simple: the plugin must not touch the SPS managed by SyMenu and NirSoft. Those are already controlled, verified, and updated by the SyMenu engine itself.

Custom suites, on the other hand, are meant to be managed externally by the plugin.
Letting the plugin operate freely inside the SyMenu and NirSoft folders will only cause issues.

I have to ask: why should the plugin manage SPS that are already being managed? What is the reason? I really can't see it.
link
ronen1n
ronen1n
Posts: 33


4 days ago
ronen1n
ronen1n
Posts: 33
ok but with that logic we need to block updates or creating new app in from the plugin that already in the symenu because if we create sps and update app faster than symenu or you're not the uploader for this app so you need to wait, the problem still exists it will show downgrades
not sure what's wrong with it updating the symenu that the local files are more updated then the symenu update if symenu can't do it?
maybe and we use the plugin just locally without updating symenu server for new apps that way the app will be in each user who wants it but not on symenu so it won't need to get fixed to not show downgrades
you say it's simple to limit the plugin a lot to just update github apps and apps that not in symenu or not in nirsoft but also want new apps to get into symenu list so what's the point? even if its only github and i upload it to symenu list ill need this fix
didnt see issues with this plugin fix yet
give me better solution and show me real problem with what that is done now
link
Gianluca
Gianluca
Administrator
Posts: 1409


3 days ago
Gianluca
Gianluca
Administrator
Posts: 1409
Dear ronen1n,

I think there is a misunderstanding here.

SyMenu and the plugin have different goals.

SyMenu updates are intentionally based on human validation and publication. An SPS becomes available to all users only after an editor decides to publish it. This design has several advantages: quality control, source verification, licensing checks, VirusTotal verification, package structure validation, and support for any download source, not only GitHub.

The plugin follows a different approach. Its goal is to detect and apply updates much faster by relying on automation.

Both approaches are valid, but they naturally produce different results.
If the plugin chooses to update SPS definitions that belong to the SyMenu or NirSoft suites before the corresponding official definitions are published, temporary version mismatches are expected, and a loop of continuous updates and downgrades may occur until the SyMenu definitions match those generated by the plugin. In some cases, this may never happen.

How should those mismatches be handled?
Not by SyMenu, because it has to follow its own logic and workflow.
Not by the plugin either, because it has to follow its own logic and goals.
IMO, the only way to solve this is to prevent the two logics from overlapping.
And to prevent this kind of doubt, should I stop maintaining GitHub-based SPS files in the official suites because the plugin now exists?
I don't think so. The plugin is still relatively new, not every user relies on it, and it still needs time to prove its robustness, reliability, and long term accuracy.
Moreover, I still don't understand how a new GitHub SPS managed by the plugin should reach users for the first time. If it is distributed through the official suites, we are back to the overlap problem. If it is not distributed through the official suites, how does it initially reach the users? Well this is entirely obscure for me.

Custom suites are a different story because there is no official editor workflow behind them, which is why I see much more value in the plugin operating there.

What happens if you are not satisfied with the release pace of a SyMenu suite application?
For example, for Thunderbird Portable I chose to follow the ESR releases rather than every available version. If Thunderbird Portable were available on GitHub, you could choose whether to manage it within its original suite or manage it through the plugin. The latter approach suggests placing it in a custom suite.
This is how I would operate, but every user is free to work the way they prefer.
If you want to suggest a workaround that enables a different scenario, you are free to do so.


Remember when I was talking to you about the architectural choices you took for the plugin?
This is one of the friction points I had in mind when we previously discussed the plugin scope.
The plugin can certainly choose different directions from what I suggested, but in that case these kinds of conflicts are expected and should probably be addressed at the plugin level rather than at the SyMenu level.


A big element of confusion comes from this sentence:
ronen1n wrote:
you say it's simple to limit the plugin a lot to just update github apps and apps that not in symenu or not in nirsoft but also want new apps to get into symenu list so what's the point?

Creating new SPS for the official suite, submit them, and enriching the SyMenu echosystem can be a nice thing the plugin can bring on the table.

But please don't confuse the role the plugin could have for an end-user and the role it can have for an editor.

If you are an editor and decides to go with the plugin to create/update your GitHub SPS for the official suite, please be my guest.
You have to grant the same high level quality I expect from any editor and take responsability of your SPS.
So you can use the plugin to get help with updates and use it to load the new/updated SPS to the cloud.
But from there on, I don't care how you worked, your work has to meet the same quality standards as any other SPS published through SyMenu. The SyMenu community deserves the highest level of validation we can reasonably provide.

On the other hand you have the users.
Why should an average user perceive the plugin as more useful than the standard automatic updates?
In most cases, there is no compelling reason. The users want a trustable system that takes care of their program automatically. Most users are more interested in stability and reliability than in receiving updates a few days earlier.
An advanced user may find it useful to add software that is not yet available in the suites, and the plugin enables exactly this kind of customization but why a normal user would have to mix the official suite with custom SPS? I don't see the reason.

There's a third scenario, where an editor want to use the plugin to create a custom, publicy-available, suite (sl23 is working on a suite like this). The editor probably can choose to use the plugin to create the SPS and suggest their users to use the plugin to get the updates. So they publish the starting definitions, the users download it, and from then on the plugin takes the lead.

And probably there's many other use case possible. But again, these are the kinds of design considerations that inevitably emerge once a tool starts being used in different ways by different users, and, above all, this kind of discussion is not suitable for this forum (I imagine nobody except the two of us read all this long post).
To be fair, these are exactly the kinds of questions I hoped we would address during the design phase.
They don't necessarily invalidate the plugin, but they become increasingly important as the plugin starts being adopted by a wider audience.

edited by Gianluca on 16/11/2026
+2 link
sl23
sl23
Posts: 330


3 days ago
sl23
sl23
Posts: 330
If I am honest, I can't say I would use this plugin. Mainly because it is not really clear to me what it is doing and how it is doing it. That said, I think it is a really great idea and should be continued. But at its present state, It is not something I can trust the use of. As Gian pointed out, stability and reliability are paramount. If I don't even know how to use it, why would I trust it not to mess up my apps installations? I'm sorry, but I am not that brave! If I had more time to spare then I would most likely go to the trouble of making specific test folders for this to try it out. But, for me, thats not going to happen.

A simple example... What does it mean when an app states: Official Suite: No upstream source configured?
Absolutely no idea what that is supposed to mean?!

Browse PortableApps.com directory... To me this should say something like: Install from PortableApps.com.

I'm guessing it is a translation issue though rather than poor choice of wording. But you've also got: Add App/From PortableApps.com (520+ apps) is this the same as the above, if so, why is it there twice and named two different ways? This causes confusion and confusion in software means one thing to users: uninstall it!

Again, SPS Community Publisher (Check uploader apps) no idea what that means? What does it do, how do I use it, what benefit is it to me? I open this window and am totally clueless what it is for!

What is the Overlays manager and why would I want to use this? Again, it is extremely vague what this is doing. How does all of this affect my apps or the Current SyMenu installation. I'm not prepared to corrupt anything just to test this out. I am not trying to be harsh, I am just trying to point out some basic things that users will see and feel when downloading your plugin. If it is of no immediate use or can't be understood, most won't bother with it, would you?!

Prune menu shortcuts - What is this? Does it delete broken shortcuts? Then it should say that.
Merge PortableApps... - Do you mean this will Import PortableApps? Which to me is the typical wording for such a thing.
I have a setting called: Patch official suite definitions blah, blah... Yet I am constantly getting upgrades and downgrades showing despite this being ticked by default. I have changed no settings or touched anything since installing the plugin other than open windows. I open the normal SPS Manager and get asked to update three apps, as I explained to Gian in an email: Audacity, for example, is asking to upgrade, I do so, then I am again asked to downgrade, then upgrade, downgrade, wtf?! Uninstalling the plugin stops this behaviour. I find the plugin interesting and would like to advise much as I can, but these issues need resolving for it to be of any use.

Don't be disheartened by my comments, I mean only to give instructional criticism, not pessimistic abuse. I am trying to make you see how I see it so you can try to make the plugin easier to use and less buggy. I hope you can resolve these things because it looks good and is a great idea.

I will also say, although Gian is right, I do see the merits of having this plugin cater to the default suites. There are users who do not want auto updates, do not use SyMenu in a traditional way, but may want to use this plugin in some other manual way, and that could be where it becomes useful to take control of the default suites. Or if Gian stops being interested and no longer updates the default suites, it could happen! Many possibilities, so this could replace that. Tbh, this could potentially even replace the way Gian works and make it easier for him to continue updating the default suites much more easily, who knows?

EDIT: Just looked at the first post again! Ok, some of my criticisms are explained there. I would suggest having a Help option that opens a window to explain what things are, like in your OP. Or, and this may be better, in each window, have a dedicated area at the bottom that shows tooltips when hovering over things. Then the manual is integrated and better explains what things are.

edited by sl23 on 16/11/2026
link
ronen1n
ronen1n
Posts: 33


3 days ago
ronen1n
ronen1n
Posts: 33
Gian I think you can delete this thread because of the following reasons:
1. I offered all the code to you to do anything with it and you didn't think any of that can be added to the app so didn't want it
2. you think that the GitHub option can be used but not any of the others
3. some users don't trust it and it make sense not to
4. i enjoy the plugin like that because i set all the updates once and get the latest updates for all apps without the need for manual symenu updates that dont make sense to me
5. I'm not sure I will add more apps to symenu apps list as uploader now that i have automatic updater
6. I get that each of you want the plugin 100% to your liking but this plugin is 100% now for my liking so I don't see why i need to change any of it and work by my self
sl23 sorry didn't read all your notes because i won't change it anymore because it's not even in the right direction
link
sl23
sl23
Posts: 330


3 days ago
sl23
sl23
Posts: 330
Thats ok, I understand, you cant please everyone all the time! wink
No offense meant, I thought you were working alone and intended to keep it that way.

It's not that its wanted to be to my liking specifically, its that when designing an app, you have to make it foolproof, if you dont design it like that, how can you expect it to be popular?! That is the basis of what I said.

I get there is a translation barrier, understandable, but if you want to share something, as can be seen by just about any other app in existence, it has to be legible in English, if it isn't people tak eit the wrong way or plain misunderstand what it is meant to do. It's a fantastic idea!

Gian has spent over twenty years on SyMenu, isn't that enough? I get you think this should be integrated, but if you are vibe-coding, one thing to learn, stick at it! Because that is one issue many have with us and it is a valid point. AI is new and everyone wants to be a developer, it is not an easy thing, to do. The hardest thing is sticking through it when it gets tough, and now, this is getting tough, don't give up, you're doing great. As I said, if you want to share it needs better wording and tooltips to explain in the app. That would go a long way to helping users understand how this works without havin gto look things up everytime they want to use it.


Anyway, thanks for the effort wink

Is the source on Github? Are you willing to share it? Maybe I can take a look and try help, not sure exactly when, I am trying to create a suite of AudioPlugins at present, and only on my third!

edited by sl23 on 16/11/2026
link
Gianluca
Gianluca
Administrator
Posts: 1409


2 days ago
Gianluca
Gianluca
Administrator
Posts: 1409
Dear ronen1n,

I think we simply have different goals.

You built the plugin primarily to solve your own problem, and from what I can see it does that very well.
My interest was different: I was trying to understand whether some of the ideas behind the plugin could evolve into products suitable for the broader SyMenu ecosystem.

Sometimes these two goals overlap, sometimes they don't.

As I said from the beginning, I think some of the ideas in your plugin have great value.
We simply disagree on how they should evolve and above all how they should interact with the official suites.
That's perfectly fine.

If the plugin works the way you want it to, then you have achieved your goal.

The forum thread should absolutely stay where it is.
Users can test the plugin, share feedback, suggest improvements, and decide for themselves whether it fits their needs.
Also, for what it's worth, I'm currently using the plugin myself for some software in my custom suite and I expect I'll continue using it because, in that scenario, I think it does a very good job.
So please keep sharing new versions if you decide to continue developing it. I'll be happy to follow its evolution and test new releases.
And if, at some point in the future, you ever feel like revisiting some of these design discussions, you know where to find me.
The door is always open.

Good luck with the project.
+1 link
12



UGMFree © 2002-2026
PayPal BTC TON