Posts by DecSoft

Hello to all,

Then I can't be a bit sarcastic with my poor english... if I am not wrong my imagined sample 3 wanted to shown that, at least some times, we can reduce the sample 2 to just one line, that is, from this:

SetStyle "View1" "margin-top" "0px" SetViewSize "" "[App.InnerHeight]px"

To this:

SetViewSize "" "[App.InnerHeight]px"

On the other hand, the sample 4 wanted to use the Amin proposed code. So, as you can see, Tin, we already know what the sample 3 and sample 4 can be, without included it in App Builder. :)

Hello Paolo,

I am not sure if the Collapse component of Boostrap CSS can be useful for you. If so, it's possible to use their HTML "as is" in an AB HTML Content control and the Collapse component works as expected.

Another possible way can be to use a hidden AB control (maybe an HTML Content or a Container control) that can be shown / hidden when a Push button is pressed by the user.

May you can also implement the "Material project" that you linked, just trying like any other thirdparty Javascript code. If you decide to do this, just post here if you find some specific problem.

Hello Paolo,

Maybe you must use something like this to shown the modal?

$('#exampleModal').modal('show');

Note the "show" argument passed to the "modal" method. On the other hand, can you try to reproduce the problem in a small sample app and then send it to me via email or shown here what error message you get?

Hello again Paolo,

I send to you an app sample which uses pure HTML and Javascript to shown modals. That works as expected, so, I supose that the problem is in another place in your code. Please, take a look at the sample that I sent to you, may can help you in something. On the other hand, remember that we can use views as modals dialogs without HTML and Javascript, that is, using AB app's views and AB actions.

Hello Paolo,

If we try with the "Live demo" code from the Boostrap CSS documentation, the thinsg works as expected. However, we can use AB views and the "ShowDialog" and "CloseDialog" actions in order to shown modals views.  Anyway, can you try with the refered Boostrap CSS "Live demo" sample and tell me if that works for you?

Hello Paolo,

Thanks for share the possible solution. :-)

Just to comment another possible solution... we can work with the Report's Data variable, and, the changes that we made on it, are automatically reflected in the report. Supose we have the Report's Data source from the response of an HTTP client control. We can then process that Data variable (iterate it) and add new properties to the object items that can contain, for example. The server can also do something like that, that is, include in the Report's Data variable what we need, in order to avoid to use more or less "complex" code.

The above mean that may we can prepare the appropriate URL for the image in certain Data's item variable, and then we can "simply" use it in the Report's HTML code. Of course we can do it, but, maybe the "use simple variables" approach can be more clean, to say like that.

Hello to all!

Yes; Tin, another issue that I can see is if the input is in the bottom of the view, but, we can solve it by place some container or other control like a button below the input that is reach to the bottom of the view. On the other hand, I want to prepare an InputsScroll3 sample... and maybe an InputsStroll4 sample based in the Amin code, just when I can try it here. :-)

Hello Amin,

Thanks for sharing that code. I want to try it when possible. I think the InputsScrolls sample can be avoided, since we can use the InputsScrolls2 sample approach, even if our inputs are not beyond the app's view height. Maybe I need also to prepare an InputsScrolls3 sample, because, from the below two lines that are used in the InputsScroll2 sample:

SetStyle "View1" "margin-top" "0px" SetViewSize "" "[App.InnerHeight]px"

... certainly the first one can be avoided sometimes, getting also good results with the software keyboard. So, we can choose the approach of the InputsScroll sample, that don't satisfied me due to the use of a container. We can also use the InputsScroll2 approach, with the above two lines, which works well, even if the scrolls don't go beyond the app's view height. And we can also try with the same approach, but, using only the second line of the above code.

And of course another possible way can be to try your CSS code. :-)

Hello Amin,

I already reply to you via email, but, also want to do it here, so the thread don't get finally "unclosed". Certainly the issue with the AlertBox that you found exists, however, it's quite, quite rare and difficult to catch. In fact, what I suggest to you is another possible approach, just a simple change of the "CloseDialog" action. They work more or less as expected (can work, anyway) and the AlertBox issue did not appear in this way. I hope the proposed approach / solution can be good for you, Amin. :-)

Hello Amin,

If the problem with the close button persists, please, give me a sample app in which I can reproduce the problem here. You can send it to me at info (ARROBA) davidesperalta (DOT) com. Certainly I can see the problem with the close button here at the first time, but, solving the bug with the AlertBox, then I can't see it again. So please, give me an sample app in which I can reproduce the problem and then I will try to fix it.

P.S. I try with the HttpClient app sample, in which the Http Client control launch an AlertBox in their Success event, and they works as expected.

Hello Amin,

Yes; apparently you found a bug, sir. I fix the main problem now, that is, we can close the app's dialog or modal view after shown an AlertBox. If I am not wrong, this fix also implied that the problem with the close button in the AlertBox has been solved too. Please, upgrade your AB copy, made your own tests and tell me if the AlertBox action works now as expected.

Hello Paolo,

Thanks for sharing that information with us. Certainly, client side databases are something not very well supported, and, for example, can have some limitations in terms of the available storage space. Can be a good thing, of course, and, apparently the project is used by some relevant projects.

However, my point is that maybe not all the times we need something like a relational database in the client side. For example, we can use the app's local storage to store information in an JSON way, which can be set and get when needed.

We can also use the app's storage to store other kind of information in addition to certain JSON, for example, something ready to be used by the ParseVariables action. If our target allows to use Cordova, we can write files too in order to store information in the client side.

And, finally, we can use an app's server... and therefore a server's database (MySQL, Oracle or whatever else) in order to store our app's information in the server side: this means we don't have the possible limitations in the client side, of course.

Anyway thanks again for share the project with us, Paolo: again, I only want to remark that maybe not all the projects requires something like that, but, of course, may can be useful in certain specific projects, or just a good tool to take in consideration.

Hello Amin,

Glad to know that you got it. :-)

Hello Paolo,

If we are talking about an AB Select control, we can add new items using the Select Array "Items". If we are talking about an Select control, but not an AB one, we can add more options to the control in various ways, for example, take a look at this StackOverflow thread.

About the Select value, if we are talking about an AB control, in fact we deal with the selected item index and the item text, to say like that, not exactly the value, and can be retrieved like in the below code:

ArrayGetItem "[ColorsSelect.Items]" "[ColorsSelect.ItemIndex]" "[SelectedColor]"

If we are talking about how to get the value of a Select control which is not an AB control, we can do it in a way like this:

$("#myselect").val();

If what we want to get is the Text of the selected value, we can write something like the below code:

$("#myselect option:selected").text();

Hello Paolo,

I think we can consider this a more or less "advanced" feature... and, in fact, you already can use "document.getElementsByClassName", or, better, "document.querySelector", or maybe better... an jQuery selector (remember that jQuery is included in our apps by default) and pick classes like "custom-control-input" and "form-control". With these two classes you can match all the inputs controls in your app's view.

Below is a bit of code using jQuery that may you can find of your interest:

StartJS $('.form-control, .custom-control-input').each(function () { // All text inputs if ( $(this).hasClass('form-control') ) { alert( $(this).attr('id') + ' :: ' + $(this).val() ); // Checkboxes and radio buttons } else { alert( $(this).attr('id') + ' :: ' + $(this).is(':checked') ); } }); EndJS

If you need any kind of particular help, please, post it here, Paolo.