Posts by DecSoft

Hello Peter,

Sorry, but I need to ask... what is the problem exactly and what is the expected results? We are talking about fill a Report's Data variable? Are you try to fill it and get some error? There is possible to execute a callback or function after all the queries are executed / returned? If so... maybe it's possible to save the data in certain variable and use it in the "final callback" function. Maybe it's possible to just fill the Report's Data variable "step by step", when the queries finished... I hope that some of these questions can help to finally solve the problem!

Hello Danny,

I am not an expert in the store (now I just develop the apps!), but, what App Builder provides are various BAT files (talking about Windows, also creates SHELL files for Mac OS, to be used in the same way and for the same purpose). These files names are "debug", "run" and "release".

When we execute the "run" BAT file Apache Cordova generates a debug APK of our apps, and, if we have a device connected to our PC (or an iPhone connected to our Mac OS), after the APK for Android (or IPA for iOS) is generated the app is launching in the device.

To do the above we just must connect our device in the computer, if everything is ok (the drivers are ready, etc.) we can use the "run" BAT to compile and launch the app into the device, so this is the best way to debug the app in a real device.

If we have no devices connected and execute the "run" BAT file, Cordova try to launch the device emulator configured in the Android SDK / Android Studio. I told you this is the best way to debug the app... but talking about the device... because normally we can debug the app in a browser, which is more easy and fast. Only when need to try something that only works in a device... we need to test it in the device, of course.

Then we have the "debug" BAT file (or SHELL file). Executing this Cordova prepares a "debug" compilation of our app that we can copy to our device or another, etc. It's the same than "run", except that with the "debug" the app is not launched in any device nor emulator.

Finally we have the "release" BAT file (or their SHELL version for Mac OS), and, when we execute it what Cordova prepares is a release compilation of the app. This generated APK is ready to be uploaded in the Android Store.

In order to get a release, if I am not wrong, we need to sign the APK, so you need to fill the App Options -> Cordova -> Android -> Signing. Once you fill the edit boxes that you can see there, App Builder generates the right JSON file, which Cordova uses to sign our apps.

Probably I miss something that you can be interested in, so, please, go ahead if you have any further question, and, I will try to help you as best as possible.

Hello Danny,

No problem at all! Note anyway that the "CloseWindow" action is intended to be used only if we need to take control of the opened window. In fact, the last argument of the "OpenWindow", give us an identifier that we can use with the "CloseWindow", but for other things too. However, the "CloseAction" window only works in the browsers, not in platforms like Android, iOS, etc.

Hello Danny,

Very good! But take your time if possible! Worries are good for nothing! :-)

Hello Danny,

Yes; remember to try the app in a browser like Firefox, with the developer console opened: unfortunately the AB debugger can't tell us about requests and the possible success or error on them, but the developer console of Firefox, for example, can do it, and, in fact,can tell us lot of other things, so we can use the internal debugger for take a quick look, but, if wanted more information, we need to run the app in a browser like Firefox, and we can do it just by press the right IDE button. So just temember to try the app in that way.

You're welcome, Danny!

Hello Danny,

If you run the app in a browser like Firefox, with the developers console opened, probably you can see what happen. Probably it's a CORS related issue: the server must provide the right CORS permissions that allows the app to reach the JSON file.

You can take a look at this website, since the possible configuration of the server depend on the server itself, it's not the same for all the posible servers.

If you can't configure the server to provide the right CORS permissions, it's probably possible to do it using some "bridge" for the JSON file, so, for example, we can prepare a PHP script, who read the JSON file and serve it to the app: then we can set the CORS permissions in the PHP script.

You can see various examples of setting the CORS permissions from PHP scripts, since are used in various app samples, mostly "Report*" samples. Anyway this is the code that can be used, more or less:

Hello Ryan,

The controls that we have "out of the box" don't support something like that. We can know the "index" and the text of the selected item, so we must do whatever thing with that information. Probably it's possible to create something like that using the HTML Control and the appropriate HTML markup and Javascript code, in a similar way than what is show in this post.

If you want to use the "out of the box" controls, it's up to you what to do, based in the data that you are using. So, once you know the item index or the item text, you can search in certain array or object to match that item and get the rest information about the item that you need.

I am not sure if my explaintaion is very good... so please, go ahead if you have any further question.

Hello Danny,

You are right: I forget that we are talking about a multiselect list... but it's ok, with a bit more work we can get something like that working:

I add a bit more of Javascript and a new "item-selected" CSS class in the app "Inline CSS" option.

Hello Danny,

If I am not wrong the Select control never show a horizontal scroll, and, we can't force it using any CSS style. A possible workaround can be to place the Select inside a Container, made the Select as width as the larger item, and, set the Container's width to what we wanted, and then use the "overflow-x: auto" of the Container. You can see this approach in the below app sample:

Another possible approach is to use a Menu control instead of a Select one, and use the "overflow-x" of the Menu:

Another approach (probably the best to me) can be to use a HTML control, and, use our own HTML markup to show a list of "large items" in a way that don't get out of the screen, so we no need the horozintal scroll at all:

P.S. In this last app sample, you must look at the view Show event, as well the HTML markup placed in the used HTML control.

Glad to know that you got it, Danny!

Mala suerte, entonces: por alguna razón Cordova no soporta esos eventos en iOS... :-(

Hola Jordi,

¿De qué plataforma estamos hablando? Puesto que esos eventos parecen disponibles sólo en Android...

Hello Danny,

If we talk about the "Alert" action there is no problem even if the view changes. Remember than the "Alert" action show a native platform dialog alert, so this action is quite recommendable. However, if we want to use the "AlertBox" action, then we must take in count that when we go to another view, the possible alert is hidden. So the approach must be: 1º Set a flag variable like "ShowAlert" to "true" before we move to another view. 2º Use the another view Show event to look for the flag variable, and, if required, show then yes, use the "AlertBox" action.

So the button which go to another view can look like this:

And therefore in the "View2" Show event we can write this code:

Absolutely right, Danny! That's exactly!