You can take a look at various Report* samples... who use variables in various ways inside the Report HTML, in a similar way than the HTML control. There are various Report* samples, as you know: probably you can learn something good (related with this thread) from some of them.
I forget to mention something... certainly I expect that the SHELL files works as expected right now, however, I only prepare the signing stuff for the Microsoft Windows platform. This means that right now we can sign our apps in Microsoft Windows, but can't sign our apps in Mac OS... except if we prepare the right "build.json" file by ourself. I expect to add support to the Mac OS signing in the next App Builder release. For the possible case of GNU/Linux, apparently there is no signing stuff required.
Yes, I agree; the Cordova's Electron appear a very interesting platform. Create native executables (and even an installer) for our apps it's very, very easy in Microsoft Windows., as we can see in the below video:
Talking about Mac OS,... are you tried the very latest release of AB? Because now we also generates SHELL files for Electron... similar than the SHELL files that we already generates for iOS. These SHELL files are intended to be used in Mac OS, and, for the Electron case, maybe also to be used in GNU/Linux, since Electron is also supported in this operating system.
I did not test the Electron SHELL files yet, however, but, in principle, they must work as expected. About the permissions... take a look at the generated SHELL files,... you can see a comment line like the below one:
I take exactly the same way than the SHELL files generated for the iOS platform, since they works like a charm here in Mac OS. When possible I want to test the new generated Electron SHELL files, in order to see if work like expected too.
The below video shown how easy is to create installers and executables for Microsoft Windows from our App Builder apps, using the recently added Apache Cordova's Electron platform. Enjoy it!
Then it's a bad thing... because the objective must be to no need to touch or take care about any file... I have no time right now in order to try it, Harald. Maybe I can do it in the future... because it's quite are... certainly, if an script refers to an specific file location... the questions must be why that specific location is used... and if we can do the job in other way, maybe moving that "require" to other file... maybe edit the script to refer to our file location...
I hope at least that, if there is not another way, you can get it working with not too much efforts...
What if you change the "navigator.serviceWorker.register('service-worker.js')" for the right app's path? This means that, at least, you only need to touch that line of code?
I know this is an old thread, however, maybe this new release of App Builder can be of your interest, since we introduce the support for the recently added Apache Cordova's Electron platform. By now, with this new Cordova's platform, we can create Windows' native executables and installers for our apps.
If I am not wrong... we can use relative paths... so if our scripts are placed in "www/app/scripts", maybe we can use something like this:
Note that the above is correct if the script is placed in "www/app/scripts"... in other words, if you place the above code inside the "app.js" (in the app's Ready event, or a view's Show event), when maybe you can use the URLs like before... not in a relative way than the above.
Try it, Harald, if you can do it, then you no need to place files in specific directories, etc.
Yes; certainly the scripts are copied into the app's files folder... however, what we need to put that script in the "www" folder? Is there any reason? Of course, I mention this, because, in principle, I can't see a reason to need to copy an script in an specific folder... if the script is linked... then we can use their stuff... or I am missing something...
Everybody can read the DecSoft support forum for learning purposes, however only DecSoft customers can post new threads. Purchase one or more licenses of some DecSoft products in order to give this and other benefits.
This website uses cookies only to store your preferences.