Posts by DecSoft

  • d
  • h
  • m
  • s
Show threads by DecSoft
3355 posts found, page 102 of 224

DecSoft (In thread: New MegaPack 2019.2)

You're welcome, Eric! Always thanks you for your support and thanks for your kindly words too. :-)


DecSoft (In thread: New MegaPack 2019.2)

Hello to all,

Here is a new DecSoft NeoPlugins Mega Pack release, with the below changes, fixes and enhancements:

Get more information and download individual NeoPlugins and the NeoPlugins Mega Pack from here.


DecSoft (In thread: Como pasar un valor por URL a AppBuilder)

Hola Jordi,

Echa un vistazo al apartado "App views URLs" de la ayuda:

Supose your app is placed in the below URL:

http://www.yourdomain.com/app/#!/View1

Additionally, you can use an URL like the below one:

http://www.yourdomain.com/app/#!/View1/a=1&b=2

The above URL provide to the View1 the "a" and "b" params. These params can be accessed using the Params variable in this way: [View1.Params.a] and [View1.Params.b].

Revisa también el ejemplo "ViewParams" que se incluye con AB.


DecSoft (In thread: Change the default / first view at runtime)

Hello Amin,

Thanks for your kindly words! :-)


DecSoft (In thread: Change the default / first view at runtime)

Hello Amin,

Please, upgrade your AB copy to the latest release. Take a look at the changes. With the new release of AB and their new stuff, it's possible to determine the default app's view at runtime. Take a look at the new "StartEvent" sample and tell me what do you think about. I hope that the new AB stuff can be useful for you and other customers too. :-)


DecSoft (In thread: New App Builder release 2019.13 (02/06/2019))

Hello to all,

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

Read the entire product's history


DecSoft (In thread: Change the default / first view at runtime)

Hello Amin,

NO problem. I am happy to help when possible. :-)


DecSoft (In thread: Change the default / first view at runtime)

Hello Amin,

I try some things here but without lucky yet. Just to remark something... maybe the main app's view can be shown for a couple of seconds... maybe the main app's view Show event must start a timer that, in a couple of seconds, redirect to the right other view. The point is that we let the main view a little in the screen, showing the animated GIF, the FontAwesome spinner, maybe a progress bar... something that solve the possible abrupt change between one view and another.


DecSoft (In thread: Change the default / first view at runtime)

Hello Amin,

I understand what you wanted, however, I am not sure if we can got it. Let me to explain. AB allows to choose the first app's view in designtime, and then, in runtime, the appropriate "router" is prepared for the app. In that router AB specify the first view (and default view) according to designtime. Change that route code is possible, since it's in the app's code, but, change it programatically... it's another thing...

I want to continue thinking on that, but, before, please, can you try something that can may be useful? Try to use the "Animation" variable of the first view and also the others who can be loaded. Set this "Animation" to "fadeIn" in designtime. The intention of this is to get a better "view shown" for the user. But I am not sure if this can be solve exactly what you wanted.

On the other hand, maybe the required work (in order to modify the app's route in some way... if possible...), to be honest I don't see anything wrong in your approach: show the main app's view, which can simply shown some spinner or animated GIF or something like that, and then redirect to the user to the right app's view, maybe not automatically, so the user can see that something is loading... and then we load it.

Since maybe the "views change" can be a little abrupt, I suggest to use the "fadeIn" animation. If this is not enough for you, just post it here and maybe we can continue thinking in some possible way to deal with the app's router in runtime.


DecSoft (In thread: Build and publish app into the Apple Store)

Hello to all,

Thanks for your reply, Amin. Certainly I have experience using a real Mac OS computer, and, except for the Apple Developer stuff that must be ready (App ID, Team ID, etc.), I am very happy about how we can debug and finally archive (publish) the app in XCode. The things is quite easy once Apache Cordova is ready, we only need to use one of the AB produced SHELL files and that's all, an XCode project is created and can be opened in order to debug and archive the app.

I mention that because, certainly, I have no experience using virtual machines, Phonegap, etc. The only thing that I can say is that, at least using a real Mac OS computer (that is probably what you suggested too, since you talk about rent a real Mac OS), it's quite easy and pleasant to work. Again, the only possible stuck come from the Apple Developer account and their required stuff, like to prepare the certificates to be used, etc.


DecSoft (In thread: New App Builder release 2019.12 (02/03/2019))

Hello to all,

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

Read the entire product's history


DecSoft (In thread: Build and publish app into the Apple Store)

Hello Kim,

You're welcome. Please, don't hesitate to post here (in this post or in a new one) any further questions.


DecSoft (In thread: Build and publish app into the Apple Store)

Hello Kim,

Certainly AB do not full document the Cordova / iOS / General and Signing options. But they can be deduced from the iOS and Apple "worlds", to say like that.

So you need to search for information about what a "Bundle version", means in the Apple "world", as well what is the "App ID", the "Deployment target" and the "Target device". Here are examples for these fields:

The above is for the General options. The signing options are the same, that is, refers to things that we need and are more or less common in the Apple development world: "Code sign identity", "Development team", "Package type" and "Build blags".

The Signing options refers to things that you must have available in your Apple Developer account. So, for example, you must have created a "Code sign identity", and that is what you must place in the "Code sign identity" field.

The same for the other options: you must have one or more "Development teams" in your Apple Developer account, so you must place in the "Development team" field one of the availables. The "Package type" refers also to options provided by Apple: probably in your case you must choose the "app-store" value for this option.

The "Build flags" can contain... specific build flags to take in consideration when compile our apps in XCode. In principle you no need to fill this field, if you no need to use specific build flags. Below you can see a sample of build flags that we can use:

I hope this information can help you in some way. I must admit that there are not very well documented in App Builder, however, these options refers to Apple and iOS things, so they can be found documented in the Apple Developer website, we can find the right values from our Apple Developer account, etc.

Anyway, please, go ahead if you have any other specific question and we will try to help you.


DecSoft (In thread: Build and publish app into the Apple Store)

Hello Kim,

I am sorry, but, maybe we can help in something. What kind of problems you have? What kind of need do you wanted? What platforms are your targets? Do you already compile your apps to APK, IPA, etc? In few words, maybe we can help you in specific problems or tasks... On the other hand, how to publish the apps in the different stores is something out of the scope of App Builder, that is, every apps store have their rules, instructions, etc. But all of these are documented by the apps stores itself, so, we need to refer to that stores in order to know how to proceed.


DecSoft (In thread: New App Builder release 2019.11 (01/31/2019))

Hello to all,

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

Read the entire product's history

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.

This website uses cookies only to store your preferences.

Ok! Hide this note More information