Posts by DecSoft

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.

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 to all,

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

Read the entire product's history

Good to know it Paolo. :-)

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.