Posts by DecSoft

Hola a todos,

El problema es el tiempo, Asley, aparte de la necesidad de contar con una cuenta de desarrollador en Facebook, una app "para pruebas", etc. En realidad implementar algo así en AB y en AB2 debería ser muy similar, puesto que se trata de utilizar el API de Javascript que proporciona el propio Facebook, pero, insisto, es necesario un tiempo del que ahora mismo no dispongo. No digo que no lo pueda hacer en el futuro... pero... lo que sí he dicho ya es que estoy dispuesto a intentar echar una mano en algún punto en concreto del proceso, si fuese menester.

Hola Jordi,

No me queda claro qué has intentado hasta el momento. Tampoco creo entender bien cuando dices que te pregunta el email y la contraseña. Por último, no me queda claro si tu app incorpora ya algún tipo de mecanismo de "login"... Sea como sea, nunca lo he intentado, pero, empezaría con la propia documentación del SDK para Javascript de Facebook.

Creo que por ahí pueden ir los tiros... o bien exista también algún SDK para hacer lo propio en el lado del servidor... pero vaya, yo empezaría por revisar la documentación del SDK de Javascript. Por ejemplo, aquí se muestra cómo se puede utilizar en conjunto con jQuery, que, ya sabes que se incluye con todas las app de AB.

En fin, investiga la documentación del SDK para Javascript de Facebook y si necesitas alguna ayuda en particular coméntalo en este hilo e intentaré ayudarte en la medida de mis posibilidades.

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

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

Read the entire product's history

Hello to all,

Here is a new DecSoft HTML Compiler 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 Paolo,

you were just perfect! I had thought of this solution, and your confirmation makes me happy. To store the status of some variables that are set only once I'm already relying on a json file that resides in the webserver, and everything seems to go perfectly. Thanks always, App Builder it's a real power and satisfaction of its own and wonderful for the support too! Thanks thanks thanks

You're welcome! Glad to know that I can help you in some way, Paolo. Thank you for your kindly words!

Hello Paolo,

I am not sure if I can help in an exact way with the information that I have, but, I will try it with some information from my own:

1º Even when we can try to catch the F5 key, maybe also the CTRL+F5 keys, in order to avoid the browser to be refreshing, probably this is not a very good idea, I mean, if the user want to press the F5 key or refresh the browser by other way (the menu, for example) he must can to do it. So thinking to avoid the browser to be refreshing can't be a solution in my opinion.

2º The Ready event of the old DecSoft App Builder, is not related with a specific view, but with the whole app. This mean that if we enter the app from the "View2", the same "Ready" event is executed than if we enter the app from the "View1".

3º Sometimes we use the first / default app's view in order to initialize some variables for the entire app, or to made some HTTP calls which get us information to be used in the entire app (other views). This is important, because, certainly, if we go to the View1 to the View2, and, once we reach the View2, the browser is refreshing by the user, what is loaded is the View2, and not the View1, as we can expect.

4º The above 3 point can be your case, Paolo, and, there is a solution to force to load the View1 firstly of all other app's views. So, even when the user refresh the browser at the View2, we can force to goto the View1 and start the app from that View1 view. The solution is more or less easy, for example, we can use the View1 Show event to place a code like the below:

... then, in every other app's view Show events, for example, in the View2 Show event, we can place a code like the below:

