Posts by DecSoft

Hello Amin,

It's very good that you got it. One thing to do by myself is try to search for a possible "stable project" for Bootstrap RTL, search a bit around this topic, so, we can use the right CSS, maybe the one that you already use, and then include this theme in the App Builder's installation, so put it available to be used "out of the box".

Hello Amin,

I am sorry for too many problems. Certainly change a theme at runtime is possible, but, we are talking here about an special theme... the RTL one... that, in fact, I don't know if it's updated or what... maybe we must see in this direction: trying to locate some Bootstrap RTL... that uses the latest version of Boostrap...

Thinking about... what if you identify that the user needs the RTL theme and then start the app from the scratch? We are here in the same problem than the "default view" that we have in the past? Maybe another configuration variable for the default theme can help?

Hello Amin,

Yes; of course. We can use the SetAppTheme action. You can change the [App.TextDirection] global variable and the app's theme according to the language. Remember that we can include in the app as many themes as we wanted, in addition to set the default one to be used. Then, in runtime, we can set one of the includes themes when needed.

Hola Jordi,

La variable Report.Data es un Array, por tanto, podrías usar la acción "ArrayLength", para averiguar el número de elementos en dicho Array.

Hello Amin,

Certainly, support RTL languages is not my best... I can imagine that maybe we need to deal with our own CSS... or maybe download something like Bootstrap 4 RTL... (I am not sure if this is maintained by the official team).

Since the above apparently don't work (the download link is dead) I find this other project, who link to this RTL Bootstrap CSS file.

Now, navigate to the RTL Bootstrap CSS file, copy the CSS and save it in a file like "rtltheme.css". Copy this "rtltheme.css" file into the "C:\Users\[Your Windows user]\Documents\AppBuilder\Themes\" directory. Start an app, or open y our own one. Open the app's options, and set available the new theme, even use it by default.

And try it, Amin... I think that must be the direction... and work with possible caveats using more CSS... The referred last project also link to a JS version of Bootstrap... I am not sure if we need this... if so, maybe we can include it in the app's file manager, but maybe this cause some problems with the already included Bootstrap version... the CSS is different... we can use the above RTL CSS file as a theme without problems (if I am not wrong right now).

Hola Jordi,

Claro... por eso te decía... digamos que el Query del Report es la forma más sencilla y rápida de filtrar su contenido, ojo, su contenido, lo que se muestra, puesto que en realidad estamos actuando sólo sobre la variable Report.Data. Todo lo que vaya más allá, como posibles búsquedas más complejas, pasan por no usar el Query del Report... sino por prepararlo nosotros mismos, filtrando la variable Report.Data nosotros mismos, bien en el cliente, bien (probablemente mejor), en el servidor. Hay un ejemplo de paginación de datos en el Report... la idea es la misma... se le envían al servidor los campos o inputs que sean necesarios... y el servidor retorna el JSON para el Report.Data convenientemente filtrado, listo para usar.

Hola Jordi,

Si no me equivoco, el "Query" del Report filtra usando todos los campos... diría que incluso los no visibles. Por ejemplo, puedes probar el ejemplo "Report", y, buscar por un deporte o por el nombre de una persona...

Para todo lo demás, también podrías tú mismo filtrar, bien la variable "Report.Data", bien lo que retornas desde el servidor de tu app. Siempre teniendo en cuenta que lo situado en "Report.Data" será lo que se muestre: antes de mostrarlo, por tanto, es posible filtrar aquello que se necesite.

Anyway... probably there is nothing like a mouse and a keyboard. I don't want to compare App Builder with Delphi nor other IDE... but, as an user of more IDEs (in addition to App Builder), I can't imagine to work with it using a touch screen... maybe for some specific actions, yes... maybe we need to edit something... but certainly just think to work without a keyboard and a mouse scare me. Maybe I am too old!!?? :-)

Hello Harald,

I must declare my ignorance in touch screens.... in principle, I can't understand why a pen is different than a finger, that is, why they differs in their configuration. Of course there must be a reason... and maybe another possible configuration that I simply unknow... :-(

Hello Harald,

Thanks for your ideas. There is a lot of work and the time is limited, but, I will look into this for sure. I think the Javascript plugins can be useful... and in fact there are various of them working like a charm. But anyway I will look into this and hope that can get something good.

Hello Harald,

Sound good, but, probably we are talking about something beyond "just" custom HTML blocks... In fact, a Javascript plugin for App Builder can perfectly require an HTML control, so, they can act or do something with that. Another kind of plugins in addition to the Javascript ones? Let me to think about... and please, post here if you have any idea that you consider that can be good on this topic.

Hello Harald,

I think the idea can be good, of course. However, I am not quite sure about their possible implementation. If we are talking about to share HTML markup, certainly, just to copy that markup into the clipboard, and then paste it into the AB designer, causes the creation of a new HTML Content control with the clipboard's HTML markup.

On the other hand, an HTML Content control can also contains events and may the right code placed in that events. When we copy an HTML Content control to the clipboard from AB, what we copy is a XML piece which include both, the HTML markup and the possible events and code of that control. So, I am not sure if you refer to share only the HTML markup or may also the code.

What do you think about? Any idea after the above? I will insists that the idea appear good to me, but, maybe we must think about twice before try any possible implementation.

Thanks for sharing, Peter. :-)

Hello to all,

A couple of days ago we start to experiments some problems while try to send E-Mails from the DecSoft websites, that is, for example, to customers who want to reset their password, new replies to customer's threads, etc.

This post is to say that apparently we finally fix the referred prolem: it's possible that the E-Mails arrive to your E-Mail inbox into the SPAM folder... so please, take a look at that folder and check that E-Mails as non SPAM.

P.S. Note that the problem that we try to fix means that you never receive an E-Mail, even into your SPAM folder. For example, if you use a GMail address, GMail simply reject the E-Mail and you never knows about it. We want to continue looking into this, but, as I say before, at least now GMail receive the E-Mail and maybe put it into the SPAM folder.

Hello Peter,

Please, upgrade your AB copy. We reach the 190 app samples with the current release, one of these, the new WYSIWYG app sample. This app sample uses SummerNote to provide a WYSIWYG editor to our apps, and, shown how we can initialize it with some specific contents, and how to retrieve the contents from the editor, in order to be uploaded to the app's server, for example.

In fact, we go a little beyond with this app sample. Let me to explain a bit. In the sample that I prepare for you above, and, in order to allow me to copy it here as XML, we use the SummerNote script and style from a thirdparty server, that is, we use URLs to retrieve, link and use these required files. When I start to prepare the sample to be included in App Builder, I note that the style file requires by itself a couple of font files.

The above represent a problem, because, we can use the app's file manager to specify an app's local script and style, but, then these files are placed into the "app/scripts/" and "app/styles/" folders, and, in the case of the SummerNote style, can't find the appropriate font files in the expected place, so the editor cannot be properly initialized nor used.

To avoid the above problem, the current release of AB allows to specify app's relative paths using the app's file manager. So, as you can see in the new WYSIWYG app sample, what we do is to use the file manager "Folder" tab, in order to include the entire "summercode" directory. Then, we specify app's relative paths for the required style and script, and, now yes, all works as expected, since all the required font files (for example) exists in the place that the SummerNote expected.

Probably you reach the described problem if you start to use local files for SummerNote (which probably it's quite recommended, since it's perfectly possible, easy to do (right now) and do not depend on any server), so I hope the introduced changes are good for you and others too.