Differences

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

--- tutorials:advanced:create-module-lib [2025/04/02 16:05] – gaetan
+++ tutorials:advanced:create-module-lib [2025/04/02 16:26] (current) – gaetan
@@ Line 7: / Line 7: @@
 Let's create a very simple project from the ''newRGG'' template.
+**Rename the Model.rgg file to An.rgg** (or any other name). It is not required but it gets confusing when all modules come from Model classes.
 Let's include a custom shader from an image to the project (steps correspond to image bellow):
@@ Line 66: / Line 68: @@
 Then, restart GroIMP to load the library.
+Now let's open a new project (''newRGG'' for instance).
 ==== Type ====
+The types from the module library can be imported in the project like any other classes:
+''import pkg.example.An.A;''.
+The pattern is: ''import {package name}.{File name}.{Class/module name};''.
+Notice that the name of the file is required in the import. GroIMP implicitly create classes with the name of the files to wrap all types defined in .rgg classes.
+**Note:** in the ''newRGG'' project, if you import ''An.A'', "nothing" visible will happen. Because the project also declare a type called ''A''. So, in order to adds An.A to the project you can either use its full name, or hide (by deleting?) the module A declaration.
+The Node An.A have the shader from their original project, i.e. the one with the image.
 ==== Resources ====
+Resources from module lib can also be used without classes. You can use the shader ''testshader'' on any module in your project with:
+<code java>
+module A(float len) extends Sphere(0.1)
+{
+	{setShader(shader("plg:pkg.example.Test:testshader"));}
+}
+</code>
+The Shader reference use the path: ''plg:{package name}.{plugin name}:{resource name}''.