corwin42 Expert Licensed User Longtime User Nov 3, 2016 #1 http://android-developers.blogspot.de/2016/11/support-ended-for-eclipse-android.html Hopefully this will have no impact on B4A development and libraries development...
http://android-developers.blogspot.de/2016/11/support-ended-for-eclipse-android.html Hopefully this will have no impact on B4A development and libraries development...
moster67 Expert Licensed User Longtime User Nov 3, 2016 #2 RIP Personally I've been using Android Studio for quite some time together with Erel's compiler tool. Works without any problems as long as you add the B4A-libraries to your project. Also for JAVA, I stopped using Eclipse in favour of Intellij.
RIP Personally I've been using Android Studio for quite some time together with Erel's compiler tool. Works without any problems as long as you add the B4A-libraries to your project. Also for JAVA, I stopped using Eclipse in favour of Intellij.
corwin42 Expert Licensed User Longtime User Nov 3, 2016 #3 moster67 said: RIP Personally I've been using Android Studio for quite some time together with Erel's compiler tool. Works without any problems as long as you add the B4A-libraries to your project. Also for JAVA, I stopped using Eclipse in favour of Intellij. Click to expand... A few months ago I gave Android Studio a try to develop the AppCompat and DesignSupport libraries. I was not satisfied with the workflow and setting up a project in AS was quite complex, even if it is much easier to add the support repository libraries. Maybe I give it a new try again in the next days.
moster67 said: RIP Personally I've been using Android Studio for quite some time together with Erel's compiler tool. Works without any problems as long as you add the B4A-libraries to your project. Also for JAVA, I stopped using Eclipse in favour of Intellij. Click to expand... A few months ago I gave Android Studio a try to develop the AppCompat and DesignSupport libraries. I was not satisfied with the workflow and setting up a project in AS was quite complex, even if it is much easier to add the support repository libraries. Maybe I give it a new try again in the next days.
Erel B4X founder Staff member Licensed User Longtime User Nov 3, 2016 #4 The Android Developer Tools are not needed for libraries development. Libraries are made of regular Java projects.
The Android Developer Tools are not needed for libraries development. Libraries are made of regular Java projects.
corwin42 Expert Licensed User Longtime User Nov 3, 2016 #5 This is true for 99% of the projects. But there are exceptions. AppCompat and DesignSupport are actually Android library projects.
This is true for 99% of the projects. But there are exceptions. AppCompat and DesignSupport are actually Android library projects.
