Imagine you have created an experience named yourExperience and stored this experience in a folder named yourExperience
. The underlying file organization is described below.
NOTE:
- In all cases, be sure to display file extensions.
- See this article for guidance about manually copying/transferring/deploying projects to other PCs and this article for an automated option.
Intuiface Version 6 and Version 7
Regardless of your Platform account level - Trial, Essential, Premier, Enterprise - the project structure and file naming are the same.
For example, assume you have an experience named 'yourExperience'. It is represented by a single folder also named "yourExperience". This folder contains:
- A file named yourExperience.ifx. This is an XML file used for our Windows support, and it should never be edited directly. All changes to this file are made through the use of Composer.
- A file named yourExperience.ifx.json. This is an XML file used by Player on all platforms but Windows. As with the .ifx file, never edit this file directly.
Note: This file is created when you save changes to a project. A newly created project does not contain this file. - A file name yourExperience.ifxp. This is a file that will only permit playback in Composer; Edit Mode will be unreachable. If you give someone in possession of Composer a project containing only the .ifxp file and the Files folder (see below), meaning you deleted the .ifx file, that person will be able to play the experience but not make changes.
- A folder named
Files
containing all of your assets (images, documents, videos...).
Intuiface Version 5
With Intuiface Version 5, experiences created using Intuiface include information about which Composer edition was used to create them. This means there are three kinds of experiences – Free, Pro and Enterprise – and not just three editions of Composer. Each experience filename is tagged with the name of the Edition last used to save it: .free.ifx for Free, .pro.ifx for Pro, .ifx for Enterprise.
Using the Free Edition as an example, the experience named 'yourExperience' is represented by a single folder also named yourExperience
that contains:
- A file named yourExperience.free.ifx. This is an XML file used for our Windows support and it should never be edited directly. All changes to this file are made through the use of Composer.
- A file named yourExperience.free.ifx.json. This is an XML file used for our iPad, Android and Samsung SSP support. As with the .free.ifx file, do not modify this file in any way.
- A folder named
Files
containing all of your assets (images, documents, videos...).
Intuiface Version 4
With Intuiface Version 4, experiences created using Intuiface include information about which Composer edition was used to create them. This means there are three kinds of experiences – Free, Pro and Enterprise – and not just three editions of Composer. Each experience filename is tagged with the name of the Edition last used to save it: .free.ifx for Free, .pro.ifx for Pro, .ifx for Enterprise.
Using the Free Edition as an example, the folder yourExperience
contains:
- A file named yourExperience.free.ifx. This is an XML file used for our Windows support and it should never be edited directly. All changes to this file are made through the use of Composer.
- A file named yourExperience.free.ifx.json. This is an XML file used for our iPad and Android support. As with the .free.ifx file, do not modify this file in any way.
- A folder named
Files
containing all of your assets (images, documents, videos...).
NOTE: Before Intuiface Version 4.1, the Files
folder was named [yourExperience]_Files
. Projects using this now deprecated naming convention can still be opened by Version 4.1+.
Intuiface Presentation Version 3
In Intuiface Presentation Version 3, the folder yourExperience
contains:
- A file named yourExperience.ip3. This is an XML file that should never be edited directly. All changes to this file are made through the use of Composer.
- A folder named
yourExperience_Files
containing all of your assets (images, documents, videos...)
Comments
0 comments
Article is closed for comments.