R RichardN Well-Known Member Licensed User Longtime User Dec 11, 2018 #1 I have a number of apps designed to work in a non-internet environment where the update of file assets OTA is not practical. These apps have a selection of common files (mostly sqlite.db) that are delivered in the package via the project \files folder when an update is compiled. It is frankly a bit of a pain to maintain multiple up-to-date copies of each in their respective \files folder over several projects and it is easy to lose track of which database version is the latest when copying files manually. It would be very beneficial to have a means (perhaps via a code meta-tag) that automates the copying of an asset file (comparing the dates) from an absolute location where the master copies lies. The asset would be refreshed every time a compilation takes place where the nominated asset is found to be newer, thus ensuring the latest version of an asset is packaged. If the named file is the same as the one in the \files folder.... no action. Something like: Code: Copy #IncludeUpdatedProjectAsset: "c:\AbsolutePath\ProjectAsset.db"
I have a number of apps designed to work in a non-internet environment where the update of file assets OTA is not practical. These apps have a selection of common files (mostly sqlite.db) that are delivered in the package via the project \files folder when an update is compiled. It is frankly a bit of a pain to maintain multiple up-to-date copies of each in their respective \files folder over several projects and it is easy to lose track of which database version is the latest when copying files manually. It would be very beneficial to have a means (perhaps via a code meta-tag) that automates the copying of an asset file (comparing the dates) from an absolute location where the master copies lies. The asset would be refreshed every time a compilation takes place where the nominated asset is found to be newer, thus ensuring the latest version of an asset is packaged. If the named file is the same as the one in the \files folder.... no action. Something like: Code: Copy #IncludeUpdatedProjectAsset: "c:\AbsolutePath\ProjectAsset.db"
Erel B4X founder Staff member Licensed User Longtime User Dec 11, 2018 #2 It will be better supported in the next version of B4A.
R RichardN Well-Known Member Licensed User Longtime User Dec 11, 2018 #3 Thanks Erel. Naturally a lot of the benefit in maintaining a central repository of assets will be felt by developers who are publishing the same application in both Android and iOS.... so to have the facility in both would be ideal.
Thanks Erel. Naturally a lot of the benefit in maintaining a central repository of assets will be felt by developers who are publishing the same application in both Android and iOS.... so to have the facility in both would be ideal.
Erel B4X founder Staff member Licensed User Longtime User Dec 12, 2018 #4 RichardN said: Thanks Erel. Naturally a lot of the benefit in maintaining a central repository of assets will be felt by developers who are publishing the same application in both Android and iOS.... so to have the facility in both would be ideal. Click to expand... Another possible method that is currently available: https://www.b4x.com/android/forum/threads/xui2d-cross-platform-tips.96815/
RichardN said: Thanks Erel. Naturally a lot of the benefit in maintaining a central repository of assets will be felt by developers who are publishing the same application in both Android and iOS.... so to have the facility in both would be ideal. Click to expand... Another possible method that is currently available: https://www.b4x.com/android/forum/threads/xui2d-cross-platform-tips.96815/
