Data Explorer manages all the resources : import, create, delete resources and publish project for the different supported platforms. it also provides a source control management for the ShiVa Advanced version.
Open the selection with the dedicated editor module.
Thumbnail : Display the resources as miniatures, pictures or large icons according to their type.
Scene : Import objects as Scene -> Go.
Import from libray : Import the content of a library archive in your project.
The fast filter
The fast filter is a quick search tool that filter on resources name.
A scene is a collection of models and simple objects that can be loaded by the engine at runtime.
A model can be instanciated in a scene manually or in script using the scene.createRuntimeObject function.
An animClip contains TRS information of an animation and can be applied on various object.
3D sound spacialisation need a mono sound.
Dedicated for multi-platform game creation, profiles are used to prepare all the resources for the seletected platform targets. You can force the maximum size, compression for the exported texture.
Once created, the profile will be available in the export windows.
Separate files : use this option to clean a project, only files used will be exported.
Edition Archive : like the separate files option but the export will produce a single file( zip style )
Runtime Package : with the profile chooser on the right, create a runtime package (stk) to be used with the Authoring Tool or as-is using the ShiVa Players.
Runtime Package ( + cpp source) : with also the profile chooser on the right, create an assets only ( ie without script ) runtime file, the scripts will be exported as separate files and converted into C++ to be used with the Authoring Tool.
Feature available in Advanced version only
Create a new project in your source control manager (SCM)
Create a new project in the dialog from ShiVa Menu > Main > Projects.
Then, checkin your new project in your SCM : DataExplorer Menu > Tools > Checkin project to repository.
You can change the name under which the project will appear in the SCM.
If you enter 'MarvelousProject', the Games folder of your project locally named 'WonderfulProject' will be checked in 'svn://192.168.1.15/AllMyProjects/MarvelousProject/Games'. The DataExplorer root will change from WonderfulProject to WonderfulProject[MarvelousProject]. That means that your local project 'WonderfulProject' is now linked to the SCM folder 'MarvelousProject'.
Retrieve a project from your source control manager (SCM)
Create a new project in the dialog from ShiVa Menu > Main > Projects (The project can be named differently than the project on the SCM).
Then, checkout the project form your SCM : DataExplorer Menu > Tools > Checkout project from repository.
The DataExplorer root will change from 'MyNewProject' to MyNewProject[MarvelousProject]. That means that your local project 'MyNewProject' is now linked to the SCM folder 'MarvelousProject'.
Synchronise your local project with the SCM repository
This dialog presents the overall status of your local project.
'Outgoing files' contains the files modified locally and that need to be checked in the SCM repository.
'Incoming files' contains the files other users have modified in the remote SCM repository.
You can use filters to display only desired files. In that case, only displayed files will be taken into account by the synchronization process (even if you select file before enabling a filter).
the file is locally new (not present in the repository yet).
the file has been locally modified.
the file is locally deleted (but still present in the repository).
the file has been locally modified but, meanwhile, has been modified in the repository by other users. If you select the outgoing file, it will replace the remote version. Note: in this version, it's not possible to merge local changes and remote changes. You either overwrite remote changes with your local changes or overwrite your local changes with remote changes (see below).
the file has been added to the repository.
the file has changed in the repository.
the file was deleted from the repository.
the file has been locally modified but, meanwhile, has been modified in the repository by other users. If you select the incoming file, it will overwrite your local file (your local changes will be lost and replaced by the incoming file).
Manage locked files
This dialog allows you to see all locked files (including files locked by other users) and allows you to unlock the files you have locked. There are two ways to lock a file:
A locked file can be modified only by the user that locked it. If, in Shiva Editor, another user tries to modify a file already locked by you, the editor tells him that the file is locked (warning in the Log Reporter) and prevents him from checking this file in the repository until you release the lock.
There are two ways to unlock a file:
• Automatically, when you checkin the locked file in the repository. • Manually by clicking on the 'Lock icon' in the dialog or by right clicking on the file and selecting the 'Version control > Unlock' option. Warning: if 'Autolock on editing' option is checked, the file will autolock again if you modify and save it.
Project and files revisionYou can list all the revisions of your project using DataExplorer Menu > Tools > Checkout project from repository. To retrieve a revision, select the revision and click on 'Get revision'. It will overwrite all the files of your project : your local changes will be lost and replaced by the incoming files.
You can list all the revisions of a file by right clicking on it in the DataExplorer list and select 'Version control > Show history'. To retrieve a revision, select the revision and click on 'Get revision'. It will overwrite it: your local changes will be lost and replaced by the incoming file.
Special actions :