Thread: [CEDET-devel] Android support current status
Brought to you by:
zappo
From: <pa...@sd...> - 2014-02-23 12:15:37
|
Hi everybody! What's the current status for the Android support? Reading from lisp/cedet-android.el, it seems to be that development is currently blocked and I'm very interested in enhancing this mode. Given that the Android world is shifting towards Gradle, my first wish would be to implement Gradle support in cedet-android. I plan to use https://github.com/slp/Telegram as my testing project, and what I want to reach as a first milestone is to pair with remvee android mode (https://github.com/remvee/android-mode) usability features (love that keybindings, although I'd eventually implement a single keybinding to do everything needed until my latest source code is running on my device/emulator). By current status I mean: 1. Blocking issues not evident from raw source 2. Next steps based on the structure of the code 3. Communication channels with people currently involved on this. Thanks for reading! Hope you enjoy your Sunday |
From: Eric M. L. <er...@si...> - 2014-02-25 23:35:00
|
On 02/23/2014 07:15 AM, Parménides GV wrote: > Hi everybody! > > What's the current status for the Android support? > > Reading from lisp/cedet-android.el, it seems to be that development is > currently blocked and I'm very interested in enhancing this mode. > > Given that the Android world is shifting towards Gradle, my first wish > would be to implement Gradle support in cedet-android. I plan to use > https://github.com/slp/Telegram as my testing project, and what I want > to reach as a first milestone is to pair with remvee android mode > (https://github.com/remvee/android-mode) usability features (love that > keybindings, although I'd eventually implement a single keybinding to > do everything needed until my latest source code is running on my > device/emulator). > > By current status I mean: > 1. Blocking issues not evident from raw source > 2. Next steps based on the structure of the code > 3. Communication channels with people currently involved on this. > > Thanks for reading! Hope you enjoy your Sunday Hi, Android "support" in CEDET is more than just cedet-android.el. The listed file contains only the Emacs interface for interacting with the external tools that compile, query, debug, etc your android project. Additional android support is in cedet/ede/android.el. This code identifies an android project, and sets things up so EDE commands such as compile, debug, etc all work. It also reconfigures internal java settings so that Semantic can do smart completion on your java source code. At the moment, I think I'm the only person who occasionally writes Android programs (as a hobby) and also maintains this android support. Based on your brief description of a shift to Gradle which I know nothing about, here is my recommendation: First: Decide if the new commands you need to support are an extension of, or independent of the ADK. That determines if you need to extend cedet-android, or create cedet-gradle, or maybe it is simple enough to just be a string input when calling 'compile'. Second: Create a new EDE project, independent of android.el. Maybe ede/gradleandroid.el or something. You can probably start with android.el and just hack up the project identification piece. It may be you can subclass android.el (via the class ede-android-project class) and overload just a couple things. That would maximize code reuse and future maintenance. By creating a new EDE project, the old one will continue to work for old-timers, and anyone using the new system will get the new tools, and all the keybindings, etc will remain the same for everyone. I think the only blocking issue is that I don't do enough android development to know what might be a blocking issue. Lastly, if you dig into writing source code, you will need to sign a release for your contributions to CEDET so that it can be later merged into Emacs. Thanks! Eric |