Administration module.
This module provides hooks to create and modify Toxik project, user
and machine preferences. It also provides access and search mechanisms
for Toxik components (compositions, composition versions, etc) through a
virtual file system: the library manager.
Toxik has three types of administrable that defines preferences used
in the application: Project (".txproject" file), User
(".txuser" file) and Machine
(".txmachine" file), which all derive from a common base
class: Administrable.
|
|
AdminError
|
|
|
Administrable
The Project, User
and Machine classes all derive from the Administrable base class.
|
|
|
FindUtil
The FindUtil class can be used to perform search queries in the
Toxik library.
|
|
|
LibraryMgr
The library manager is a static class used to access and manage
Toxik and regular files on the filesystem.
|
|
|
Machine
|
|
|
MachineMgr
For projects, users and machines (administrables) a common
interface is implemented by their respective manager classes: ProjectMgr, UserMgr and MachineMgr.
|
|
|
Project
The Project class provides additional methods to access its
preferences.
|
|
|
ProjectMgr
The manager class for Project administrables has a slightly
different interface than the manager class for User
and Machine administrables.
|
|
|
UdaMgr
Use this class to manipulate user-defined attributes (UDAs).
|
|
|
User
|
|
|
UserMgr
For projects, users and machines (administrables) a common
interface is implemented by their respective manager classes: ProjectMgr, UserMgr and MachineMgr.
|
str
|
getAbsolutePath(path)
Returns:
The absolute path of a file for the given relative (or absolute)
path. |
|
|
str
|
statStr(libmgr,
path)
Returns:
A string representation of the output of stat for printout. |
|
|
|
|
setUDA(componentPath,
udaName,
udaValue)
Convenience function that creates a UDA if it doesn't exist in the
current project and sets its value on the specified component. |
|
|
str
|
getCurrentDir(...)
Returns:
The current working directory of the process. |
|
|
str
|
getHomeDir(...)
Returns:
The home directory is a directory under which Toxik stores data on a
per user basis, and under which the Toxik user data directory will be
created. |
|
|
str
|
|
str
|
getLogFile(...)
Returns:
The file name for the log file of the current process. |
|
|
str
|
getOutputDir(...)
Returns:
The directory under which Toxik stores log files and other run-time
information. |
|
|
str
|
|
str
|
getResourcesDir(...)
Returns:
The resources directory is where the Toxik runtime resource files
reside. |
|
|
str
|
getRootDir(...)
Returns:
The root directory (str) of the file system (/ on UNIX
or the current drive on Windows). |
|
|
str
|
getScriptsDir(...)
Returns:
The path to the directory where the Python scripts used by Toxik are
located. |
|
|
str
|
getTempDir(...)
Returns:
The path (str) to the platform-specific directory where
Toxik puts its temporary files. |
|
|
str
|
|
str
|
substituteString(...)
Substitutes Toxik tokens (such as <ProjectHomeFolder>,
<Date>, <CurrentUser>, etc) in the specified string and
returns the resulting string. |
|
|