Posts by DecSoft

Hola Jordi,

Dándole vueltas a este asunto, nos encontramos, que, añadir un argumento más a la acción que nos ocupa, implica jorobar la compatibilidad hacia atrás. por lo tanto, creo que esta otra solución puede tenerse en cuenta: se trata de usar un Timer, que, se encargue de cerrar el "AlertBox" usando la acción "CloseDialog".

El asunto es sencillo. Primero ejecutamos el siguiente código, asumiendo que tenemos un "Timer1" en la vista que nos interesa:

TimerStart "Timer1" AlertBox "This is a normal AlertBox, with a close button" "primary"

Por su lado, el evento "Interval" del "Timer1" quedaría así:

TimerStop "Timer1" CloseDialog

De este modo, puesto que usamos "AlertBox", tendremos el botón para cerrar disponible, y, por otro lado, el "Timer1" "auto cerrará" la alerta, si el usuario no la cierra antes.

Hola Jordi,

Por favor, prueba el ejemplo "InputsScroll2", y, fíjate en el código que se ejecuta en el evento "Show" de la vista de dicho ejemplo. Dicho código debes ejecutarlo también en tu app, al menos, en la vista en que lo necesites.

Hola Jordi,

Veremos de hacerlo como dices, dando la opción de poner el botón de cerrar o no en el "Alert".

Hola Jordi,

¿Te refieres a algo como lo siguiente?

AlertBox "<i class='fas fa-question-circle'></i> Look at me, I am an AlertBox!" "primary"

Hello Amin,

Thanks for yor kindly words, Amin, Merry Christmas for you too and Happy New Year creating apps with DecSoft App Builder! :-)

Hola Jordi,

La app tiene un evento "Ready", que, equivale al "deviceready" que mencionas. Si no pudieras utilizarlo (en dicho evento pueden no estar disponibles algunos controles, por ejemplo), siempre podrías colocar el código que has mencionado en el evento "Show" de una vista, por ejemplo, entre acciones "StartJS" y "EndJS". En todo caso el evento "deviceready" será ejecutado cuando se espera: una vez Cordova y sus plugins estén disponibles.

Hello Amin,

What about to use the "[App.TextDirection]" variable? Are you tried with that?

SetVar "[App.TextDirection]" "rtl" "String"

Hello Amin,

I am right now working in certain app, and, this forum's thread come to my mind. Certainly, we are talking here about Arrays, and the ability to load and parse variables. But we can't forget the ability to deal with JSON. Deal with JSON can be very useful. Supose the below JSON code inside a "config.json" file:

{ "app_header_fg_color": "#ffffff", "app_header_bg_color": "#88a542" }

We can load that file with an HttpClient control, and, in their Success event, do something like the below:

CopyVar "[AppConfig]" "[ConfigHttpClient.Response]"

After we that, we can access the JSON variables, directly, in this way:

Alert "" "[AppConfig.app_header_fg_color]"

In fact, the usage of the "CopyVar" action is only for our convenience, that is, it's also perfectly possible refer to the above variable, directly, using the HttpClient control's response:

Alert "" "[ConfigHttpClient.Response.app_header_fg_color]"

As you can see, we no need (even when it's possible) to use actions like "ObjectGetProp" here, but we can directly use the JSON object's properties/variables. I hope this can be also useful for you and others too, Amin. :-)

Hello Amin,

We can control that. We can control if the current app's view has been already translated, so, we no need to do it again. We can use variables like "flag" to do that. We can control, for example, if the app's view no need to be translated... because the app's language is already the default one, for example.

Place all the strings in one sole file can be attractive... depend on the app, may this can be enough. However, the ability to divide the strings in various files appear to be more easy later, to deal with every specific file/view. On the other hand, probably we are talking about more stuff...

My idea (and I already try it in one specific app) is to prepare a "languages" directory, which is included enterely from the app's Files Manager (we can refer to entire directories, instead to specify files one by one). Then that "languages" directories can have subdirectories.

