Exe compile
Quote from CDY@44 on December 29, 2021, 12:57 amHi @luishp,
I just wanted to know why there is the possibility to compile the apps in Windows *.exe.
It doesn't seem to work anymore or I'm wrong.
Best regards,
Hi @luishp,
I just wanted to know why there is the possibility to compile the apps in Windows *.exe.
It doesn't seem to work anymore or I'm wrong.
Best regards,
Quote from luishp on December 29, 2021, 8:05 am@cdy44-2 you are totally right. I have just disable that possibility and also the Chrome App option as it doesn't exists anymore.
Anyway the Desktop properties options are still present as they are used by NWjs (the tab is now the last one instead of the first one)Thank you!
@cdy44-2 you are totally right. I have just disable that possibility and also the Chrome App option as it doesn't exists anymore.
Anyway the Desktop properties options are still present as they are used by NWjs (the tab is now the last one instead of the first one)
Thank you!
Quote from PaulJonestindall on December 31, 2021, 5:14 pmIs there a reason for disabling this option? As I'm new to the Web version, it seems this feature could have definite possibilities when used along with the Win version. Were there issues with the EXEs?
Is there a reason for disabling this option? As I'm new to the Web version, it seems this feature could have definite possibilities when used along with the Win version. Were there issues with the EXEs?
Quote from Neal Stone on December 31, 2021, 10:52 pm@pauljonestindall one of the issues I have seen is some of the visual plugins didn't always work correctly or at all. However, even with compile to EXE disabled you can still make desktop apps using neoEdge or NW.js. Both work extremely well and in fact run a lot smoother and the visual plugins work great. At first I wasn't happy about compile to EXE being disabled, but now using neoEdge and NW.js, I no longer miss it and love how well it works compared to EXE compiling.
NW.js allows running on Windows, Mac and Linux.
@pauljonestindall one of the issues I have seen is some of the visual plugins didn't always work correctly or at all. However, even with compile to EXE disabled you can still make desktop apps using neoEdge or NW.js. Both work extremely well and in fact run a lot smoother and the visual plugins work great. At first I wasn't happy about compile to EXE being disabled, but now using neoEdge and NW.js, I no longer miss it and love how well it works compared to EXE compiling.
NW.js allows running on Windows, Mac and Linux.
Quote from fkapnist on July 27, 2022, 6:41 amQuote from Neal Stone on December 31, 2021, 10:52 pm@pauljonestindall one of the issues I have seen is some of the visual plugins didn't always work correctly or at all. However, even with compile to EXE disabled you can still make desktop apps using neoEdge or NW.js. Both work extremely well and in fact run a lot smoother and the visual plugins work great. At first I wasn't happy about compile to EXE being disabled, but now using neoEdge and NW.js, I no longer miss it and love how well it works compared to EXE compiling.
NW.js allows running on Windows, Mac and Linux.
I think VisualNEO should have kept the "compile to EXE" feature, while introducing neoEdge and NW.js as optional improvements. It is not wise to cripple software that people were already used to. If the compiled EXE didn't always work, that is for each programmer, not for VisualNEO, to decide. Distributing neoEdge and NW.js folders and packages is not so easy... It now requires a third-party utility to create self-extracting EXE files, yet VisualNEO was able to do just that..
Quote from Neal Stone on December 31, 2021, 10:52 pm@pauljonestindall one of the issues I have seen is some of the visual plugins didn't always work correctly or at all. However, even with compile to EXE disabled you can still make desktop apps using neoEdge or NW.js. Both work extremely well and in fact run a lot smoother and the visual plugins work great. At first I wasn't happy about compile to EXE being disabled, but now using neoEdge and NW.js, I no longer miss it and love how well it works compared to EXE compiling.
NW.js allows running on Windows, Mac and Linux.
I think VisualNEO should have kept the "compile to EXE" feature, while introducing neoEdge and NW.js as optional improvements. It is not wise to cripple software that people were already used to. If the compiled EXE didn't always work, that is for each programmer, not for VisualNEO, to decide. Distributing neoEdge and NW.js folders and packages is not so easy... It now requires a third-party utility to create self-extracting EXE files, yet VisualNEO was able to do just that..
Quote from luishp on July 28, 2022, 7:41 amI think VisualNEO should have kept the "compile to EXE" feature, while introducing neoEdge and NW.js as optional improvements.
@fkapnist You are right. The problem is it didn't work anymore. I disabled it after it stoped working.
I did a great effort to offer a free solution using neoEdge. I think it's really easy to use and distribute. And also quite more powerful as it allows bidirectional communications and even calling VisualNEO Win commands from VisualNEO Web.
Anyway I'm not happy either with having to disable the "compile to EXE" option.Regards
I think VisualNEO should have kept the "compile to EXE" feature, while introducing neoEdge and NW.js as optional improvements.
@fkapnist You are right. The problem is it didn't work anymore. I disabled it after it stoped working.
I did a great effort to offer a free solution using neoEdge. I think it's really easy to use and distribute. And also quite more powerful as it allows bidirectional communications and even calling VisualNEO Win commands from VisualNEO Web.
Anyway I'm not happy either with having to disable the "compile to EXE" option.
Regards
Quote from fkapnist on July 28, 2022, 9:11 amIt won't fix itself. You'll have to do that, once you set your mind to it. For example, Ask DecSoft to remove "compile to EXE" from their Windows software. See what they have to say... Meanwhile the bugs of Internet Explorer set my project back by a decade. That is a very long time. It is scary indeed but I won't give up !! neoEdge is quite good, you just have to find a way to compile it all into a self-extracting EXE. Good luck!
It won't fix itself. You'll have to do that, once you set your mind to it. For example, Ask DecSoft to remove "compile to EXE" from their Windows software. See what they have to say... Meanwhile the bugs of Internet Explorer set my project back by a decade. That is a very long time. It is scary indeed but I won't give up !! neoEdge is quite good, you just have to find a way to compile it all into a self-extracting EXE. Good luck!
Quote from fkapnist on July 28, 2022, 4:08 pmQuote from luishp on July 28, 2022, 7:41 amI think VisualNEO should have kept the "compile to EXE" feature, while introducing neoEdge and NW.js as optional improvements.
@fkapnist You are right. The problem is it didn't work anymore. I disabled it after it stoped working.
I did a great effort to offer a free solution using neoEdge. I think it's really easy to use and distribute. And also quite more powerful as it allows bidirectional communications and even calling VisualNEO Win commands from VisualNEO Web.
Anyway I'm not happy either with having to disable the "compile to EXE" option.Regards
But you already have a pub script for VisualNEO Win that creates LAUNCHER.EXE from VisualNEOWeb files by compressing app folders into a zip and adding neoEdge.exe, package.json, and WebView2Loader.dll into the same zip. (After compilation Launcher.exe is then renamed to whatever your new app name is.)
:start .unzip files in the temp directory you choose or TempDir by default SetObjectCaption "launchertext" "Start extracting..." UnZipToFiles "[Embedded]data.zip" "[TempDir]" "*.*" "" "" "[ZipResult]" If "[ZipResult]" "=" "1" SetObjectCaption "launchertext" "Extract ok" Run "[TempDir]NeoEdge.exe" "" "RunOnce+LoadComplete" "" "" SetObjectCaption "launchertext" "Exit" Exit "" "" Else AlertBox "Error" "Error extracting" Endif ReturnIf " [ Embedded ] data . zip " is replaced in the above script with a non-embedded, predetermined zip name and location containing the new VisualNEOWeb app files, you can create a small program that compiles into EXE without the user having to buy the entire VisualNEO Win package. All the user has to do is first create the appropriate zip containg the app folders and make sure it is in the correct location with the expected file name. Then compile to EXE.
That's just a rough idea of course. There are other, and perhaps easier, ways to compile zip files into EXE. But they will have to pass the antivirus tests...
https://visualneo.com/forum/topic/extracting-embedded-files
.
Quote from luishp on July 28, 2022, 7:41 amI think VisualNEO should have kept the "compile to EXE" feature, while introducing neoEdge and NW.js as optional improvements.
@fkapnist You are right. The problem is it didn't work anymore. I disabled it after it stoped working.
I did a great effort to offer a free solution using neoEdge. I think it's really easy to use and distribute. And also quite more powerful as it allows bidirectional communications and even calling VisualNEO Win commands from VisualNEO Web.
Anyway I'm not happy either with having to disable the "compile to EXE" option.Regards
But you already have a pub script for VisualNEO Win that creates LAUNCHER.EXE from VisualNEOWeb files by compressing app folders into a zip and adding neoEdge.exe, package.json, and WebView2Loader.dll into the same zip. (After compilation Launcher.exe is then renamed to whatever your new app name is.)
:start .unzip files in the temp directory you choose or TempDir by default SetObjectCaption "launchertext" "Start extracting..." UnZipToFiles "[Embedded]data.zip" "[TempDir]" "*.*" "" "" "[ZipResult]" If "[ZipResult]" "=" "1" SetObjectCaption "launchertext" "Extract ok" Run "[TempDir]NeoEdge.exe" "" "RunOnce+LoadComplete" "" "" SetObjectCaption "launchertext" "Exit" Exit "" "" Else AlertBox "Error" "Error extracting" Endif Return
If " [ Embedded ] data . zip " is replaced in the above script with a non-embedded, predetermined zip name and location containing the new VisualNEOWeb app files, you can create a small program that compiles into EXE without the user having to buy the entire VisualNEO Win package. All the user has to do is first create the appropriate zip containg the app folders and make sure it is in the correct location with the expected file name. Then compile to EXE.
That's just a rough idea of course. There are other, and perhaps easier, ways to compile zip files into EXE. But they will have to pass the antivirus tests...
https://visualneo.com/forum/topic/extracting-embedded-files
.