moamoa
|
Posted: May 12, 2009 21:12 by moamoa
|
|
Hi, I am just wondering if this project is being seriously developed? I don't want to take anything away from the excellent work that has been done to date, but there does seem to be little activity on this project. I am a netbeans user for a long time and want to start looking at android. However, I will need to squeeze this in with my day job, so don't really have the time to try and learn android via a plug-in that also may not work fully. I do not really want to use eclipse as I like netbeans better, but unless the netbeans plug works well, I don't see much choice. Can someone please give me an honest heads up on the status of this project? Is there any time frame for getting a full 1.5 compatible plug-in working? Thanks. |
What is the status of this plugin?
3 posts
Replies: 2 - Last Post: May 16, 2009 08:17
by: moamoa
by: moamoa
showing 1 - 3 of 3
|
jcpalmer
|
Posted: May 15, 2009 15:35 by jcpalmer
|
|
It seems pretty obvious that paddles might be necessary to right the ship. I am trying to include other projects in my Android project, which is similar to your library. I have older posts, and a feature request regarding this. I have adopted a third option to either this plug-in or eclipse, described below. The main advantage being you avoid the extremeness of switching to eclipse, while working on 1.5 without any drama. You could switch back to the plug-in in future. The option is to add the android.jar for all versions you wish to develop for as Netbeans libraries. Create a Nebeans library, and add it to your Netbeans. Now you can write any android code you wish, and even compile it in Netbeans, if you want. If you build a jar of the android source and add to the Netbeans library, then you can have sub-second access to any android method or class, and enhanced code completion. I will describe that in a separate topic soon. You can easily build/run you code with a directory of small scripts, you can just double click: (MS-DOS Version) First to use 1.5, you have to create at least one "AVD". You only have to do this once File: createAVD.cmd ECHO OFF SET PATH=C:\android-sdk-windows-1.5_r1\tools\;%PATH% CALL android create avd -n my_android1.1 -t 1 -p c:\android\avd PAUSE A second one time script creates a directory structure for the external Android build tools. There is a libs directory created, where you can place your barcode jar. File: create_android_project.cmd ECHO OFF SET PATH=C:\android-sdk-windows-1.5_r1\tools\;%PATH% CALL android.bat create project --target 1 --path c:\android_project --activity MyActivity --package myPackage PAUSE Every time you wish build an APK, double click this script. I am building my Views dynamically with code, rather than with XML. If you are building with XML, you may have to adjust script. File: build.cmd ECHO OFF CD \android_project REM copy all source from Netbeans projects, let ant figure out what has changed XCOPY /Y /B /S \CVS_working_dir\project_1\src\*.java .\src XCOPY /Y /B /S \CVS_working_dir\project_2\src\*.java .\src CALL ant debug PAUSE If the Emulator is not currently running start with: File: start_emulator.cmd ECHO OFF SET PATH=C:\android-sdk-windows-1.5_r1\tools\;%PATH% STARTemulator -avd my_android1.1 -skin HVGA-L -no-boot-anim PAUSE If emulator is already started, you install your APK with: File: install.cmd ECHO OFF SET PATH=C:\android-sdk-windows-1.5_r1\tools\;%PATH% adb.exe wait-for-device install -r c:\android_project\bin\MyActivity-debug.apk PAUSE Finally to see you logging output, run: (adjust your log tags as necessary) (colonD makes a smileface) File: view_logs.cmd ECHO OFF SET PATH=C:\android-sdk-windows-1.5_r1\tools\;%PATH% adb.exe logcat MyActivity  *:EThis works during my development, however I really need to replace the build script with one that includes proguard to get all the dead code out of the final APK. I have failed so far to do this, and have stopped trying for now. I have seen a post which indicates it can be done however http://sourceforge.net/forum/forum.php?thread_id=3215098&forum_id=182455 |
|
moamoa
|
Posted: May 16, 2009 08:17 by moamoa
|
|
Thanks for just making be re-think before going down eclipse route. I did some thing like what you have done, but a little different. this works pretty well and lets you use the XML layout too as well as not needing bat files, which i find handy when following the examples; 1) create a project with the standard android tools; 2) create a new freeform java project in netbeans, using the project dir you just created 3) add src,res,gen folders from project to source directories 4) add android.jar and gen folder as source classpath 5) add these few things to the build.xml; <target name="build" description"build" depends="debug"/> <target name="install-it" description"install-it" depends="install"/> <target name="reinstall-it" description"reinstall-it" depends="reinstall"/> 6) in netbeans project settings (build & run) set commands for "build" to the build task and "install" to the "reinstall-it" task All done. Now you can just edit your main.xml and source files in netbeans. build your project from netbeans as normal and install it via net beans. I have actually set my run task to map to the reinstall-it task, as that suit me. were run puts it on emulator. btw, first time you need to run install-it, since the build task assume it is already there in emulator and is replacing it. |
Replies: 2 - Last Post: May 16, 2009 08:17
by: moamoa
by: moamoa
