Hi Fam!
There has been a lot of strategies employed to manage the b4x library update process.
What if b4x developers had to add the exact #DownloadURL of their libraries in the manifest file? This could provide useful for un-assumed exact locations.
For example, usually the first post of a thread usually has one or more b4xlib uploaded by the developer, some developers release their libraries on github / google drive etc depending on whats possible.
In the b4xlib code...
This content is used in the manifest, now including the DownloadURL
#KeepingAnOpenMind.
There has been a lot of strategies employed to manage the b4x library update process.
What if b4x developers had to add the exact #DownloadURL of their libraries in the manifest file? This could provide useful for un-assumed exact locations.
For example, usually the first post of a thread usually has one or more b4xlib uploaded by the developer, some developers release their libraries on github / google drive etc depending on whats possible.
Advantages
- Self-describing artifact
- Library knows where it lives
- IDE doesn’t need external registry for updates
- Decoupled distribution
- Developers can host anywhere (GitHub, CDN, private server)
- Supports automation
- CI/CD can update versions and publish automatically
- Version truth consistency
- Version + download source tied together
In the b4xlib code...
B4X:
#LibraryName: MyCoolLib
#Version: 1.2.3
#Author: John Doe
#DownloadURL: https://example.com/mylib/latest.zipThis content is used in the manifest, now including the DownloadURL
#KeepingAnOpenMind.
