Posts by DecSoft

Hello tin,

Maybe sound stupid, but, since we are talking about some system font registration... please, follow this steps:

1º Uninstall App Builder.

2º Assert they are uninstalled by try to locate their files in C:\Program Files\David Esperalta\AppBuilder

3º Remove the above directory if they exists after uninstall.

4º Restart the computer (yes, restart the computer).

5º Install the latest release of App Builder.

6º Run it and look again at the icons selector dialog.

On the other hand, please, refer here your Windows version tin. I can't reproduce the problem here right now, so, I am not really sure about the possible solution. Follow the above steps and tell me what happen.

P.S. Remember this post too, since they appear a very similar issue...

Hello to all,

For the first time in more than two years of hard development in hundreds of releases, we must communicate certain changes in DecSoft's App Builder that can break the backward compatibility with some existing applications, in other words, we are talking about some changes that can affect to existing applications, so these applications must be updated / adapted for the nexts DecSoft's App Builder releases.

Don't worry! Maybe your apps are not affected, and, if they are affected, with a few changes, you can be ready to continue use the very latest releases of DecSoft's App Builder. What are the changes that we are talking about? We refer below the changes and also the possible problems and their most appropriate solutions. Don't worry and continue reading.

Introduction

From some release ago, DecSoft's App Builder start to use the Boostrap CSS framework version 4, instead of the version 3. The Boostrap CSS 4 drop their support for the Glyphicons, if I am not wrong, and, between other things, because the CSS code used by the Glyphicons touch certain Boostrap CSS rules, which is something not very good.

Since Boostrap CSS 4 don't support the Glyphicons, we want to drop their support in App Builder too, however, and, related with the above point, this means to remove some CSS rules which affect the Boostrap CSS framework. Removing this CSS rules causes some problems, that we try to solve as best as possible.

Changes in the the Report control

Once we drop the support for the Glyphicons, and, also remove their CSS code, we can say that now we are using the Boostrap CSS 4 in a proper way: no old Boostrap CSS 3 code is now placed in our applications. In fact our apps can appear exactly like before, except for the Report control. The Report control has now enhanced with a new variable named "RowClasses". We must use this variable now to specify one or more Boostrap CSS 4 grid related classes, to be applied on the Report.

Solution for the Report control changes

If you use a Report control with their Wrapper variable set to "table", congratulations! You no need to do anything, in other words, the changes don't affect the "table" reports. On the contrary, if you use a Report control with their Wrapper variable set to "grid", then, you must take care, and, review the HTML code of that Report control. Basically you must to remove the "col-*" CSS classes from your Report HTML, and, use the new Report's RowClasses variable.

Don't worry. All the App Builder Report* samples are updated in the new release in order to shown you how to deal with the "RowClasses" variable. In fact, this class have a default value: "col-12 col-md-6 col-lg-4 col-xl-4", which can be good for a 99% of the Reports, so, remember what you must to do: remove from the Report's HTML code any "col-*" classes that you previously set. Then these classes don't interfere with the new ones. That's all!

Changes in the IFrame control

Not related with the Boostrap CSS framework, the next releases of AB changes how the IFrame controls are drawn. In order to be ready with the iOS platform, App Builder uses now certain technique when drawn an IFrame control. This technique is very well know, and, consists on add the IFrame in a Container, and, apply to that Container (and the IFrame itself) certain CSS rules in order to be ready with the iOS platform.

Solutions for the IFrame control changes

Only if you already apply that "trick" with your IFrame controls, that is, only if you place the IFrame control inside a Container, and then apply the well know CSS rules to it, you must take care. Since App Builder already apply the "trick" for you, what you must to do is to remove the IFrame from the Container, and remove the CSS rules that uses before. Now App Builder do the "trick", so, you no need to worry about the iOS platform "problem".

Changes in some CSS classes

Since DecSoft's App Builder do not use any more Bootstrap CSS version 3, any CSS class that you use in your apps related with this version of the framework don't work anymore as expected. Again, don't worry. You can take a look here at this migration guide, only if you find some specific problem.

Since DecSoft's App Builder do not include any more (by default) the Glyphicons icons, you must change it (if use) by the included ones. Supose you are using an icon in a Push button control. If the icon is already an Awesome icon (included by default in App Builder) you no need to worry about. If your icon come from the Glyphicons package, what you must to do is to select another icon from the availables.

Conclusion

This is the very first time (that I can remember) that some changes in App Builder can cause that some existing applications must be modified in order to be ready with that changes. The affected controls are, however, only the Report and the IFrame ones. These changes are needed, because we must say goodbye to Boostrap CSS 3 and the Glyphicons. With Boostrap CSS 4 we no need it anymore, so, maintain old code just for backward compatibility is not good in this specific case, because the old Boostrap CSS 3 code interfere with the new Boostrap CSS 4 code.

Are you ready?

