Posts by DecSoft

Hello Asley,

I am not completely sure if you can create a directoy in the place that you wanted, but anyway, you must use the Cordova Files plugin, that is, the Javascript API that such plugin offers. Please, read all the documentation, and, in particular (but not only) the last topic: Create directories. Post here if you have any specific problem!

Hello Amin,

You are right, methods like "prepareInterstitial" can be good. In fact the AdMob Javascript plugin uses it... but also uses their argument "autoShow" set to true, which causes that the interstitial appear right after their preparation.

Taking a look at the AdMob plugin API, the API appear very, very easy to use.

So, maybe I can enhance the AdMob Javascript plugin in the near future, but, for now, you must use the AdMob API directly, Amin. My recommendation is that you forget the AdMob Javascript plugin complete, just follow and use the AdMob plugin API.

Then please... post here any problem that you can have and I will try to help you.

Hello Amin,

We need to touch various things here. First of all, AB actions are finally translated to the right Javascript code, so, there must no difference between use AB actions and Javascript, since at the end we are talking about Javascript code.

What I am thinking is that the AdMob plugin relies in Internet to work... that is, probably to show an ad one or more HTTP requests are required, so maybe the quality of the internet connection matter here. Maybe the second show is faster?

Are you try with the AdMob app sample? Can you see the same "slow" behaviour? When I try this sample in the past (not too much time ago) I can't note any "slow" behaviour... both "banners" and "interstitials" appaer reasonably well.

Hello Harald,

Yes; please,take a look at the "Device" app sample. Look at the Menu -> File -> Samples and search for "Device".

Hello Peter,

Certainly, the DateInput2 appear to have a problem with Chrome: it's related with the icon used in the button that shown the date picker, that is, if you replace the icon by text, or add some text aside the icon, you can see that the Date picker works as expected also in Chrome.

On the other hand, I think the Date Input can be considered, since don't require anything else than place a Date Input in the view, and, works well (in my opinion) in all the modern browsers, and, perfectly well (again in my opinion) in platforms like Android and iOS.

Hello Peter,

Certainly a Timer picker exists in the UI boostrap framework: you can try to implement it, and, post here if you have any question or problem. However, a time picker can be as simple to use a couple of Input or Select controls, to allows the user to choose the hour and minute.

P.S. Take also a look at the Date Input control. Can be a good replacement for the Date picker too.

Hello Asley,

You have a good signature. :-) Now you can think in change your Gravatar. :-) Anyway, please, upgrade your AB copy and take a look at the new ExternalFonts app sample.

Hello Peter,

Please, upgrade your AB copy and take a look at the new DateInput2 app sample, which show how we can use the DatePicker control from the ui-bootstrap 4 framework.

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 to all,

Here is a new DecSoft App Builder release, 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 Harald,

Humm... in fact, what the OpenWindow is translated to Javascript we use "no" for the location bar, and not the empty string that we pass as an argument of the OpenWindow action...

About the Javascript usage, certainly is good! We can (and sometimes it's quite good) use pure HTML pieces, CSS style and Javascript code in any place without any problem. :-)

Hello Harald,

Certainly, maybe "presentationstyle" do the job... but apparently is not required in Android 6.0.1. The point, on the other hand, is that probably the "slow behaviour" that you note, is related with the options... maybe with "presentationstyle", and why? Because in fact the "OpenWindow" action become to the same Javascript code to be executed.

In my opinion, maybe you need to use the Javascript code that works in Android 5.0, since probably works like expected in later versions. Remember that is perfectly possible to use Javascript code in our apps, for example, we can see that the InAppBrowser plugin have several options, beyond than what the OpenWindow action offers, so, we can use that Javascript directly if we see it useful.

Hello Harald,

The location argument works here in Android 6.0.1 like expected... what version of Android are you testing?

Hello Harald,

Thanks! Works like a charm :-)

You're welcome! :-)