The first level can be a subdirectory per app's view. Or may we want to have a "views" as the first subdirectory of "languages", and, inside "views", place more subdirectories: one per app's view. Then every app's view directory can have the INI like files that we need, and maybe other stuff, like possible images (that need to be translated too, etc.).

Maybe the "languages" directory, and the "es", "en", subdirectories, then the "views" subdirectory, then the "main", "options", app's views directories, etc., may appear difficult or complex... but in fact we can follow certain rules in order to maintain all of these stuff controlled.

Anyway, as always, depend on the app... maybe one sole file (like you are thinking) can be perfectly enough.

In fact the "Languages" app sample is very simple... may I have a bit of free time in order to prepare another "Languages2" app sample, which try to put in the practice all that I try to explain above.

Hello Amin,

Remember that we can place in the INI like files not only "entire variables", but, also control's variables, so we can perfectly define variables in this way:

MyVar=Here a normal var MyArray=|Here|Is|An|Array|var MyButton1.Text=Here is the text of a button MyButton1.Placeholder=Here is the place holder of a button

When you load and parse that file (depending if you use LoadVariables or ParseVariables), and once loaded or parsed, we get the variable, the Array, but also the "MyButton1" text, placehoder, etc.

And yes; it's possible to place comments in that files, Amin: just start the commented line by a semicolon, for example:

MyVar=Here a normal var MyArray=|Here|Is|An|Array|var MyButton1.Text=Here is the text of a button MyButton1.Placeholder=Here is the place holder of a button ;This is a commented line, which is ignore when load and parse it

Probably can be a good idea to divide the files at least in app's views, so, we can look for the appropriate "translate view file" automagically using some variable like "[App.CurrentView]". Anyway, as here if you have any further question, Amin.

Hello Amin,

Certainlty, there is no way to use an action like you wanted above. :-( On the other hand, "LoadVariables" and "ParseVariables" support Arrays. So we can define an Array variable inside an INI file like, and then use it with LoadVariables or ParseVariables. Something that may you also can consider is to use Javascript. As you already know, we can use Javascript code anytime, for example, to set certain Array variable: that variable is then accesible from both Javascript and AB code. Please, go ahead if you have any further question, Amin.

Hello Amin,

Before enter in the Array question, can I ask if you already try the Languages sample app? Certainly, in order to translate apps, probably one of the best possible ways is to use the LoadVariables and/or the ParseVariables action. Please, take a look at the Languages sample, made your own test. That sample uses LoadVariables, but, is perfectly possible to use an HTTP Client and the ParseVariables with their response. We can directly set languages/variables for the controls, and, also, these actions support Arrays too.

Hello to all,

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

2018.135 (12/16/2018) * Avoid the Javascript error which is produced if a control do not exists in the app and we try to use the actions Show, Hide, Toggle, Enable and Disable. * Fix a mistake in the updater feed archive which cause that App Builder cannot inform to the user if a new release of the program is available.

Read the entire product's history

Hello to all,

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

2018.134 (14/12/2018) * The Focus and the Blur actions check now if the element which we want to give the focus really exists in the document DOM, avoiding an error if that element do not exists.

Read the entire product's history

Hello Adrian,

The input date is a bit particular. Certainly, we can do what you wanted, just with a code like the below one:

NewDate "[DateInput.Value]" "" "[Date]" DateSet "[Date]" "year" "2018" // Month value must be 0 to 11 DateSet "[Date]" "month" "11" DateSet "[Date]" "date" "14" DateToJSDate "[Date]" "[DateInput.Value]"

The above code set the date of a date input to 2018-12-14, tomorrow at this time. You can take a look at the "DateInput" sample. Also take a look at the "DateTime" sample.

Not only me (the Mozilla documentation refer it too) prefer to use something like the "DateInput" sample, that is, provide three Select controls for years, months and days, instead of deal with the date input particularities.