search

NBANDROIDTEAM / NBANDROID-V2

Netbeans Android support plugin
Apache License 2.0
94 stars 25 forks source link

The future of the project (Layout Designer, Maven and Ant support, NDK) #195

Open arsi-apli opened 5 years ago

arsi-apli commented 5 years ago

I'm starting to think about where to direct this project further.. If I tell the truth, I can't handle Layout Designer. I am a system programmer and graphics are not my strengths. And the available projects are terribly old and simple. And according to my experience, when I created something in Designer from AS, it looked completely different after starting the application and I always finished with editing the xml. My suggestion is to add a component palette through which you will be able to add respective XML code. And add a Theme Editor to Layout preview.

And then we have Gradle, it doesn't belong to my favorite systems and would like to return Maven and ANT. I found this project https://github.com/wldomiciano/android-app-without-gradle and apparently it will not be so difficult. I have no problem to write Maven plugin. I have no experience with Ant, I will need help there. And maybe @wldomiciano could help us, certainly knows more about building an android app outside Gradle than me.

And the last thing is NDK support, we will have to wait until Cpp modules are donated to Apache netbeans.

Chris2011 commented 5 years ago

I'm starting to think about where to direct this project further.. If I tell the truth, I can't handle Layout Designer. I am a system programmer and graphics are not my strengths. And the available projects are terribly old and simple. And according to my experience, when I created something in Designer from AS, it looked completely different after starting the application and I always finished with editing the xml. My suggestion is to add a component palette through which you will be able to add respective XML code. And add a Theme Editor to Layout preview.

IMHO, leave it as it is. You don't need to be a designer but that stuff is important for a lot of people who are visual thinking persons etc. So atm we have a good preview, didn't test it yet but soon I will and thats good as it is for now. Later one someone else can enhance it. A first nice to have was to move the components around on the preview but if it is not coming for now, thats also fine.

And then we have Gradle, it doesn't belong to my favorite systems and would like to return Maven and ANT. I found this project https://github.com/wldomiciano/android-app-without-gradle and apparently it will not be so difficult. I have no problem to write Maven plugin. I have no experience with Ant, I will need help there. And maybe @wldomiciano could help us, certainly knows more about building an android app outside Gradle than me.

You only mean using gradle for the plugin or gradle inside of the plugin? IMHO when I start to create a AS application, gradle is defacto standard there and it is more modern. Someone likes it, someones not but it should fit in the needs of the developer too and not being ignored.

If you only mean to rewrite the plugin in maven thats also fine. If you mean to get the choice from the developer which creates a Android app, I wouldn't recommend that. Maybe make it optional. Gradle as first level support and maven as an option for those who don't want to use gradle.

And the last thing is NDK support, we will have to wait until Cpp modules are donated to Apache netbeans.

So whats the problem? Don't do it, until we have the donated code :)

Chris2011 commented 5 years ago

Next thing could be the Proguard thing. With the newest AS studio, they added another obfuscater called R8: https://android-developers.googleblog.com/2019/04/android-studio-34.html

arsi-apli commented 5 years ago

Next thing could be the Proguard thing. With the newest AS studio, they added another obfuscater called R8: https://android-developers.googleblog.com/2019/04/android-studio-34.html

R8 is now the default code shinker for new projects created with Android Studio 3.4 and for projects using Android Gradle plugin 3.4 and higher.

obrázok So no problem...

If you only mean to rewrite the plugin in maven thats also fine. If you mean to get the choice from the developer which creates a Android app, I wouldn't recommend that. Maybe make it optional. Gradle as first level support and maven as an option for those who don't want to use gradle.

Independent plugin for Maven. Only SDK tools would be used.I think it is quite a good thing for developers like me from old school...

Later one someone else can enhance it.

;)))) Please, do not show interest all at once.

Chris2011 commented 5 years ago

I really would like to jump in into this project to help but atm I have other prios but I give my best to comment and give proposals. That's all atm what I can do :). You are doing a great job, really. I think a lot of people will appreciate your work.

Independent plugin for maven.

So you only mean the architecture of your project, right? Not using maven inside of your plugin like creating n android project -> with gradle and another plugin with maven. That wouldn't make sense for me to have 2 plugins which makes the same but only for using different building tools inside of the plugin. So that's why I think it would be better to have one plugin which have options to create a maven based android project or a gradle based android project. My 2 cents.

arsi-apli commented 5 years ago

The same NBANDROID but with added support for maven. Used Maven subsystem from ANB. And for that a plugin for Maven is needed. Of course, I have to complete the current stuff first. This will be on the next year's schedule. But it is already necessary to think about it by APIs

mweisshaupt1988 commented 5 years ago

Would it be desirable if the Plugin would be integrated into the main NetBeans sourcetree?

I think it would be a good idea to integrate the core components and provide extra components like the layout designer for example as additional plugins. This way the workload for maintaining the plugin could be distributed to more people and more time could be spend on new features and improvements.

arsi-apli commented 5 years ago

First of all, all issues need to be completed. Then I need to rename the packages to Netbeans namespace. And I don't know if there will be a problem with the imported source code from Android Studio. It's under Apache license. But with my Translator English, the discussion will be difficult.. And it is necessary to test everything properly. If it is part of ANB, I probably won't be able to do 10 PRs a day ;)

arsi-apli commented 5 years ago

Would it be desirable if the Plugin would be integrated into the main NetBeans sourcetree? See the thread "Apache NetBeans Gradle Patch 1 Release" on ANB dev mailinglist. So adding NBANDROID to the Netbeans source tree wouldn't be the best idea. This project is still in development and it would mean a lot of problems..

arsi-apli commented 5 years ago

The project has reached the first one hundred installations. That's one small step for a man, one giant leap for NBANDROID-V2 ;))) I would like to thank the Apache NetBeans team for advertising this plugin! obrázok

obrázok

Chris2011 commented 5 years ago

Wow, cool :) You are amazing :) keep up the great work.

acuilab commented 5 years ago

really amazing!

patoessy commented 5 years ago

Wow, installed this plugin and you are really amazing. Keep it up.

arsi-apli commented 5 years ago

@geertjanw I would like to ask you for info in what state is ANB maven repository. What we are currently using is canceled https://repository.apache.org/content/repositories/orgapachenetbeans-1011 I found a new one https://repository.apache.org/content/repositories/public https://repository.apache.org/content/repositories/releases But they have changed group id from org.apache.netbeans to org.netbeans.
Which one should I use and is it the final version? Thanks!