Differences

This shows you the differences between two versions of the page.

--- 05_developer_tutorials:02_extending_groimp:creating-node-class [2025/01/31 14:13] – removed - external edit (Unknown date) 127.0.0.1
+++ 05_developer_tutorials:02_extending_groimp:creating-node-class [2025/11/21 16:43] (current) – gaetan
@@ Line 1: / Line 1: @@
+===== How to create a node class =====
+Creating an own Java node class is not difficult. The new class, say Cube, has to be a subclass of _de.grogra.graph.impl.Node_ or one of its subclasses. So we have to write something like
+<code java>
+import de.grogra.graph.impl.Node;
+public class Cube extends Node
+{
+}
+</code>
+However, we also would like our new cube to have a width-attribute. We add this in the usual way:
+<code java>
+public class Cube extends Node
+{
+    float width = 1;
+}
+</code>
+So far, this attribute is not registered with the UI and persistence mechanism of GroIMP. It will not be shown in the GUI, and it will not be saved or restored when a cube is written to or read from a data stream. We have to add special "comments" which are actually comments for the Java compiler, but read as input for the Perl script enhance.pl which is part of the Build project of the source distribution of GroIMP.
+<code java>
+public class Cube extends Node
+{
+    float width = 1;
+    //enh:field getter setter
+    //enh:insert
+}
+</code>
+The //enh:field// tag tells the script that the previously declared field has to be added to the persistence mechanism of GroIMP so that it is saved and restored as part of a cube. The tag also commands the script to create getter- and setter-methods. **It is important that the enh:field tag immediately follows the field declaration and is not split into several lines.** The //enh:insert// tag defines the location where the script shall insert the generated Java code. This has to be the last tag and should be placed at the end of the file. See [[:01_user_documentation:06_graph:07_persistence:99_code_enhancement|this page]] for more information on the code enhancer.
+=== Calling the code enhancer with Maven ===
+Project compiled with maven will automatically call the code enhancer and update the sources files.
+=== With ant ===
+The Perl script is invoked by the target //-src-enhance// of the Ant buildfile //buildproject.xml// in the Build project. This buildfile should be imported by the build.xml buildfile of every GroIMP project, and for projects which need source code processing by //enhance.pl//, the target //-src-enhance// should be invoked by the target //src// as in
+<code xml>
+<target name="src">
+    <antcall target="-src-enhance"/>
+</target>
+</code>