Differences

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

--- user-guide:export-as-lib [2025/04/02 16:29] – [Compiled classes] gaetan
+++ user-guide:export-as-lib [2025/04/03 12:09] (current) – gaetan
@@ Line 1: / Line 1: @@
-====== Project as Library ======
+====== Project as a Module Library ======
 Project can be exported as a library usable from other projects. The exported library makes all types (classes, modules, ...) and resources (images, shaders, ...) available for import.
@@ Line 23: / Line 23: @@
 ==== Package name ====
+By default, .rgg types are compiled without a package. It makes them all visible from the same pool. However, for ensuring a uniqueness when importing module library, a package name is required during the export. GroIMP will use the given package name as default package during the compilation.
+Thus, if the project contains type with named package, they will not be affected by the package name provided.
+The package name must follow java's specification on package name.
 ==== Reference wrapper ====
+GroIMP implicitly wrap all references call in the project to be exported as module library to make them use the resources form the library.
+Indeed, if a project contains a resource with the name "shaderleaf". When exported, the module that use ''setShader(shader("shaderleaf"))'', needs to point as the resource from the module lib. And not a possible "shaderleaf" in a newly opened project.
+The wrappers force the references to point at ''plg:pkg.Plugin:"shaderleaf"''.