External JS Files and Web Extensions

Create multiplatform apps with DecSoft App Builder, including Android and iOS with the same base of code.

DecSoft App Builder integrates an Open AI assistant in order to assist you while developing your apps.

Create apps and expand their capabilities by using the world's popular programming language: Javascript.

Take a look at some frequently asked questions about us and our products!

DecSoft App Builder include a convenient Command Line Compiler, so you can compile your apps from the console.

Create modern HTML apps and games at another level making things impossible to do even by modern HTML apps and games.

Save time, resources and money creating apps for Android, iOS and more with the same base of code.

Design for small screen devices but deploy also (without changes) in larger devices like tablets.

Save money by purchasing our NeoPlugins bundles. Five, Ten and even the complete NeoPlugins collection at an incredible price!

DecSoft NeoPlugins are available in both runtime and designtime flavours to keep your apps as small as possible.

DecSoft HTML Compiler is easy to use: set your project's options and compile your apps and games in a nutshell.

Apache Cordova's official plugins are supported out of the box and there are hundreds of plugins ready to use.

Compile, convert your modern HTML apps and games into Microsoft Windows executable programs without dependencies.

DecSoft NeoPlugins put your VisualNeo projects into another level with +1,000 new actions for your apps.

DecSoft HTML Compiler include a convenient Command Line Compiler, so you can compile your apps from the console.

Take a look at our YouTube channel and subscribe to be notified about new videos!

John Clarke

I have an external JS file that contains some object orientated style Javascript code. This has been set up in the File Manager. In my code on the WebExtBackground I want to be able to use the code from the external JS file and say

pageObjectsFactoryObj = new PageObjectsFactory();

However, I get a Javascript Error. If I use the same create object code on the WebExtMessage I get no errors.

I would appreciate all advice offered regarding this

DecSoft

Hello John,

The problem is that the app Files Manager are only prepared to include scripts to be available in the app context, not in the background nor the content context of a Web Extension. The "WebExtMessage" app's event is running from the app context, so, certainly it's possible to use the script's stuff there. Please, upgrade your AB copy: I prepare the app Files Manager and the File Picker dialog in order to allow to check scripts to be included "as content script" and / or "as background script", so that scripts are copied and linked in the Web Extension manifest file. I hope this can help you.

Purchase one or more licenses of our products if they are useful to you!

John Clarke

That is absolutely fantastic. Thanks for this new feature.

DecSoft

Hello John,

That is absolutely fantastic. Thanks for this new feature.

Glad to know that can be useful to you! ;-)

Purchase one or more licenses of our products if they are useful to you!

John Clarke

I think I have found an issue. An external JS file's functionality could be used in a view, in a background script, in a content script or in all 3. Currently if I leave Is Content as false my views show functionality can use the JS File but the WebExtContent cannot. And if I set Is Content to True the WebExcontent can use the JS File but now the view cannot. How can this be solved ?

DecSoft

Hello John,

Let me to think about. The objective was to maintain the backward compability, so, by default the "Is Content" and "Is background" checkboxes are unchecked, means the script that we add (or we already add in the past) are used by the app context, and not by the Web Extension context.

What do you want to share between the app context and the Web Extension content context and Web Extension background context? Remember that we are talking about different contexts, so, I am not sure if we can really use the same stuff in all contexts.

In fact, I am not sure if we really can do it... let me to explain. Supose you have a script which is used by the app context. That stuff is linked in the app's HTML, in order to be available in the app context, but, this stuff is not available in the Web Extension context, and cannot be available...

At least cannot be available "as is"... supose you place a global variable in the app's script, then you cannot use that global variable in the Web Extension context... because we are talking about the same script, but, the script is not shared between the different contexts, so possible changes in the variable in one context, are not available in other context.

If what you wanted is to use some JavaScript object definition, in order to be available in all the contexts, then, a possible solution right now can be to duplicate the script, that is, you can prepare two "script1.js" and "script2.js", with the same JavaScript object definition, so you can use the app's File Manager and add the two scripts, one for the app context, and the other for the Web Extension content and / or background context.

Remember the ability to share stuff between the app and the Web Extension contexts using messages: this is the way that we must use in order to communicate some possible variables values, etc. Adding the same script in the app and the Web Extension contexts cannot avoid the requirement to use messages in order to communicate the different contexts that we are talking about.

Please, post here if you have any question or want to comment something about, John.

Purchase one or more licenses of our products if they are useful to you!

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.