Posts by DecSoft

Hello,

Thanks for posting Donald. Certainly PayPal.me can be a solution in some cases. Here is my URL, for example:

https://paypal.me/davidesperalta

I think, for other possible uses, we can deep a little search for possible Javascript/HTML APIs. In the future maybe some kind of API can be integrated in App Buidler, but, unfortunately, I can't promise nothing at this time.

Hello Ade,

Thanks for posting. Certainly it's easy to made a "ListView", since we have "views" and also "Multiselect" and "HTML" controls. We have also a simple "Select" control, which on Android, for example, is very lovely, since the system show us a "modal list" with the options to choose.

About the "Scrollview", I am not sure, but, remember our "Report" control: take a look at the "Report1" to "Report9" samples... such control offer us lot of posibilities. Maybe right now we can't get a "scrollview" (out of the box) but a very similar and widely used approach.

About the "Login" and "Grid" view: the login can be prepared with a couple of "Inputs". The "Grid" control does not exists now in App, but, a control like that in a mobile environment... anyway we can use a "Report" control for data show, and then "Inputs" for data edition.

About PayPal,... my recomendation right now is to use some of the "HTML" API they offers. For example, we can open the "Paypal users page" in certain "Iframe", or use the "OpenWindow" action with certain PayPal links ready to process a purchase.

I know this is not exactly the answer you may expected, but, hopefully they can help you in some way Ade.

Hello,

Thanks for sharing Asley! :)

Hello Donald,

Basically we need to use the Location control in conjuction with the GeoLocation action. Once we call such action the Location control's events can be fired. Take a look at this sample application: MyApp.zip In principle this control can works in browsers "as is", however, you can check/add the "Location" plugin for Apache Cordova.

Hello,

Tryting to reply as best as possible (like always) I want before to ask something: are you tried with the app's views "Animation" variable? A "fadeIn" animation for the app's views can looks nice. Anyway, I think we can do somethings, but, probably not in a generally way. At least I can't think a way to "generalize" a question like that.

For example, I am investigating a possible images "preload", however, probably this cover only a portion of your idea.

Are you experimenting some problem? Using some specific control?

Hello Donald,

The file's manager just saves referecences to the files (their relative application's path to be exactly) and never touch or copy the files.

Hello Donald,

I can't reproduce here such behaviour. Are you sure the application is properly saved before save it again using "save as"?

Hello Donald,

I can't reproduce the problem here. That is, suposing an application with certain files added, I can save such application with other name (but remember, in the same directory!) and then I cam compile it without problems.

Maybe you save your application with other file name, but, since the app name is currently the same than the previous one (because one thing is the app's name, and other is the app's file name) the compiler do not update the compiled directory properly? So we need to remove it firstly?

Hello Donald,

This have a long story behind. The initial App Builder releases based their designtime controls in the Microsoft Windows WebBrowser control. In that days every control in the designer are in fact a WebBrowser control which in fact reflect more or less well the final result. Unfortunatelly, the usage of the WebBrowser control have a great impact in the program behaviour, like you can see in the below video:

https://www.youtube.com/watch?v=BZE2QShiIR4

In order to get an IDE really faster and don't worry if our applications have two or twelve views, dozens of hundreds of controls, I decide to get out the WebBrowser control as the base for the designtime controls. However, I know the current designtime controls can probably be enhanced. This is something I know and therefore I want to deal with it in the future.

Hope this can help you in some way. :)

Hello,

No problem Donald. Certainly the file's manager copy the "complete" path because we can use it in Image controls, HttpClient controls, etc. In fact we only need to refer to paths like "../" when use it in CSS styles. However probably I can do something about. In the meanwhile, it's good to know the app's directory tree, where the files, images, etc., are placed, etc. Therefore, forgetting the drawbacks, maybe we can learn something here. :)

Hello Donald,

If you added a "redwhite.png" image using the app's file's manager (under the Images tab!) then the below code must work:

Are you sure you put that code for the entire app, or, in other words, are you sure you add the code in the right app's view?

Can you provide (attach it here if you wanted) a sample application in order to try here.

Hello,

App Builder produces applications are HTML5 applications ready to be deployed in desktop and mobile browsers. This is why I recommend to use the App Builder's integrated debugger, and, also, the Firefox browser, since their developer console (just press "F12" when you are in Firefox) is absolutely amazing and can help us too much.

Apache Cordova, on the other hand, allow us to build such HTML5 applications in order to be deployed in various platforms, one of them Android, but also others like iOS, for example. But, in my opinion, we must debug and test the application before build for that possible platforms, using the integrated debugger and other browsers like Firefox.

Of course certain things cannot work in browsers. For example, if we plain to use the "Files" Cordova's plugin in order to write and read text files from our applications, the FileWrite, FileAppend and FileRead actions can't work until our application are build using Cordova. But we know (using the [App.Cordova] global variable) if our application is running in a browser or builded with Cordova.

Then we can prepare a "workaround" to that actions, again, in order to continue debugging our application using the integrated debugger and Firefox, for example. In few words, trying to made something like this can save our time since the integrated debugger is faster that any emulator nor bridge. Of course we must to test our application in a real device, but we must do that in any other environment.

That's the idea.

Hello Donald,

It's more easy than appear. Taking a look first at the compiled app's directory tree:

When we use the app's file's manager to choose an image (to later use it as the background) such image is copied into the "app/images" directory when the application is compiled. The app's stylesheets, however, are placed in the "app/styles" directory. Then, when we must to refer to an app's image file from an app's stylesheet, we must "up to the parent directory", and this is what is we are doing below in the code:

Such code are placed in an stylesheet in the "app/styles" directory, so we "up to the parent directory" (using the "../") and then enter in the "images" directory to finally choose the "Background.jpg" image file.

Hello Ade,

Yes; fortunatelly we are both in home. However she requires lot of cares. Hopefully with their rehabilitation and the sufficient time she can recover their mobility. :)

You're welcome! :)