Posts by DecSoft

Hello John,

I think you have two possibilities, well,... three... if you count to place the function in the Show event, or the app DomReady event. You can also place the function as an app's function, using the app's Functions Manager, then you can use the function's body that you show "as is". And you can also place the function in an external JavaScript file, however, in this case you must use the function's return / result, that is, your code must be something like this:

There is another additionally possibility, John, using some app's internal methods like "app._getCurrentView()", since we have a "window.app" variable that we can use, however, probably the possibilities mentioned above are more recommended. For example, just use the external JavaScript function's return / result can be enough, so we no need to deal with app's internal methods, which maybe can change in the future, etc.

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

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.

Hello John,

That is absolutely fantastic. Thanks for this new feature.

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

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.

Hola Jordi,

Ojo, que, el anterior código no funcionará el Internet Explorer 11 (en que se basa el depurador de la anterior generación de App Builder)... tendrás que probarlo en Firefox u otros navegadores.

Hola Jordi,

No sé si algo como lo siguiente podría servirte:

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

Hello to all,

Here is a new DecSoft App Builder release, with the below changes, fixes and enhancements:

Read the entire product's history

Hello Amin,

Thanks for your answer. You are right, the ModifiedDate entry in the XML can cause some non desired issues, and, since it's not really used... I will to remove it from the XML in both the previous generation of AB and the current generation of the product too. I will change this and prepare new releases of the products to fix the possible issue with version control programs.

Update: It's done. Both the previous generation and the current generation of AB has been upgraded in order to avoid the "ModifiedDate" entry in the project's XML file. I hope this can help in order to use version control programs with AB. Thanks Amin for the suggestion.

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

Hello Paolo,

Certainly, it's a question beyond HTML / JavaScript, so, we must deal with something like that using some Apache Cordova plugin: something like this one. The problem can be to find a plugin which works in both platforms iOS and Android... the linked one works for Android and Mac OS, but, not for iOS... but for sure you must try to find an Apache Cordova plugin in order to give something like that working, Paolo.

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

Hola Jordi,

¿Estás seguro de eso? Yo estoy pensando en algunos entornos como Delphi, y, la fecha de un control Date es la actual... cuando sitúas el control en el formulario, pero, no estoy seguro de que siempre sea la fecha actual... en todo caso, yo creo que no cabe discusión, Jordi: se trata de ejecutar las dos líneas de código de arriba para poner la fecha actual, si así lo quieres, o cualquier otra fecha. Poner la fecha actual "siempre"... me suena a "forzar" dicha fecha actual... no sé... es posible... pero no lo veo tan claro, y, teniendo en cuenta que hablamos de un par de líneas de código para poner la fecha actual, pues...