... now suppose your app start and then you or the user go to the View2. Everything works as expected, because you go to the View2 from once the View1 has been loaded. Suppose now that the user refresh the browser at this point, that is, when he is in the View2. In this case, the above View2 Show event is executed, and, since the "MainViewIsLoaded" variable is not defined (because it's defined in the View1 Show event), we just redirect the user to the View1, and therefore the app started as expected, from the View1.

5º On the other hand, we must know that the app variables are not saved if the user refresh the browser. If we really want to store something between app executions, we must use the browser's local storage. The old (previous) generation of DecSoft App Builder provides you with actions like "SetOption" and "GetOption", which deal with the browser's local storage. If you save something in the local storage, when the app starts again (for example, because the user refresh the browser), that stuff is available to be used. You must take this in consideration if you need to store something that remain between app executions: the app's variables are lossed when the app is restarted, but the local storage is there to save information which is not deleted between app's executions.

6º Another possible way to store information can be the app's server. If we save something in the app's server, for example, in a database, that information remain intact even if the user refresh the browser. So we can consider this like a "server storage", something similar than the local storage, but, with the information saved in the server side.

Said the above, I think your specific problem is related with the app's views. I suppose that you made some initialization in the main / default view's Show event, in other words, you expect that the app starts in the default / main view, and, certainly, as I refer in the point number 3 above, if the user is in the View2, and, then refresh the browser, then the app start from the View2, and not from the View1 (the default / main view). If this is the case, what you must to do is what I explain in the points 3 and 4, that is, force the app to start in the View1 (the default / main view), so the app's initialization is made as expected.

I hope this information can help you in some way or give you the right ideas, but, please, go ahead and post here if you have any further questions, Paolo.

Hello Danny,

Certainly, there is no tutorials about how to publish in the stores. However, I can say something about it. For the case of Android, the things are more or less easy, because, the point os to get our app's APK file. And we can do this directly from Windows, that is, we can compile our app's APK using Apache Cordova (with the stuff provided by DecSoft App Builder) and finally get an APK file ready to be upload into the Google Play store. Basically, in order to be published, we need to prepare a "release" APK, instead of a "debug" one. But, once we do that, it's a question to use the Google Play store account to upload that APK, following the steps that we can see in our Google Play store account.

Talking about iOS the things are a bit different. Apache Cordova can create IPA files of our apps in Mac OS, however, what I do for my own iOS apps is to use the XCode IDE. So, the steps that I follow are more or less these ones: 1º Compile the app in Windows, so we get the "compiled" directory, with "shell" files ready to compile the app with Apache Cordova on iOS. 2º So we move the "compiled" folder to a Mac OS, and, then execute the "debug" shell file created by DecSoft App Builder in a Mac OS computer. 3º Once we do that, that is, once Apache Cordova compile the app with that shell file, what we get is an entire project ready to be opened by the XCode IDE.

Once we have the project opened by the XCode IDE, we must choose the "Project / Archive" in the menu. Then the IDE offer to use various ways to distribute our app. I can't help you in order to publish in the store, precisally, because the apps that I develop for iOS are distributed (from Project / Archive) using the "Enterprise" option, which is a bit different than to publish in the store, however, certainly when use the "Project / Archive", there is an option to distribute the app into the Apple store. So I think it's a question to follow the instructions... select that option (Apple store) when "Archive", and follow the steps that the XCode IDE requires.

Maybe you can try all the above, and, also search in the web about how to publish in the Android Play store and the Apple store, I mean, the instructions that you can get, probably can be used without problems also for our DecSoft App Builder apps, since finally what we get are APK files (for Android) and IPA files (for iOS), so, at this point the publication in that stores do not differ from another apps made with other possible tools. What you can do is to go ahead, Danny, and, if you find some particular problem or question, just post here or in a new thread, so I will try to help you at that particular point.

Hello Danny,

Not a basic question for sure! Certainly, we can set the app's default view at designtime in both AB1 and AB2. The first view in the app's views list is the default one, which is loaded when the app starts. Additionally, in AB1, we can set the app's default view at runtime, but, I am not sure if this is exactly what you wanted.

Why I say that? Because, for example, we can have a app's default view who redirect the user to another app's view. We can dedicate the app's default view only for this if we wanted: the scenario is not common, but, it's possible if we want to do it. On the other hand, maybe you really want something like AB1 in AB2?

Maybe I can ask why you think you need that? In other words, maybe you can explain here what you want to do, and then, maybe I can help you without the implementation of something similar than AB1 in AB2. If we finally see that we need something like AB1 in AB2, then I can try to implement it in AB2, Danny.

P.S. If you want to refresh your mind about how to set the app's default view at runtime in AB1, you can take a look at the AB1 "StartEvent" sample app.

Hello to all,

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

Read the entire product's history