[Anton]

Hello,

Learning now how to build mobile app. with QT/Felgo, and have a questions:

1. I’m using the latest QT creator (4.14.0 community) / QT6
   I have downloaded and installed Felgo SDK and it was installed as another one QT creator 4.11.2 community / QT5
   Now I have 2 QT creators.
   Have tried to maintenance Felgo repositories to 4.14.0 with the maintenancecomponents.exe (of the latest QT creator) – have selected Felgo, it was successfully downloaded, but on start was dependency errors, and no live server available, and unable to load the samples, and so on, so I have uninstalled Felgo SDK from there and still using the 2nd QT creator provided by Felgo.
   So, for now is it possible to setup Felgo SDK into the currently installed the latest Creator?
   
2. Is it possible to call from Felgo UI components c++ methods? I.e. I would like to build UI in the 1st project, and to build c++ business logic in the separate 2nd project as a library. Is it possible and is this approach good? (I just have spent my 10+ years in .net / visual studios)
3. The license: if my Indie license expired, and pluging in the applications are licensed (i.e. push notification plugins that is currently requires at least Indie license but not free licence) this plugins will active in the application installed later, and in a new installations?
4. I have setup Android SDK and NDK in Felgo QT Creator (the same as for te latest QT creator) and it was valid. But no armeabi build is available. The latest QT creator can privide armeabi build. Do you have the documentation how to setup an environment to build Android app? And as far as I understood, to build IOS apps need XCode only (and to select IOS platform is only available on Felgo SDK IOS installer) is it true?

Thank you!

[Anton]

and also: if possible to call c++ methods from UI, how about Felgo Live? Will the library (with c++ methods) be uploaded to the device, or Felgo Live just uploads QML markup / resources?

 

Thank you!

[Anton]

I just fixed double QT creator problem and Android NDK.

First of all need to know that the current Felgo SDK supports QT 5.13.2 only.

So the steps:

1. I’ve opened my the latest QT creator (4.14.0), search in marketplace – Felgo, completed purchase for free, closed QT creator and started maintenancetool.exe to add the components
2. Checked to setup Felgo there, and checked to setup an additional QT version 5.13.2 (mingw compiler, Android precompiled libs)
3. After setup is finished – need to start QT Creator, check kits, create a new Felgo empty project – it worked as a charm even with Live server on my Iphone.

And after just need to delete the prev. installed standalone Felgo SDK with a different QT Creator: go to its folder and start maintenancetool.exe to delete them all, that’s all

In this case, Felgo SDK will run under QT 5.13.2 and ander QT Creator 4.14.0

And according that into this QT creator I have setup Android environment later – an app. is build under Android successfully.

[Anton]

for now how all the questions except licensing is clear for me.

but the provided use-case with license expiration can’t find …

[BenceFelgo Team]

Hi Anton,

Regarding your question on licensing: Once your license is expired, your published app will continue to work as expected, including plugins, however, you will not be able to update it in the app stores.

Best,

Bence

[Anton]

Bence thank you for your response. Why will not be able to update it in the app stores? The plugins of the new built versions will not be able to run (i.e. no messaging) or what the restriction about an app. update do you mean?

[AlexFelgo Team]

Hi Anton,

quickly jumping in here. As Bence mentioned, if your license expires, your published app will not be affected at all. Also the licensed plugins will kepp working.

The point he brought up about updating is: If your license expires, you will not be able to build another version of the app that includes the paid plugins. So unless you renew your license, you will not be able to update your app including the same functionality, since you will only be able to use features of the free personal license. Again, this does not effect the published app version that already is avaialable in the stores.

I hope that is clears up this question?

Best,
Alex