Friday, March 30, 2012

Donations update

My huge thanks to all those folks who made a donation to this project. There are less than 10 of them and the average amount is smaller than 15 EUR. All these contributions are appreciated.

I see that some people are not happy and do not see that there ain't no such thing as a free lunch but I do not mind. As you can see there are some updates to keep the plugin uptodate. And there are people who report their real problems and I am trying to address at least some of these. Recently we had some fixes in the area of classpath handling because the latest SDK tools release brought some interesting changes again.

There are few ideas what to do next to improve the plugin:

  • Add layout preview functionality. Eclipse has GUI editor for layout and IntelliJ has at least preview. We can get on par with IntelliJ.
  • Better XML editing. Basic Java support work but all these special XML files are what makes Android development different from usual Java coding.
  • Lint integration. 
  • Maven support.
  • Many smaller things around device control, logcat support.
  • Better testing support. The one that we currently have is pathetic.
I had a vague promise to get help on the first and the third items (XML preview and Lint) but nothing material is available. It can be the best to ignore them and just write it from scratch.

Maven support is not likely to be addressed by me. I am free to help but I am not Maven fan boy.

Yet I am busy most of the time. Contributions are welcome.

4 comments:

  1. gracias por desarrolar NBAndroid, soy desarrolador Java y futuro desarrollador Amdroid. no puedo contribuir ya que solo soy estudiante bolivianom, quisiera ayudar en algo, para el editor GUI.
    bye

    ReplyDelete
  2. Some other idea:

    - Build an gui editor for the manifest file. Permissions, sdk versions, features could be changed via GUI and not in the Manifest file.

    - No offence: the documentation could need a bit more work. I tried to look into the source code of the project, so that perhaps I could do what I can, to help a bit with some smaller issues.. and somehow felt lost. I started here (http://kenai.com/projects/nbandroid/sources/stable/show) and didn't even know what parts of the project exists, and just clicked around a bit. So imho it would be very great if there would be some kind of general code overview, or something similiar.

    ReplyDelete
  3. Re manifest GUI editor: I commented the bug in our JIRA.

    Re docs: I agree that there is a big space for improvements. If anyone wants to write some resources I can put them on web. Even better would be to give someone access and let them fix this. Or build the website for nbandroid from scratch to match current state.

    ReplyDelete
  4. Hi there,

    Im a developer and teacher in Android development.
    Here are some comments based on the >300 students I've had.

    Re manifest GUI editor: Everyone edit it by hand, by copying and pasting. I don't think an editor is neccesary.

    BUT a check if the activites/services etc in the manifest matches the java classes and if it conforms to the XML Schema would save us TONS of time!



    I really really think a visual layout editor, however simple, is THE main missing feature for much much bigger general adoption of nbandroid.
    I know it sounds ridicolous as experienced developers barely use the visual layout editor.... but: All NEWCOMERS to Android development (including my students) needs it (or think they need it) and therefore simply must choose Eclipse.
    Afterwards they stick to eclipse, of course.


    So... if there was just the tinyest most basic visual layout editor integrated in Netbeans then all newcomers could start on Netbeans and that would give a HUGE amount of users.

    Believe me, as a teacher Ive tried to promote nbandroid a lot, but it is a stumbling block that all that would prefer Netbeans have to install and use eclipse also (or use DroidDraw).

    ReplyDelete