With a lot of Android projects available on the internet now being written in Android Studio, I decided that it was time I looked at it. I can't remember the learning curve for Eclipse (so it probably wasn't huge), and I only use it infrequently for wrapping and testing the odd library, but I have spent the best part of a day trying to get a small library downloaded from the internet working in Android Studio.
Not only do we have to write or wrap or amend the code, we also have to deal with the building of the output files. While I recognize the complexity of these processes, and the tool provided (Gradle) does make sense (eventually), it's still a big learning curve to do anything but a simple compile of a project.
Thankfully in B4x, Erel protects us from this type of requirement. I'm sure it's the same with XCode but I have never built a native Xcode project, so I can't be sure.
All we have to worry about with B4x is getting the code right and pressing a button and it takes care of the rest for us.
Another opportunity to say a big thank you to Erel for this great development environment. Long may it continue and develop. (But please never make Gradle or similar a requirement)
Not only do we have to write or wrap or amend the code, we also have to deal with the building of the output files. While I recognize the complexity of these processes, and the tool provided (Gradle) does make sense (eventually), it's still a big learning curve to do anything but a simple compile of a project.
Thankfully in B4x, Erel protects us from this type of requirement. I'm sure it's the same with XCode but I have never built a native Xcode project, so I can't be sure.
All we have to worry about with B4x is getting the code right and pressing a button and it takes care of the rest for us.
Another opportunity to say a big thank you to Erel for this great development environment. Long may it continue and develop. (But please never make Gradle or similar a requirement)