What is the proper workflow for developing and debugging a NetLogo extension

Question

I am developing NetLogo extensions with Netbeans and I would like to get advice on the correct flow to optimize my code ... Usually I write code in NetBeans and then compile the extension in NetBeans using this add to my build.xml (I copy it here because it may be useful for someone):

<target name="-pre-init">
    <property name="project.name" value="myextension" />
    <property name="class.manager" value="org.nlogo.extensions.myextension.MyClassManager" />
    <manifest file="manifest.mf">
        <attribute name="Manifest-Version" value="1.0" />           
        <attribute name="Extension-Name" value="${project.name}" />
        <attribute name="Class-Manager" value="${class.manager}" />
        <attribute name="NetLogo-Extension-API-Version" value="5.0" />
    </manifest>
</target>
<target name="-post-jar">
    <delete file="manifest.mf"/>
</target>

at that moment I dragged .jar to the desired folder and open the NetLogo model from the terminal to find out if my extension is writing any material / error / something else ... since I'm not a computer scientist, I think that this is the right way to continue ... I know this works, but what if I need to see where my code is slow or memory is consuming? maybe I could optimize it with a debugger, but outside of NetBeans I don’t know how to do it ...

I would be grateful for the most commonly used workflows from expert developers ...

Regards, Simone

Answer 1

Great question. I am curious how others will respond.

, NetLogo. , , , :

ln -s /path/to/NW-Extension /path/to/Netlogo\ 5.0.x/extensions/nw

, , .

, , , , ?

VisualVM. , NetBeans, . JVM. , VisualVM NetLogo ( "Local Application pid 42138" - ). .

, . NetLogo ( 5.0.x). NetBeans, , NetBeans , . .

. NetBeans; sbt ( NetLogo ). . wiki, , .