You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, projects packaged using nodegui/packer still run the REPL by default when executed with no target script. This is undesirable behaviour, obviously, and the lack of clarity around that behaviour has spawned many issues on the packer project, so there clearly needs to be some way to override that behaviour in the qode executable for packaged applications. Particularly on Windows, the change to the windowing system causes the executable to run the REPL while having no stdio, causing a non-interactive and essentially dead process that must be manually killed.
One method would be to allow for simply catenating a script onto the executable, which could be the entire application script, or simply a loader for some external resources (loose scripts, ASAR archives, whatever the user wants) and having qode automatically execute this script if present, rather than invoking the REPL.
Another approach would be to try creating qode executables integrating the patches from pkg, potentially allowing leveraging pkg to build executables with packaged scripts and resources on top of the Qodejs binary instead of Nodejs. This would have a huge number of other benefits, such as bytecode execution, asset packing, default flags, and so on. Executables built with these patches cannot be easily used for development, however, so separate builds of qode for development and use in packaging would be needed.
The text was updated successfully, but these errors were encountered:
Right now, projects packaged using nodegui/packer still run the REPL by default when executed with no target script. This is undesirable behaviour, obviously, and the lack of clarity around that behaviour has spawned many issues on the packer project, so there clearly needs to be some way to override that behaviour in the qode executable for packaged applications. Particularly on Windows, the change to the windowing system causes the executable to run the REPL while having no stdio, causing a non-interactive and essentially dead process that must be manually killed.
One method would be to allow for simply catenating a script onto the executable, which could be the entire application script, or simply a loader for some external resources (loose scripts, ASAR archives, whatever the user wants) and having qode automatically execute this script if present, rather than invoking the REPL.
Another approach would be to try creating qode executables integrating the patches from pkg, potentially allowing leveraging pkg to build executables with packaged scripts and resources on top of the Qodejs binary instead of Nodejs. This would have a huge number of other benefits, such as bytecode execution, asset packing, default flags, and so on. Executables built with these patches cannot be easily used for development, however, so separate builds of qode for development and use in packaging would be needed.
The text was updated successfully, but these errors were encountered: