ero35 Posts: 11
6 days ago
|
1-ready packages can be created. Example simple, normal, advanced etc...
2-it would be good if the description part could be translated into a language.
3-symenu folder can be simpler, just like a launcher (App,Data SyMnu exe)
|
|
link
|
Gianluca Administrator Posts: 1280
6 days ago
|
What??
Please, can you explain a bit better what you are speaking for? Give a context at least because I can not even understand if it's a suggestion, a question, or whatever. Thank you.
|
|
link
|
ero35 Posts: 11
6 days ago
|
ero35 wrote:
1-ready packages can be created. Example simple, normal, advanced etc...
2-it would be good if the description part could be translated into a language.
3-symenu folder can be simpler, just like a launcher (App,Data SyMnu exe) " border="0"> " border="0">
|
|
link
|
Gianluca Administrator Posts: 1280
6 days ago
|
Ok the third one is clear now.
Unfortunately, with the technology I'm using to develop SyMenu, it is not possible to move all the files except SyMenu.exe in a subfolder. Indeed SyMenu.exe is not really a win32 executable but it's a .NET Core IL file. .NET Core needs to have all the files you are seeing to execute it.
Well I could move the files README.LICENSE.TXT and README.PRIVACY.TXT in a subfolder but IMO it won't be a big improvement.
To make a comparison try to download Paint.NET that is developed with the same technology as SyMenu and see what .NET Core really would expect to find on the root folder. In SyMenu I succeeded to move practically everything in the subfolder Lib but to do that I had to rewrite the mapping files SyMenu.Admin.deps.json and SyMenu.deps.json and it was a big thing, so much so, Paint.NET author choose to not do that.
|
|
+1
link
|
ero35 Posts: 11
5 days ago
|
Example from liberkey " border="0">
|
|
link
|
Gianluca Administrator Posts: 1280
5 days ago
|
Ok now I understand the 1) too.
Yes, it was a thing I was working on a while ago. My intention wasn't exactly to create a package for newbies and one for experterts but to create thematic packages. For example a package for musicians, one for the students, one for video gamers.
Further my idea was to offer the opportunity to create these kinds of packages directly to the users. So if a user builds an interesting package for a designer he could have shared it with the community.
Unfortunately, the effort to create this kind structure is too much.
If you follow this community or at least read the forum you know for sure that I'm maintaining the project and not much more because the return I got from SyMenu in terms of money, satisfaction, and gratitude has been too little to justify this kind of work and dedication on my part. Sorry for this.
|
|
+1
link
|
ero35 Posts: 11
5 days ago
|
Paint.NET 5.1.1 (x64)
https://disk.yandex.com.tr/d/oDVl82SSzM-8XA
|
|
link
|
Gianluca Administrator Posts: 1280
5 days ago
|
I know it's possible.
The PAF launcher or the FCPortable launcher you used for Paint.NET, are often used to convert non-portable programs to portable. SyMenu is already portable so the only reason to use a launcher like those is to have no other files on the root. It's the classical killing of a fly with a cannon. If I do that, I would use something different, a more lightweight solution as an executable with a SyMenu icon and some information details on it with the only task to execute the real SyMenu.exe inside a subfolder.
It should be a solution but there are some drawbacks: - SyMenu already has a deep folder structure... Some programs, for example Calibre, suffer from this depth and sometimes they don't work at all. Creating another folder level is not so wise; - I want some files to stay in the root. The license and privacy files must always be visible to the users; - the SyMenu autoupdate process has to be rewritten because I could have needed to update the launcher too. It's not a big task but it's another task; - but, above all, as I told you, I'm not willing to use my time for hardly useful tasks in this project, because the project is in maintenance mode. Not dead but almost.
|
|
+1
link
|