Hi.

1. Does it come with FULL source code?

2. If yes, is it commented in English?

Regards

Abe 

Hello,

3 hours ago, Abe said:

1. Does it come with FULL source code?

No, we provide source code for crossplatform units and iOS/Android API headers.

3 hours ago, Abe said:

2. If yes, is it commented in English?

Yes, Most of the code has XML-docs. However, it's in russian right now. But we export this documentation on https://docs.fgx-native.com/ So techincally you can use auto-translation tool.

Thank you.

On 1/2/2023 at 6:52 PM, Yaroslav Brovin said:

No, we provide source code for crossplatform units and iOS/Android API headers.

Sorry for the dumb questions, I'm currently looking into FMX Native as a complete newbee.

If above is NO: What exaclty is missing then, are these missing files the source-code of the specific IDE designer, needed to develop, or are there some binary files needed, or what else is missing then?
Can I work still without those missing files, by recreating them anyhow like new iOS/Android headers, or will it come to a full stop, after a subscription ended?

The whole FGX Native, to better understand, is this a complete separate, parallel foundation, not based on FMX, or is it building up from the FMX foundations, by just adding components?

I have read about Flexbox/CSS support, does that mean the FGX foundation is based perhaps web/browser technology, instead of traditional FMX?
Where can I find more information on the underlying basics of the system, if this differs much from FMX.
 

 

Hello @Rollo,

Quote

If above is NO: What exaclty is missing then, are these missing files the source-code of the specific IDE designer, needed to develop, or are there some binary files needed, or what else is missing then?

Lets consider FGX Native as set of different files:

1. IDE designers. This part is closed, so no any sources in this part. So we distribute set of bpl and dlls for each supported Delphi versions 11.0 - 12.*.
2. Implementation of FGX Native for Android and iOS. The implementation can be considered as:
   1. Crossplatform units (it describes all components and controls and their API). Other words, it includes all code, which works on iOS, Android. We distribute it and binary versions for 11.0 - 12.*. For example FGX.CollectionView:
      
   2. Platforms implementations of all components for Android and iOS: FGX.CollectionView.Android and FGX.CollectionView.iOS. This part is closed. So we distribute binary versions of this units.
   3. Platform API headers: iOS API, Android API. We provide sources of all available headers. If you need additional headers, you can generate it via our provided tools Java2Delphi (for Android) or Octoid (for iOS).
   4. Set of additional AAR libraries (Android) and external iOS frameworks (iOS). We provide binary versions only. 

Don't worry, You will be able to develop applications and, if desired, make your own components. If you have any questions about this part, you can always contact me for help.

Quote

Can I work still without those missing files, by recreating them anyhow like new iOS/Android headers, or will it come to a full stop, after a subscription ended?

Sure, You can continue to use FGX Native after subscription ended. The subscription gives you the opportunity to receive updates and technical support on the forum. So all the versions that you received while you had a subscription remain with you and you can continue to use them.

Quote

The whole FGX Native, to better understand, is this a complete separate, parallel foundation, not based on FMX, or is it building up from the FMX foundations, by just adding components?

it is a completely independent framework, like VCL or FMX. It has its own unique set of components, core, and more. There is something similar in the API, but there are also differences.

Quote

I have read about Flexbox/CSS support, does that mean the FGX foundation is based perhaps web/browser technology, instead of traditional FMX?

Yes and No. We don't support CSS. But we support subset of FlexBox for alignment system. All our components a native based. It means, it uses native views and Android and iOS like a VCL on Windows. FMX implements and draws each component itself. Therefore, in FGX Native, the components look and work like native OS ones.

Quote

Where can I find more information on the underlying basics of the system, if this differs much from FMX.

I'm not sure. that we have information about it in one place. Because in general, users use our components and sometimes request access to native components. For example, if our component doesn't have any functionality, but the native one does (from the Operating System), then the user can theoretically get direct access to the View and work with it.

Thank you,
Yaroslav