|
Gianluca Administrator Posts: 1409
07/10/2026
|
Dear all, A new version has just been released. The most important changes are:
- A new interface for the plugin system (whatever that means!).
- SyMenu now highlights in the context menu the updates availability in any SPS suite, including custom suites, through a dedicated icon and special text in the context menu.
Let's take a closer look at these two features.
Plugin startup notifications The new plugin interface allows a plugin to be notified whenever SyMenu starts. A more consistent implementation might have been to leverage SyMenu's native Autoexec on Start feature. However, that would have required users to enable Autoexec just to execute a plugin during startup. It seemed preferable to let the plugin itself declare its intention to run at that stage. For those interested in the technical details, the new interface is called ISyPluginNotificationStartup and, as usual, it is exposed through SyMenu.Plugin.Resources.dll. If you need further information, you know who to contact.
Update notifications for secondary and custom suites This is a long-awaited feature. SyMenu can now show update notifications not only for the main suite, but also for the secondary suite (NirSoft) and even for custom suites created by users. When updates are available, the corresponding context menu entry is highlighted with a dedicated icon and text, making it much easier to spot pending updates.
As always, if you have questions or need additional details, feel free to ask.
|
|
|
link
|
|
sl23 Posts: 330
08/10/2026
|
I sent an email about this, but perhaps it may be better to post here, then users can see how this affects their own suites.
So the idea of this is that for personal/custom suites to notify SyMenu via the blue Get New Apps icon, by turning it green, is that right? Does it extend that far? But I see you have actually added per item in-menu update notification.
Is there anything an author of a custom suite needs to do? Or is this purely on SyMenu side? As already discussed via email, I plan on releasing a custom suite for AudioPlugins, will these need to be zipped, as the current two built-in suites are, or do I need to make these individual files?
I am just trying to figure out some things wrt how this will work. For example, for a zipped file that can be easily downloaded by users in one go, it becomes necessary for me to manually add new files however I receive these from others, into the suite. For individual sps files, I don't need to do this, but then how do others download all of the separate files as a suite? Its a bit of a problem either way. I am trying to think of how this could literally be done automatically, I realise checks need to be performed on sps files to avoid spam and malicious sps files, but how do you do this? What is your process?
Essentially, we need to understand the process for creating, sharing, updating custom suites.
Thanks for the update, it is indeed a great thing you've done! 
edited by sl23 on 08/10/2026
|
|
|
link
|
|
Gianluca Administrator Posts: 1409
08/10/2026
|
I confirm that SyMenu uses the notification icon status for custom suites too. But how does this work? What does a custom suite editor need to do in order to notify SyMenu about updates? Actually, nothing special is required. The mechanism is exactly the same as the one used by the main suite.
Let me explain. When SyMenu starts, it checks its endpoint for updated SPS definitions. If newer definitions are available, it downloads them into its _cache folder. In your scenario, these two tasks are delegated to the plugin. I agree that distributing the custom suite SPS files as a ZIP archive is the simplest solution. SPS files are very small and compress extremely well, so a ZIP archive grants a small download size and a single file to manage. The only difference between the main suite and a custom suite is that for the main suite SyMenu can read SPS files directly from the ZIP archive, while for the custom suite it needs the files to be extracted first. However, unzipping a file is trivial and the plugin can do that in secs.
Once the plugin has downloaded and extracted the updated SPS files inside the custom suite _cache folder, the situation becomes identical to the main suite. At that point, SyMenu can detect available updates in exactly the same way it does for the official suite.
How? Through the software version stored in each SPS file. Let's see the entire workflow. When a new version of AudioPluginABC is released, you would: - update the master SPS for AudioPluginABC, changing the version number and, if necessary, the download URL and any other metadata (file size, VirusTotal information, etc.); - package the updated SPS files into sl23CustomSuiteCollection.v345.zip; - upload the updated ZIP file to your endpoint; - let the plugin and SyMenu do the rest.
The plugin is responsible for checking whether a newer SPS collection is available, downloading it, and extracting it. SyMenu is responsible for determining whether any installed applications in the custom suite require updates by reading the downloaded SPS files.
I also suggest versioning the ZIP filename (for example, v345). This gives the plugin a simple reference point to determine whether the online definition package is newer than the locally downloaded package.
If you adopt this approach, remember to preserve a version marker that the plugin can compare against. This can be the previous ZIP file itself, an empty file named after the version (for example, v345), or a simple text file containing the current version number.
Another important point is the role of SPS Builder. You can use it for sure. What you can't do is upload custom suite SPS files to the UGMFree cloud. For a custom suite you can work with local files (SPS Builder does this easier), and upload the definitions manually to your endpoint.
If you need any other information, please ask.
|
|
|
link
|
|
sl23 Posts: 330
08/10/2026
|
ok, I need further information! lol
I'm totally confused! You keep mentioning "the plugin", what plugin is this? Do I need to create one specifically to manage this suite, or is that the part you have done in this update?
So I have to do the following:
1. Create a zip of all sps files contained in the suite. 2. Upload to say, github. 3. But whats the Master SPS you mention and where does this go? Where do I place this? does it become a part of the suite itself? Then I update that whenever theres an updated sps within the suite?
Could I create a SyMenu plugin that does this check automatically? ie, it performs the check online to see if the updated suite matches the latest installed version via a blank versioned file.ini then downloads and installs into the suite if newer.
|
|
|
link
|
|
Gianluca Administrator Posts: 1409
09/10/2026
|
sl23 wrote:
I'm totally confused! Let me clarify, because I think I jumped ahead.
sl23 wrote:
You keep mentioning "the plugin", what plugin is this? Do I need to create one specifically to manage this suite, or is that the part you have done in this update? About the plugin: yes, you would write it yourself. What I changed in this update is that SyMenu now tells every subscribed plugin when it starts. SyMenu doesn't manage custom suites by itself as it does with the main suite, so your plugin uses that "SyMenu is starting" moment to do the work. For example, it can check online whether a newer version of your suite definitions is available, or prepare the local folders on first run.
sl23 wrote:
Could I create a SyMenu plugin that does this check automatically? Yes, you can and you should. Without it, your suite is just a definitions file online that users must download and update manually.
sl23 wrote:
whats the Master SPS you mention and where does this go? Where do I place this? does it become a part of the suite itself? Then I update that whenever theres an updated sps within the suite? About "Master SPS": sorry, I was describing my own setup. "Master" is just the name I would use for a local copy of the SPS files. It is not part of the suite that users receive. Here is the workflow I would follow: - Keep the SPS files of your custom suite in a local folder (your "master" files). - Edit them with SPS Builder, which also helps check file integrity and VirusTotal results. In theory you can do it manually, but then you must check file integrity, VirusTotal report, package size, exe availability, and so on, by yourself. - Donโt use SPS Builder to upload these files to the official SyMenu suite, or they would become part of it. - When ready, zip the files and upload the zip to an online location, for example GitHub. - When a file needs an update, edit it in your master folder, create a new zip with all the files and upload it again. - Your plugin checks that location at SyMenu startup (for example by comparing a version number in the zip name or in a small config/ini file). - If there is a newer version, the plugin notifies the user, who can then update the suite automatically, exactly as they do with the main suite.
|
|
|
link
|
|
sl23 Posts: 330
12/10/2026
|
Thanks for explaining, I see I completely misunderstood now! lol
One thing, how do I even start with a plugin? I mean, I surely need a basis for how the plugin should interact with SyMenu, is there a template or something, so I can work from that to get my plugin to work correctly? Or is that something still in the works? (EDIT: No worries, I saw you sent me a link in my email! Thanks very much.)
Thanks for the great update, this expands SyMenu considerably! 
edited by sl23 on 12/10/2026
|
|
|
link
|
|
Gianluca Administrator Posts: 1409
12/10/2026
|
Ok, to be clearer with everyone reading this thread, what I sent you is a code template in C# to start creating your own plugin.
|
|
|
link
|
|
sl23 Posts: 330
12/10/2026
|
Thanks Gian, i will look at this soon, still a bit tied up with my PolyHost app/plugin.
One question... Would it be ok to sue RAR instead of a ZIP file? I prefer RAR and is easier for me to deal with. Besides, I have had several corrupted ZIPs lately where I update the ZIP file content, no idea why, but RAR seems much more robust, never had any issues with them in over 15 years and I use them constantly on a daily basis. My plan was to create the archive and upload to github so the plugin can check the latest release and update accordingly.
EDIT: Github repo created: https://github.com/sl2365/AudioPluginsSuite Suite name: AudioPlugins Filename: AudioPlugins.rar
edited by sl23 on 12/10/2026
|
|
|
link
|
|
Gianluca Administrator Posts: 1409
13/10/2026
|
It's not a problem whether you use a RAR or a ZIP archive because the plugin itself is responsible for unpacking it. So it's your choice. Anyway, I rarely use RAR because it is a proprietary format. They keep the archiver proprietary while providing the extractor for free, which I find a bit awkward. I've never had any issues with ZIP files, either when using GUI tools or when creating and extracting them programmatically. The issue you got was probably related to the specific ZIP implementation rather than the ZIP format itself. For more than ten years, whenever I needed compression or extraction features in SyMenu, I've relied on 7-Zip through command-line calls rather than implementing the compression algorithms directly in code. Because of that, I'm a lot out of touch with the implementation details and common issues of ZIP libraries, so I'm afraid I can't give you any particularly useful advice on the coding side.
|
|
|
link
|
|
sl23 Posts: 330
13/10/2026
|
Hi, I have one small issue. I havent really started this yet, but am at the initial development stage, planning. I have found one flaw in the example plugin, or rather ChatGPT has. There is no way to know if a user has clicked the Update App Definitions button in the SPS Manager. If my suite is loaded and I click that, it is expected that a check/download would be performed, yes? But the current test plugin does not have that ability yet. Would you be able to add that or have I missed something?
Thanks much appreciated.
|
|
|
link
|
|
sl23 Posts: 330
13/10/2026
|
I am almost there, well, about halfway to a release. Should I upload the source to the github repo? Or do you want it kept private? Also, do you want to review the code to make sure it is suitable rather than me just releasing the plugin?
The final behaviour will be:- SyMenu startup + already current: no popup.
- SyMenu startup + successful first install/update: no popup.
- SyMenu startup + failure: show an error.
- User clicks AudioPlugins: perform a fresh online check and always show the result.
- Future SPS Manager manual refresh notification: perform the same check/update silently, then return control to SyMenu.
Too late! I'll email you the entire project so you can check and let me know when its ok to release it or whether its ok to upload the project to github. Thanks for your help with this! 
EDIT: email sent.
edited by sl23 on 13/10/2026
|
|
|
link
|
|
JOJO459 Posts: 2
2 days ago
|
Hello, author. I am a user from China. When I used the older version, it had Simplified Chinese. After updating to the new version, I found that Simplified Chinese has been removed. Will Simplified Chinese be added back in future updates?
|
|
|
link
|
|
Gianluca Administrator Posts: 1409
2 days ago
|
JOJO459 wrote:
I found that Simplified Chinese has been removed. Will Simplified Chinese be added back in future updates? Hi JOJO459. It hasn't been removed. It has been downgraded to "Not Official Language" because the translator is no longer active.
You can still use SyMenu in Simplified Chinese. Any missing labels will simply appear in English. And if a new translator (a human one...) comes along, the language will be reinstated as an official one.
|
|
|
+1
link
|
|
JOJO459 Posts: 2
1 days ago
|
Thank you very much for your reply.๐๐
|
|
|
link
|