|
sl23 Posts: 285
10/06/2017
|
Due to having more than one installation of SyMenu, I find it sometimes necessary to copy/move from one to another. It would be of great help to avoid having to redownload then move settings or copy the apps folder and edit config. My proposal is to simply have SyMenu auto detect if apps have been added to any of it's folders and add the entry(ies) to the menu uncategorised.
I have to admit, this is one feature I do like about PA.com menu. It makes reorganisation or even creating new menus for others a breeze. You can just copy your existing app folders to the new menu and PA.com menu just knows they're there and are therefore available within. No Config necessary, other than renaming or recategorising if desired.
Thanks
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
15/06/2017
|
sl23 wrote:
Due to having more than one installation of SyMenu, I find it sometimes necessary to copy/move from one to another.
You already have something similar. It's the Batch import feature.
You can even use it to import SPS Suite programs from one SyMenu to another. Well, in this case you have to follow a particular procedure but it's a feasible task.
Example. I have two SyMenu installation, Sy1 and Sy2, and you want to copy three SPS program from Sy1 (source) to Sy2 (target).
- copy the three programs from Sy1 to Sy2 keeping each relative paths
- batch import in Sy2
- select the three new executables and import them
- save and exit from configuration form
- now go to the Sy2 SPS Manager and you'll find your new programs
Disadvantages:
- you don't have metadata in your SyMenu logical items even if the description fields will be restored during the first update.
- if you visit the Sy2 SPS Manager before importing, the new programs will be moved to trash.
sl23 wrote:
this is one feature I do like about PA.com menu. It makes reorganisation or even creating new menus for others a breeze.
It's easy for PA.com creates such a feature. Consider that they work only with PAF programs and the PAF programs have predictable folder structures and file names. So if the PA.com menu finds something like xyzPortable.exe that is a good item to import. Further they don't need to scan more than a first folder level because the xyzPortable.exe are all located on their own root.
As an SPS editor, you know better than me how complex and various the normal program structures are.
The only organic solution I see, is to create a plugin that works this way:
- it reads the configuration from Sy1
- it presents the full program list from Sy1 to the user
- the user selects the programs he wants to export
- the plugin now copies the selected program folders and files to the Sy2 paths
- the plugin inserts in the Sy2 configuration the xml for every exported Sy1 program
- naturally Sy2 must be closed.
It's not a complex plugin but it's a big work, and I can't face such a job. This is the reason for which I'm speaking of a plugin and not about a new native implementation. Even better than a plugin should be a separate program like SyMenu Orphan Icons Cleaner or SyMenu Published App Track (from our mighty VVV_Easy_Symenu).
If someone would like to try that, let me know.
|
|
|
link
|
|
lupusbalo Posts: 77
16/06/2017
|
@sl23
I work on several PC where Symenu is "installed"
"Master" is my personal PC
I just sync all of them the following way:
- I use FreefileSync to synchronize "Master" with a 3.0 USB mem stick
- then re-sync it on other PCs as necessary (could be autoexecuted)
and it's fairly quick and easy (only new or more recent files copied)
up to now, found no drawbacks
but I'm sure don't understand your problem!!
edited by lupusbalo on 16/06/2017
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
16/06/2017
|
sl23 is trying to do something more subtle.
His problem is not solved simply sincronizing two (or more) SyMenu installation but using a part of the master installation to create the same configuration on the target installation. His purpose is not having exactly equal SyMenu installations, but higly customized versions with some parts in common.
|
|
|
link
|
|
lupusbalo Posts: 77
17/06/2017
|
OK, understood
I use machine-personnalized sync with exclusions!
this is what I do for some Files / folders
- Symenu config itself
- mainly data profiles for apps parameters specific for a PC (example Sync parm obviously)
- applis that I don't want
that doesn't solve everything but provide a good workaround
|
|
|
link
|
|
sl23 Posts: 285
17/06/2017
|
Gianluca wrote:
sl23 is trying to do something more subtle.
His problem is not solved simply sincronizing two (or more) SyMenu installation but using a part of the master installation to create the same configuration on the target installation. His purpose is not having exactly equal SyMenu installations, but higly customized versions with some parts in common.
YESSS < Oh Mighty Evil one! 
Sorry couldn't resist that! Seeing as you got the magic 666 posts!
A much better explanation than my own, thank you.
And thank you to you too lupusbalo for your help, but not really what I'm looking for.
I have to admit I didn't think about the different folder structures causing an issue. As it's going to cause you too much work then don't worry about it. I assumed it would be a matter of simply doing a recheck as it is when checking for redundant links.
Never mind, thanks for the explanation.
|
|
|
link
|
|
Gianluca Administrator Posts: 1274
19/06/2017
|
Wow. I didn't notice the 666 post. It has a particular meaning to me: I write too many messages in this forum 
|
|
|
link
|
|
sl23 Posts: 285
19/06/2017
|
Lol think we all write too many messages! I wonder how many users have social media accounts!
|
|
|
link
|