Posts by DecSoft

Hello Paolo,

Probably it's an issue related with the IDE layouts. Please, close the program, remove this folder: "Users\[Your Win User]\Documents\AppBuilder\Layouts" and then try again.

Very good then! :-)

Hello Paolo,

Created by DecSoft's App Builder v2019.37 More information at https://www.decsoftutils.com/ Using cordova-fetch for cordova-electron@^1.0.0

Humm... that mean that finally you got it? :-)

Hello Paolo,

The version of Cordova appear fine. Please, try to upgrade NodeJS too. Download and install the latest stable version. Additionally, check if you meet all the requirements for the Cordova's Electron platform.

After do the above, remove the "_Compiled" directory of the app, compile it again so you can try to run the BAT file again from the scratch.

Hello Paolo,

I refer to the version of Cordova itself... you may can upgrade your Cordova installation: see what version you have running the below command:

You must see the version 9.0.0. If not... you can upgrade Cordova by typing this command:

As you can see... the Cordova's Electron version is 1.0.0... and this is what must be required... not the non yet existing version 5.0.0...

Hello Paolo,

Please, sorry for the delay... it's a problem here in my hosting with the E-Mail relay... I already open a ticket and hope the problems go on as quickly as possible. :-(

About your problem, it's quite rare... that is... certainly the current Cordova's Electron version is 1.0.0... so it's no way to try to play with the version 5.0.0. That's what the error message means: the required version is not found...

However, it's double rare... because... the BAT files generated by AB do not specify any version of the platforms, and so, the question is why in your case the version 5.0.0 is required..

Trying here in my computer the platform version that it's trying to be used is the expected one: 1.0.0... so, please, try by upgrade Apache Cordova... in order to assert that you are using the latest version.

Hello Peter,

Good to know! Please, sorry for the delay... it's a problem here in my hosting with the E-Mail relay... I already open a ticket and hope the problems go on as quickly as possible. :-(

Hello Paolo,

Glad to know that you got it. :-)

Hello to all,

Here is a new DecSoft App Builder release, with the below changes, fixes and enhancements:

Read the entire product's history

Hello Peter,

Please, take a look at the below app sample, who use the Summernote editor. Copy the below XML, save it as "MyApp.ab", open that file with App Builder and run the app:

As you can see, using an HTML control to place the editor, it's quite better than try to use the Textarea replacement approach. This is because, also with Summernote, when use a textarea in order to be replaced with the editor, the editor become wrong positioning, and, even when maybe we can try to fix this using CSS, probably it's not as easy as appear (see my previous post in this thread), and, on the other hand, apparently the HTML control can give us a more or less good usage of the editor.

Look at the above app sample. Probably we must calculate a "height" for the editor, or probably apply some possible CSS... and, of course, since we don't use a Textarea, we can't use any existing variable, but, in order to set and get the content of the editor, we must use the editor's API. But honestly I think this is the way, Peter, since the Textarea replacement appear to not work as expected in our case.

Supose that we find difficulties to integrate the editor along other controls in the view, since we use an HTML control, that may finally don't fit exactly the place that we wanted. Here may we can take at least two approaches: the first one, include other possible required input text controls also inside the HTML control. Or, maybe include a button and not the editor, and, when the user press that button, shown the editor in a new view (maybe modal), since maybe the editor can be more easily fit an entire view. Both of these approaches are correct, in my opinion. *

* If we can't fit the editor along other controls... but this don't mean that maybe that is possible: depend on the controls that we want to use, their positions, etc. Remember that an HTML control (our editor container) can be have their "overflow-y" CSS rule in "auto", and, doing this, we can control the position of the HTML control in a more accurate way, since everything that go "beyond" that position, is "hidden" but available in the HTML control by using their scrollbar.

Hello Peter,

Unfortunately, it's not as easy as can appear. The point is that this kind of editor made various changes and add certain style in the HTML that break the app's layout. But it's a question of a bit of CSS? Well... not really... for example, if you replace the editor inicialization code by this other:

... we (apparently) avoid the "wrong position" of the editor, which, probably we wanted in the place of the original textarea. But, if you try the above code, even when apparently works... certainly don't work completely as expected, or, some other issues appear.

And this require more time in order to check what can happen... or maybe look for another possible editor, maybe more friendly for us. Or maybe we must try to avoid the usage of a textarea... and try to use an HTML control, since this editors works also in this way.

Let me to try to take a look, Peter... if I have some time tomorrow I will try to test more editors (since I already try some of them...) and how can be the best way to achieve it, probably by using an HTML control... but this is mental note to me too... because probably this can be a better approach (for us, at least) than use an existing Textarea.

Hello Harald,

It's difficult to say... maybe the designer component, maybe others, experiment some unexpected behaviour: App Builder has not been designed to work in touch screens, and, even when the adaptation can be painless for "simple" programs (due to the good work of the Microsoft Windows and Delphi teams, in this case), probably, it's not easy to adapt something more complex to be used in touch screens, except if we take care about all the possible issues from the scratch. But I think this is not really required for App Builder... and in fact I can't try it here in a real touch screen, so double difficult in order to try it in a real environment and look for possible solutions for the possible issues.

Hello Harald,

Thanks for sharing. :-)

Did you know about the Javascript plugins for App Builder? Maybe can be interesting to you!

Anyway, thanks again for sharing it with us. :-)

Hello Harald,

Sure. It's possible to write code like the above, and using the function's result:

Both are the same. Except maybe that your one don't set the "isPWA" variable if the condition don't allow. So maybe you finally write a code like the below one:

Which is also good... however, if the "pwaPlatformPWA" function return "true" or "false"... then maybe use the function's result directly can be better, don't you? Finally we only need the below line of code:

However, even the above can be discussed... because, is that code more legible than the previous one? That is, reading the previous one code we can deduce that the function result is a boolean one, and, we know what the variable "isPWA" in any case. On the contrary, this last line of code don't tell us what finally the "isPWA" variable is... yes... it's the result of the function... but what result it is?

Maybe adding a comment line above the code... so it's our choice! :-)

Hello to all,

Here is a new DecSoft App Builder release, with the below changes, fixes and enhancements:

Read the entire product's history