====== Import types/ resources ======

To use types (classes/ methods/ modules/ ...) that are defined in a library into your project, the type needs to be imported. 

There are several level of imports:
  * Automatic imports
  * Project imports
  * Plugin imports
  * Module library imports
  * Third party imports


===== Automatic import =====

{{page>01_user_documentation:07_rgg_xl:02_xl:10_rgg_addition:03_class_import&noheader}}.

===== Project imports =====

These are the imports of type from within the current project. Within a project all files are viewed at the same level, without including the directory. Thus, the project contains a file named Model.rgg, which declare a type named A. The type A, can be imported in any of the other files of the project with ''import Model.A;''.

===== Plugin import =====

These are the imports from packages available within GroIMP. e.g. ''import de.grogra.gpuflux.tracer.FluxTracer;''. 

===== Module library import =====

Module libraries are project that have been exported as library. These libraries can be added in GroIMP as plugins, and then all of their types can be used as plugin imports. 

See [[:01_user_documentation:03_interacting_with_groimp:05_project:04_module_library|here]] to see how to export a project as a library.

===== Third party imports =====

Third party libraries can be added to your project in the ''file explorer'' (see [[:user-guide:common_panels#File_explorer|here]] for more details). 

Once imported, they can be imported normally: ''import my.pckg.Class;''. 

Note that some third party library are included in some GroIMP plugins. Thus, already available as plugin imports.