Posts by DecSoft

Hello John,

I completely forget that we already have an "RSS" app sample, which shown how to parse XML using jQuery. You can also take a look at the "RSS2" sample, which uses another possible technique. I just forget these samples, because, certainly, App Builder includes right now up to 172 samples...

Hello Romeo,

Hi David

When you send a push notification it comes to phone in alert popup box which is nice, then after you read message, it opens the app.

But how can you save that message in the app?

Thanks

If I can understand well, it's completely up to you what to do with the notification contents. For example, in an app that I am developing, we certainly save the notifications (not all of them, only what we wanted) in a database. Then, in an specific app's view, the user can read again all the previously sended (and saved) notifications.

But it's completely up to you to do that if you need it. And probably not save the notification when arrives to the app, but, when send it to the app. That is, the same server's script who send the notification can also save it into a database. Then the app only receive, process and shown notifications, and, additionally, list past notifications too.

Hello Romeo,

I was wondering is there any way to see the message within the app itself again. After you click O.K. its gone.

Please, can you explain a little more this question? I am not sure if understand well. Thanks in advance Romeo.

Hello John,

About your first question, with App Builder we can develop "fixed" and "auto scaled" apps. The first ones do not scale automatically, then, if we design the app in one determined size (800x600, for example) that's the fixed size of the app and therefore requires an screen capable to deal with that app's size. If we develop an desktop app that don't need a mobile version, the "fixed" size can be good. But continue reading...

On the other hand, "auto scaled" apps try to adapt the app interface into all the screen sizes. This mean that we can design with an 320x480 size (this is the default and recommended size) and our app can scale automatically to larger screens. Note that we can not do the opposite: we can't design our app with an 360x640 size and then view the app in an 320x480 size. This don't work as expected.

App Builder includes in our apps the two possible styles: "fixed" and "autoscaled", and, we can change between these styles in runtime too, using the "SetAppScaled" action. Even more, we can set the app to a determined size, but continue using the "autoscale" style instead of the "fixed" one. An example of this can be the Calculator app sample. This sample set the size to 800x600 in larger screens, but continue using the "autoscaled" style.

Depending on the app and their deploy requirements we can design the app in one size or another. Generally, if we want that our app works in almost all screens, we must use the default 320x480 size and the "autoscaled" style. The only problem with this can be when very larger (from our 320x480 point of view) appear in the scene, but, we can simply let the app to scale, or do what the Calculator sample app does: limit their max size to 800x600 autoscaling the controls to that size.

Additionally, note that we can also act in runtime to change the controls sizes, positions, etc. But this is probably not required in the most cases: maybe is not a good idea to perform interface changes depending on the screen sizes, devices, etc. The best is to design our apps to fit our needs (again, 320x480 is a good start point) and let the styles to do their work. Maybe limit the app size for larger screens, but don't do too much more.

Please, John, take a look at these App Builder's app samples: "Calculator", "Scaled" and "InputScroll2".

About your second question, the term "accesibility" can be quite extense. If we are thinking in people who must use, for example, some assistive technology like an screen reader, certainly almost all App Builder's controls have an "AriaLabel" variable, which determines some content useful for that users. On the other hand, if you wanted is to change the font sizes, colors, etc., the action "SetStyle" is for you. But, in principle, we no need to do nothing special with font, font's sizes, etc.

Please, go ahead if you have any further questions John.

P.S. A possible question when design our apps from an 320x480 size, for example, can be, how I can place several controls in the app's views? And the answer is, of course: you can't place several controls in smaller screens! However, this have at least two solutions. The first one is go ahead the view's height. Certainly we can place controls beyond the app's view height, and this work as expected: the app view's can be "scrolled" by the user to reach the controls.

Another possible solution for the above question is to use various app's views. There is no limit in the number of app's views that we can use. Then, supose, for example, we are preparing an user profile edit form. We can add several controls in a view (beyond their original height), but we can also prepare an view with an profile's sections Menu. Then, every Menu item give the user access to other specific app's views, so we can have a view to edit the profile's user information, another view to edit the profile's user app options, etc., etc.

