<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>SyMenu - General discussion &amp; questions - Merge / Import - Messages</title>
<link>https://www.ugmfree.it/forum/messages.aspx?TopicID=332</link>
<description>SyMenu - General discussion &amp; questions - Merge / Import - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<pubDate>Thu, 26 Mar 2015 20:06:48 GMT</pubDate>
<lastBuildDate>Thu, 26 Mar 2015 20:06:48 GMT</lastBuildDate>
<item>
<link>https://www.ugmfree.it/forum/messages.aspx?TopicID=332</link>
<title>Message from carloxp</title>
<description><![CDATA[Hi Gianluca<br/><br/>thank you once more for your reply!<br/><br/>I fully understand your point of view. Obviously, your opinion is the opinion of the programmer rather than a mere user.<br/><br/>I would be very happy to further discuss the issue with you by email :-) But more than dicussing the issue I would be very happy to meet you, as I'm a former .NET programmer too! Please, feel free to drop me a row at <i>carloxp (at) gmail.com</i><br/><br/>Cheers,<br/>Carlo]]></description>
<pubDate>Thu, 26 Mar 2015 20:06:48 GMT</pubDate>
</item>
<item>
<link>https://www.ugmfree.it/forum/messages.aspx?TopicID=332</link>
<title>Message from Gianluca</title>
<description><![CDATA[Chiarissimo :-)<br/><br/>Yes your argument are really clear but it is not  completely right. <br/>Importing the xml configuration of one item makes it available inside the item list but  SyMenu always works with a couple of elements: the xml configuration and file system related program. So  an import feature should consider either the elements i.e. it is a really complex feature.<br/><br/>My approach to solve this duality has been to create the SPS format to help thirdy party software producers  too to include their products inside the SyMenu suite. <br/>The SPS is more flexible than an import feature because it could be build with a special tool that helps with the compilation of the file (the SPS builder), it integrates the auto update process (the software producer has only to publish an SPS with a fresh program version and SyMenu notifies the user that the new version is available), it assures that the users don't need to download an entire suite but only the programs they are interested in.<br/><br/>Se hai voglia di approfondire la questione possiamo anche parlarne via mail :-)]]></description>
<pubDate>Thu, 26 Mar 2015 13:01:30 GMT</pubDate>
</item>
<item>
<link>https://www.ugmfree.it/forum/messages.aspx?TopicID=332</link>
<title>Message from carloxp</title>
<description><![CDATA[Hi<br/>thank you for replying<br/><br/>Well, importing every item is useful but, as far as I know, the menu structure is not preserved. I mean: every item goes to the menu's root.<br/>I have a very old NirSoft-SyMenu and it has a well-defined menu structure. Rebuildig it from scratch by using SPS implies to manually rebuild the menu structure.<br/><br/>Thank you for defining <i>interesting</i> my request. But I don't agree that it should be used by few users.<br/>By placing a import/merge feature would make SyMEnu very flexible, because any software developer could publish just a couple of XML rows in order to add his own menu's to an existing instance, rather than publish the whole SyMenu package.<br/>Spero di essere stato chiaro! :-)<br/><br/><i><br/></i><br/><i>edited by carloxp on 26/03/2015</i>]]></description>
<pubDate>Thu, 26 Mar 2015 12:12:54 GMT</pubDate>
</item>
<item>
<link>https://www.ugmfree.it/forum/messages.aspx?TopicID=332</link>
<title>Message from Gianluca</title>
<description><![CDATA[There is not a guided procedure to do what you desire but you have many other options.<br/><br/>1) You can import every items from a different SyMenu instance with the built in command "Batch import" <a href="http://www.ugmfree.it/SyMenuManual.aspx#Item_Manager_menu_batch_import" target="_blank" rel="nofollow">http://www.ugmfree.it/SyMenuManual.aspx#Item_Manager_menu_batch_import</a> .<br/><br/>2) NirSoft software is natively available through the SPS suite feature (http://www.ugmfree.it/SyMenuManual.aspx#SPSForm ) so you can download it inside your main instance.<br/><br/>3) If you are really brave you can merge the configuration of your three instances in a single one. The file containing the item configuration is Config\SyMenuItem.zip. Unzip your files, they are simple xml file, and merge theme in one single file. Maybe you have to move the programs too because the items configuration work with relative paths. Zip it again and run SyMneu. <br/>Watch out. Do a backup before working with the configuration files by hand and don't touch them if you don't know what an xml file is.<br/><br/><br/>Well if someone has free time to dedicate to this topic and an appropriate dev knowledge he can create a plug in to accomplish this interesting task. I exclude to implement it in SyMenu as a native feature because it is a utility poorly useful for the majority of the users.]]></description>
<pubDate>Thu, 26 Mar 2015 11:59:16 GMT</pubDate>
</item>
<item>
<link>https://www.ugmfree.it/forum/messages.aspx?TopicID=332</link>
<title>Message from carloxp</title>
<description><![CDATA[Hi all<br/><br/>I've fond no way to import or merge the menu set from different SyMenu instances.<br/><br/>For example, I have a SyMenu instance/installation with GEGeek_Toolkit commands (hundreds), another with my own items and another with NirSoft menu's.<br/><br/>Is not possible merge all these instances/installations or simply import a complete menu set from anoter instance/installation?<br/><br/>Thank you ;-)]]></description>
<pubDate>Thu, 26 Mar 2015 11:42:40 GMT</pubDate>
</item>
</channel>
</rss>
