Namespace Appearition.Common
Classes
AccountVerificationProcess
BaseDocument
Base class for a document of type FloAR.
BaseFloARHandler
Base class for a FloAR-like handler. Contains utilities to deal with handlers of that generation.
BaseHandler
Base API handler.
CustomApiStorageDatabase<T, K>
Generic database for API response, featuring both an override or additive data implementation. This system does not support removing specific items, but upon clearing the cache, its content will be cleared off.
CustomApiStorageDatabase<T, K>.DatabaseContent
DataTransferStatus
Data container class for file transfer status when communicating with the EMS, for both download and upload.
DataTransferStatus.ItemProgress
Information related to individual items being transferred. Do note that the transfers can either be linear (queue) or parallel.
ImageUtility
Utility component helping dealing with Texture2D and Sprite objects.
MediaType
Base container class for a mediatype definition. A MediaType contains information about the type of media of a specific experience. This includes how to display the media, but also how to load and upload it.
MediaType.FileValidation
Used to determine whether the MediaFile is respecting the EMS's rulesets for this MediaType.
MediaType.OtherProperty
MediaType.PropertyDefault
Contains the default properties of a MediaFile of this MediaType
MediaTypeUtility
Static utility class to help with MediaType queries.
Parameter
Container of an Appearition Parameter JSON ApiData model.
Setting
Container of an Appearition Setting JSON ApiData model.
SetUserChannelAsCurrentProcess
Requires the user to be logged in. Finds the most appropriate channel based on a logged in user, and set it as the current channel in the current user on the AppearitionGate.
Structs
EmsError
Object containing any _errors or messages from the EMS regarding the EMS request it was used on.
Interfaces
ICommonProcess
Base instructions for a cross-module process from the SDK. Those processes are likely to hit multiple modules in order to achieve what they require, and may occur in multiple steps, asking for the user to provide some input in mid-process. Make sure to check the requirements and constructors of each of those processes for more information.