Hello John,

Right now, you can use any thirdparty WYSIWYG Javascript editor, using the appropriate Javascript code. There is nothing like that right now out of the box John.

Maybe if I have some time I can try to prepare an example using the same editor used here in the support forum. But you can also try it: there is quite easy. If you have any problem... just post it here.

Hello John,

For sure is not a normal or common task. But, of course is possible, using pure Javascript. And, exactly in the same way that you must to do in an other HTML app. So, if you want to try it and need any particular help, just tell me know.

P.S. Upgrade your AB copy and take a look at the new Dynamic Controls app sample.

Hello John,

Here are a couple of links:

https://api.jquery.com/jQuery.parseXML/

https://stackoverflow.com/a/7228211/7588436

Hello John,

You can search for "Files" in the samples dialog. You can see the "FileDownload" and the "Files" samples he first in the results.

Hello John,

I think that this other reply can be useful for you for this thread too.

Hello John,

Various things to consider here. The concept of "Download" is not something affordable for HTML apps. HTML apps can't download nor deal with the user's file system, which is reasonable, because, in other way, supose that an webpage can access to your file system... not very good, don't you?

If we have some JSON file in a server... we can just read it using an HttpClient control. If we want to save something in the client side, we can use cookies or the app's local storage, and we have actions to do this already included in App Builder like "SetOption" and "GetOption".

So we can't download files? If our app are compiled with Apache Cordova, yes, we can download files. We have actions like "FileWrite" and an specific action "FileDownload", that we can use. This actions relies in the File and File Transfer Apache Cordova plugins.

There are samples for all of these actions, so you can take a look at it, but, remember that these actions requires that our app must be compiled with Apache Cordova in order to properly work: in other words, that actions can't work in a browser without Apache Cordova.

Hello John,

Parsing XML is possible, but there is not something out of the box to do it, except the included jQuery library (from a few releases ago included by default), which can parse XML, but using pure Javascript. If you can provide JSON files instead, can be better, since we can deal with JSON files in the same way than with Arrays and Objects variables, something possible and easy than using XML, IMHO.

Hello to all,

Hi David, Thanks for that. It is exactly what I was looking for. Best Wishes John

Good. However, remember that we are not limited to a kind of header. We can always use buttons or other controls to prepare it, for example. So the Navbar controls is just another possible way to get our desired results.

Hello John,

Sorry for the delay: I just miss this thread... You can take a look at the program options dialog and the Plugins tab. You can see there the Template plugin, and, an Explore button which allow you to open the plugin's directory. You can also pick it from the "AppBuilder" folder inside your User documents folder, which contains the program's Javascript plugins, config files, etc.

Hola Jordi,

Lo siento, pero, sería precisa más información. "AB no lo reconoce" no explica nada en absoluto. Y, por otro lado, algo que funciona en HTML... ¿por qué no iba a funcionar en AB, si se trata también de HTML?

Luego debes obtener algún mensaje de error o algo: prueba a ejecutar la app en Firefox y usa la consola de desarrollador (si la consola de AB no te indica nada). De lo contrario es imposible saber qué puede estar pasando.

También dices del código que "si lo meto en AB no funciona"... pero, habría que ver cómo lo estás "metiendo"... si es como lo tienes que hacer, etc. De momento, como he dicho, es menester partir al menos de un mensaje de error.

Hola Jordi,

No conozco el API que enlazas, pero, supongo que tendrás que estudiarla. Seguramente, lo que necesitas es acceder al elemento que añades en el control HTMl, es decir, usando el identificador que des al Iframe. Esto puedes hacerlo de varias formas, por ejemplo, usando Javascript:

StartJS var elementoVideo = document.getElementById('IdentificadorIFrame'); EndJS

Lo que tengas que hacer con "elementoVideo" dependerá ya del API en cuestión, que, como digo, tendrás que estudiar.