|
VVV_Easy_Symenu Posts: 159
28/01/2018
|
Hello,
With SUMO SPS App I have noticed of a unexpected behaviour: In the SPS Apps with "Build in updater" checked, the "Get new apps" don't alert of the update of app.
I supose that this is because SyMenu get the version from "*.sps.version" file and, if the user have updated the app with the build in updater, the version is wrong.
But I strongly prefers always use the SPS update (even I uncheck the inner app version check if possible) because the new version was tested by the publisher before update.
Perhaps for cover the two kind of user, can be added in the "Get new app" form a checkbox "Alert update disponibility always" or "even with build in updater" or in the avanced configuration options.
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
29/01/2018
|
Leave the choice for an SPS update or a native update to the users is a brilliant idea: a base user will allow the system to choose the best option for him, while an advanced user will choose independently the right option.
The problem here is that a change at this level in the SPS system is so big.
Currently the SPS Manager doesn't care about different versions among a program SPS and what the file system is telling, if it find the version placeholder file "0.00.sps.version". This file is the way the SPS Manager understands that it isn't in charge for updates.
But I agree, it's not a perfect way. At the time of its implementation it was a fast system to solve the problem of the double updates (one because the program and one because the SPS).
I have to think about a more flexible solution. Probably your suggestion is the right path even if I prefer an explicit choice per program instead of one for all of them. But, as I told you, I have to study it a lot.
|
|
|
link
|
|
VVV_Easy_Symenu Posts: 159
30/01/2018
|
With your explanation of the "0.00.sps.version" I understand all.
I have thought tha SPS Manager first look at the "Build in update" propierty but I understand that it would be very slow.
Perhpas may be a mix system "BIU.4.51.sps.version".
Well, to the TODO list ....
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
31/01/2018
|
Unfortunately the version attribute is not used in a consistent way in all the programs.
Some of them (Tor browser for example) use a shortcut that has no version inside.
Some others use a laucher that never changes its version (Firefox launche is 2.1, the program is 58.0 instead).
Again, others (SUMo) fill the file version attribute but leave to zero the product version.
Others, such as the entire OK suite, use a version and declare another created combining the minor and build number (DesktopOk is 4.9.4.0 but the web site declares a 4.94).
The program versioning is a real mess, well, BTW developers are all crazy... me too anyway  , and for this reason is impossible to safely check anything from the program executable.
|
|
|
link
|
|
VVV_Easy_Symenu Posts: 159
31/01/2018
|
Yes, try to get the version from the program is crazy ... I see the problems that SPS Builder have with this.
But I can suggest you a alternative/intermediate solution.
If I have understood well, in the app instalation, SyMenu set a "vvv.sps.version" with the "vvv" app publisher version in normal and "0.00.sps.version" in the build in update case for avoid the update alert.
But if you set, for instance, "BIU.vvv.sps.version" (Buil In Update) in the place of the "0.00.sps.version", SyMenu can know if the app has a build in update (for the user that update with the app) and the SyMenu app version instaled (for the user that wants the alert), so:
___1) For the "normal" user: if the file have BIU or 0.00, not update alert.
___2) For the "Alert update disponibility always" user: if the new version is diferent then alert
(For this last user there will be a first time of renewing all the "0.00.sps.version" app files, but he is a advanced user and he can understand it).
.
edited by VVV_Easy_Symenu on 03/02/2018
|
|
|
link
|
|
sl23 Posts: 285
03/02/2018
|
It is useful to have the version number as a tooltip, so when the tooltip shows 0.00, it's not very helpful.
By adding a checkbox to the config form, this would give users control over it.
How about the version file containing text to ignore updates via the sps system?
This would need to be written to the file when the checkbox is ticked.
So the version file could remain as is, without the need to use the 0.00 reference for auto updating apps, but when an app does auto update, the file has something written to it that tells the sps system to ignore it.
As the version files are zero byte files, it should be quick and easy to flag ones that contain a single word as their size is increased.
If a version file is not zero bytes, it is ignored in the update process.
Also keep the current sps form option to control this for base users that don't understand what this is about.
Is that idea any good? If you require further clarification please ask, my explanation may not be too good ;-)
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
05/02/2018
|
Well sl23,
It's a brilliant idea and easy to implement (these are the ideas I like more!). I haven't thought I can use the version file as a DB file even if it's a natural thing to to. And your approach to check only the size could work well if we only need to track the version information.
Anyway a little detail needs a clarification.
You said "when an app does auto update, the file has something written to it...".
The question here is how is SyMenu supposed to be notified about a "private" update just happened? Because I presume SyMenu should be in charge to write something inside the version file after the program updates by itself.
|
|
|
link
|
|
VVV_Easy_Symenu Posts: 159
30/06/2018
|
Continue and explained in the topic:
https://www.ugmfree.it/Forum/messages.aspx?TopicID=691
edited by VVV_Easy_Symenu on 01/08/2018
|
|
|
link
|