When this post was published, a new release of DecSoft's App Builder has been published too. You can start to play with it, searching for possible problems like the mentioned above. I am here to help, then, if you have any related questions, please, just post here. On the other hand, I want to place here a previous release of DecSoft's App Builder, then, you can use it if you wanted too:

Download DecSoft's App Builder 2018.11

Now say goodbye to Boostrap CSS 3 and the Glyphicons icons, but, say also hello to the Boostrap CSS 4, the Awesome icons (I plain to update in a next release of App Builder too). These changes are required and to continue working with App Builder using the latest version of Boostrap CSS. Definitely.

Again, please, post here any possible problems around these changes. We will try to help you as quickly as possible.

Hello to all,

I think "Decsoft" sample will the best guide.For quick deploy.

Can be a possible way: to use JSON as a possible source. In fact how the contents are stored (or how can be stored) can be fundamental here. But yes... we can also decide if use views, or to prepare some of them "specialized" in shown certain source (chapters, lessons...)... certainly we can take several approach.

Hello to all,

Thanks David,I can use Materia theme now!!

That's good, Tin. However, be ready for more possible changes related with Bootstrap CSS 4 too... I am working hard on it right now...

Hello tin,

I am proud to announce that the current release of App Builder already uses Boostrap CSS 4 instead of Bootstrap CSS 3, and therefore, App Builder also includes now the themes that you refer in this thread. Hope they can be good for you! :-)

Hello Joseph,

Probably there is not just one way to achieve what you wanted. We can talking about if you wanted. For example, if you have doubt about how many app's views you can use, in fact there is not limits in the number of app's views that you can use. On the other hand, depending on the project, maybe it's possible to not simply add views, but using some other approach. Please, go ahead if you have any further questions!

P.S. For example, we can use JSON files or just plain text files to store the courses contents, and then load it when needed in certain specific app's view. It's just an example: as I said above, we can probably take several approach to do what you wanted.

Hi David,

I read about the Domo Electra project with AB when you sent it by email. I was really happy for you and I know this is just the beginning of the AB application. Without doubt in my mind, AB application will still be more popular.

I have already told most my school mate about AB application and they were amazed too.

Thank you David and keep it up.

Thanks Ade. :)

Hello to all,

Thanks for the explanation! Certainly, there is more than one way to achieve what you wanted. Here are some of them. We can use the "ng-style" in one or more "TD" elements (if we play with a "Report / table": may more easy if we play with a "Report / grid") in the below way:

The above works, but, maybe we prefer to use a CSS class instead to apply certain style directly, so the code can appear like the below one:

In the above code, we are set the "match-name" CSS class for a Record's name which is equal to "Abel". Note that we can add more than one CSS class:

In the above case, we add the "match-name" and "other-class" CSS classes. You know this CSS classes can be defined in the app's Inline CSS option or in a separated CSS file added to the app.

Other additional possibility is to add a CSS when the name is not matched, and, for example, in the below code:

The above code add the "match-name" CSS class if the Record's "Name" is "Abel", and, on the contrary, add the "no-match-name" CSS class if the Record's "Name" is NOT "Abel".

Try with that code Joshua! Post here if you have any further questions.

Hello to all,

Is there a way to make record rows in Report control to stand out on the basis of the rows' specified field value?

I am not sure if can understand Joshua, please, can you explain a little more?

Hello Joshua,

It's done!
:cool

Here too! Thanks very much for your support Joshua. :)

Hello Joshua,

there are some limits in our country for Paypal
I will find other ways to work out

Just let me if I can do something about! A bank transfer can be good here? I can provide you the right data (IBAN number) in order to proceed! Or I can send your license and then you pay when possible! Just tell me what I can do Joshua.

Hola Jordi,

Gracias por tu "builder consejos". :) Otra posibilidad de visualizar un documento PDF, además de la que mencionas, se muestra en el ejemplo "PDFViewer", donde se usa el visor PDF de Mozilla.

Es algo más o menos similar al visor PDF de Google, pero, el de Mozilla podemos incluirlo en nuestras app, o bien situarlo en nuestro servidor, en fin, no depende de Google u otro servicio "en línea".

Hello Eduardo,

You're welcome! Always thanks your support! :)

Hello Eduardo,

Please, upgrade your DecSoft's App Builder copy: the images from the app's files are now shown in designtime too. Just like you wanted.

On the other hand, let me to say that we can deal with app's images in both ways: using the app's files manager and just picking the images from the object inspector. If the images are in the same drive than the app's project file (which is absolutely recommended) App Builder stores relative paths to the images, then, there is no problem to move our app's files to another computer, for example.

But, anyway, you have reason: the images paths from the app's files manager are not shown in designtime, and this is what I enhanced rigth now Eduardo, as you can see when update your AB copy, these images' paths are now also shown in designtime. Just like you wanted.

Hello Eduardo,

I think that I understand what you wanted. Certainly, the problem is to determine the images' path. But I think that I can do something about, Eduardo, the let me to try it and then I will inform you here.