With reference to this page https://www.b4x.com/android/forum/t...framework-for-managing-multiple-pages.118901/
It would be really nice if it is clearly mentioned about things b4xpages can not do.
It will save a lot of time by avoiding hit and trial.
For example:
It would be really nice if it is clearly mentioned about things b4xpages can not do.
It will save a lot of time by avoiding hit and trial.
For example:
- Appcompat will crash on compile with b4xpages ( recommended by Erel to avoid appcompat with b4xpages in a different thread)
- Toolbars need to be fixed and its not a simple replace x with y. Entire method, parameters etc are different
- Any Library dependant on appcompat will have issues
- Even if compilation happens the app crashes without anything loading ( Issues with reflection in code)
- A lot events will require Delegation. Not much explanation available