We don't need to edit xml layout and Jetpack Compose.
We don't need to know Java and Kotlin.
We don't need to know Java patterns.
It's easier to work with cross platform.
We don't need to edit xml layout and Jetpack Compose.
We don't need to know Java and Kotlin.
We don't need to know Java patterns.
It's easier to work with cross platform.
Ever since the beginning of Android it was clear that it is an over-engineered OS. Many clever Google developers did their best to create very innovative and sophisticated solutions to (sometimes) non-existent problems. The mess related to Activities and Services is the result of this and one can see how their behavior changes with each Android version.
There is a relatively big change in front of us, related to the way apps need to respond to screen size changes. The advantage is that it will make the behavior of B4A more similar to B4i and B4J, however the transition will introduce some challenges.
There is a relatively big change in front of us, related to the way apps need to respond to screen size changes. The advantage is that it will make the behavior of B4A more similar to B4i and B4J, however the transition will introduce some challenges.
You mean for B4X developers?
For me, I am willing to move on and learn the curve.
As example, it used to be difficult to understand B4XPages but now I like it. Furthermore, there are alternatives if one doesn't want to use it.
My crystal ball shows:
- single process- single activity always running (it goes automatically in backgroud when another app is launched and eventually it gets killed by OS when needed)
- no more services (the breaking change) as we know them
- limited changes in B4XPages events
- something new about Home Widgets
My crystal ball shows:
- single process- single activity always running (it goes automatically in backgroud when another app is launched and eventually it gets killed by OS when needed)
- no more services (the breaking change) as we know them
- limited changes in B4XPages events
- something new about Home Widgets
True..
Erel is like a microprocessor! he does all the work for us internally (registers, RAM, ROM, pointers, Java,...etc) and gives us the pinout to interface our BASIC code!
Maybe time to create a Suite, and have all 4 IDE launch from a common interface?
it makes more than sense to me now that all 3 IDE's have/create folders to the other IDE's...
SO, if a B4A project creates a B4J and B4i folder, "changing" IDE's should be easier than having to launch a new one, at the risk of changing code in one IDE that may be "forgotten" by the other open IDE