To me, yes.I understand that it is only an error that affects only the Drawer Navigation of the DesignSupport library, right?
With B4XPages, we already have nearly 99% one code base.B4X will be more better if one code base (Like Flutter, Xamarin)
I am not very familiar with other platforms either, but I am very familiar with B4X, and I am very clear that the effort to portray B4X is insurmountable<off topic>
Xamarin is not cross platform at all. Only Xamarin.Forms which is very limited. Flutter provides its own UI layer and I'm not familiar enough to say how easy it is, to access platform specific features (and there are many in each platform).
There are advantages and disadvantages for each approach. B4X tries very hard and actually succeeds in allowing developers to access all the features easily, even if they are not available in other platforms.
Example of a complex app where 99% of the code is shared: https://www.b4x.com/android/forum/t...todon-pleroma-social-networks.124214/#content
</off topic>
For further discussion about cross platform, please start a new thread.
Don't forget that B4X deploys apps onto Android and iOS devices natively with absolutely no extra dependencies.B4X will be more better if one code base (Like Flutter, Xamarin) I know B4X Pages Option. Just My WishThank you for B4X.
nice small spiderDon't forget that B4X deploys apps onto Android and iOS devices natively with absolutely no extra dependencies.
Look at the screenshot below. The comparison is based upon a test app created in XF that simply creates/uses a SQLite database
and presents the data in a scrollable list view.
View attachment 109940
I'm sorry for going off-topic, but I'm sure that Erel will forgive me just this one time![]()
I created my-release-key.jks and upload_certificate.pem following instructions. Where should i place them, in order conditional release "find" these files in order to upload new app (.aab format)?A new attribute named #SignKeyAlgorithm was added together with a new automatic conditional compilation symbol - AAB, they can be used in cases where the AAB signing key is different than the standard key. This is relevant for new apps:
B4X:#if AAB #SignKeyFile: my-release-key.jks #SignKeyPassword: xxxxxxx #SignKeyAlgorithm: -digestalg SHA1 -sigalg SHA256withRSA #end if
I created my-release-key.jks and upload_certificate.pem following instructions. Where should i place them, in order conditional release "find" these files in order to upload new app (.aab format)?
Better to start a new thread.However it looks different. Colours are more vibrant, Labels that were black are now white, Top of screen where time and phone reception battery etc is has change from blue to orange?
I don't know why?
Wherever you like. You can set the full path in #SignKeyFile.I created my-release-key.jks and upload_certificate.pem following instructions. Where should i place them, in order conditional release "find" these files in order to upload new app (.aab format)?
Could it be the new SDK 30?Thank you for latest B4X which I have loaded tonight and compiled my app fine.
However it looks different. Colours are more vibrant, Labels that were black are now white, Top of screen where time and phone reception battery etc is has change from blue to orange?
I don't know why?
Please start a new thread and provide more information. Note that nothing prevents you from using the old version.Now I can't open my application when I compile in the new version and I can't compile in the old version anymore.
It is the wrong place.I not sure if this is a right place