GroIMP wiki

a part of grogra.de

User Tools

Site Tools

Trace: • Custom object persistence
You are here: GroIMP documentation » Developer tutorials » Developer guide » Custom object persistence
05_developer_tutorials:dev-guide:embedded-file-object

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
05_developer_tutorials:dev-guide:embedded-file-object [2025/12/10 13:13] – ↷ Links adapted because of a move operation gaetan05_developer_tutorials:dev-guide:embedded-file-object [2025/12/12 14:56] (current) – [Embedded objects] groimp
Line 3: Line 3:
 GroIMP require Nodes, Node's attributes, and SCOs to be manageable by the persistence manager, to process the save/ load/ query operations. 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 [[01_user_documentation:groimp-platform:persistence|persistence management]]. To be managed by the GroIMP persistence management, an object need to implements either [[https://javadoc.grogra.de/graph/de/grogra/persistence/PersistenceCapable.html|PersistenceCapable]] (GroIMP interface), or [[https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html|Serializable]] (java interface).+GroIMP define its own [[01_user_documentation:06_graph:07_persistence|persistence management]]. To be managed by the GroIMP persistence management, an object need to implements either [[https://javadoc.grogra.de/graph/de/grogra/persistence/PersistenceCapable.html|PersistenceCapable]] (GroIMP interface), or [[https://docs.oracle.com/javase/8/docs/api/java/io/Serializable.html|Serializable]] (java interface).
    
 Usually the persistence is handled in memory (except when the project is saved), but GroIMP provides a way to integrate it with file persistence (the object is written/loaded from the file). This rely on EmbeddedSharedObject and EmbeddedFileObject. Usually the persistence is handled in memory (except when the project is saved), but GroIMP provides a way to integrate it with file persistence (the object is written/loaded from the file). This rely on EmbeddedSharedObject and EmbeddedFileObject.
Line 15: Line 15:
  
 The object that extends ESO need to implements the following methods: The object that extends ESO need to implements the following methods:
-  * ''public MimeType getMimeType()'': to provide the mimetype to use when writing and loading the object (see GroIMP [[01_user_documentation:groimp-platform:input-and-output-in-groimp:mimetype|mimetype]]).+  * ''public MimeType getMimeType()'': to provide the mimetype to use when writing and loading the object (see GroIMP [[01_user_documentation:03_interacting_with_groimp:14_io|mimetype]]).
   * ''public String getExtension()'': to provide the file extension (can be an empty string. File extensions are used to make it easier read files but are usually not required).   * ''public String getExtension()'': to provide the file extension (can be an empty string. File extensions are used to make it easier read files but are usually not required).
   * ''public String getResourceDirectoryName()'': Name of the directory in which the file will be stored when the project is saved.   * ''public String getResourceDirectoryName()'': Name of the directory in which the file will be stored when the project is saved.
05_developer_tutorials/dev-guide/embedded-file-object.1765368787.txt.gz · Last modified: 2025/12/10 13:13 by gaetan