GroIMP wiki - 05_developer_tutorials:dev-guide

Access Descriptor files in runtime

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:21+00:00

GroIMP load doclet.xml files on startup that contains description of methods and classes. Access Descriptor files in runtime The loaded content is added in the runtime registry under /plugins/statics. This directory should have the three directories:

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:21+00:00

You can change navigation with view > navigators > select the one you want. You can add a new navigator by creating a new plugin. See template navigator. WIP

Implicit conversion

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:21+00:00

Implicit conversion GroIMP compiler can automatically perform implicit conversions. By default RGG files use this implicit conversions. A common example is the conversion from float to double (and vice versa). Add a conversion During compilation, if a type if forced onto another (and they are not compatible), the compiler try the Autoconversion, which includes widening conversions, boxing and unboxing, and allows to transform an object of type A into an object of type B by means of conversio…

Package imports

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:21+00:00

Groimp enables to includes default imports in files when compiling them. These imports are defined in the registry under. /io/filter/xx where xx is the filter type to manage. Currently only the rgg filter is modified, thus, all .rgg files are compiled with additional default imports.

Nodes

Anonymous (anonymous@undisclosed.example.com) — 2025-12-12T12:14:22+00:00

Create object from Nodes -> All objects that are supposed to be added in a groimp project should implement persistence management. (project graph & registry) -> source enhancement How to create a node class Code enhancement Includes object in production Custom object persistence Disposable Nodes/Fields Implicit conversion graph-listeners user-pattern

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:22+00:00

add-navigation Add templates and examples Create windows Creating new mimeType and File type Translating GroIMP into other languages

Add to the Git repository

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:21+00:00

Add to the Git repository Pushing to the remote repository If you followed the wiki on setting up a git connection This part consists of multiple steps. The plan is as follows: * Add changed files to stage * Create a commit * Push to the forked (your own) project

Disposable Nodes/Fields

Anonymous (anonymous@undisclosed.example.com) — 2025-12-12T12:07:44+00:00

Disposable Nodes/Fields A Node is considered deleted when it is removed from the graph. The Node is made “transient”, i.e. it is not handled by the persistence manager anymore. Once a Node is “transient” it will be automatically garbage collected by Java. However, a Node can have attributes (fields in java) that require a specific dispose method (e.g

Custom object persistence

Anonymous (anonymous@undisclosed.example.com) — 2025-12-12T13:56:46+00:00

Custom object persistence GroIMP require Nodes, Node's attributes, and SCOs to be manageable by the persistence manager, to process the save/ load/ query operations. GroIMP define its own persistence management. To be managed by the GroIMP persistence management, an object need to implements either

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:22+00:00

Create new API functions Add templates and examples Access Descriptor files in runtime Package imports

Anonymous (anonymous@undisclosed.example.com) — 2025-02-19T14:51:21+00:00

mvn compile mvn package: If the plugin have some java dependencies managed from Maven, the property generate-resources needs to be added to the pom.xml. mvn package -P app-with-doc: Add to the package command the compilation of the plugin's doc. Require

Plugin repositories

Anonymous (anonymous@undisclosed.example.com) — 2025-12-12T10:50:51+00:00

Plugin repositories The Plugin Manager uses Plugin repositories to gather knowledge on the available plugins. The repositories can be provided in three formats: * Ordered List ItemAs a JSON file. Which contains the metadata of one or several plugins.The file need to follow the JSON format for plugin data (see bellow).

GroIMP Plugin

Anonymous (anonymous@undisclosed.example.com) — 2025-12-12T10:51:52+00:00

GroIMP is designed around plugins which can be added, modified or removed without modifying the GroIMP installation. GroIMP Plugin Any repository with a plugin.xml and plugin.properties files is considered as a plugin by GroIMP. To be properly loadable though, the