How to import a .farki package
Import a package
Section titled “Import a package”- File > Import Package…
- Select the file from your filesystem — a
.farkimodel file or a.farki.ziparchive (attachments included) - The file’s contents are imported into your current project
The imported packages appear in the Explorer. If the file contains an M2 metamodel, its element types and relationship types become available in the Palette for any diagram that imports that metamodel.
Importing attachments (.farki.zip)
Section titled “Importing attachments (.farki.zip)”A .farki.zip archive (produced by exporting a package with attachments) is auto-detected on import. Its bundled images and files are restored to their elements, and a confirmation summarises what came in — for example, “12 elements, 3 attachments restored”. Archive import works in both the desktop and web apps. See How to attach files, images, and links.
What gets imported
Section titled “What gets imported”A .farki file can contain:
- M2 metamodel packages — element types, relationship types, notation, properties, enumerations, and constraints
- M1 model packages — elements, relationships, property values, diagrams, and catalogs
- Both — a file can include an M2 metamodel and M1 models that use it
All packages in the file are imported into the current project. Existing packages with the same name are not overwritten — duplicates are created side by side.
Project-scope vs package-scope files
Section titled “Project-scope vs package-scope files”- Package-scope files (the most common) contain one or more packages. Use File > Import… to bring them into an existing project.
- Project-scope files contain a complete project. Use File > New Project… > From File to create a new project from these.
The file’s scope is set when it’s exported. You can check the scope by opening the .farki file in a text editor and looking at the "scope" field.