BaseContext Related Documentations

Detailed Description

Here are links to documentations related to class BaseContext. This class allows the management of a set of objects as an application context, and is provided with the base package. On this page, the methods are sorted by themes.

Modules

BaseContext Init Methods

Init Methods for BaseContext.

BaseContext Object Edition Methods

The methods that allows to create Objects in a BaseContext. Then to edit objects, use the objects methods.

BaseContext Input & Output Methods

Serialization methods. Also note BaseType::WriteFile() and BaseType::ReadFile() are valid for BaseContext.

BaseContext Event Management Methods

You can be notified of any change in the context with these Methods. This makes possible to build a complete user interface to edit the context.

BaseContext Undo & Redo Methods

BaseContext provides an automatic management for all editable object members in the context. Active it with BaseContext::SetMaximumNumberOfUndoableEvents(). Note: its is currently beta, because re-creation of destroyed objects or list elements by undo is not managed at the moment, So any deletion on a list will flush the undo stack.

Classes

class BaseContext

You may also browse the BaseContext Related Documentations page sorted by theme.
Class that manages a whole database as a set of Objects inheriting class BaseObject.
BaseContext::Serialize_Out() and BaseContext::Serialize_In() will provide a quick and full persistent serialization of all features of a whole azurveda Context. When reading the context, the objects references will be resolved. In editable compilation mode you can use:

Hook notifications for all events, useful for Graphical Interfaces: see AddGUIUpdateFunction()
Merge serialization: simply melt as many context objects you want with MergeSerialize_In()
Hability to destroy all objects that are useless to a given object with DestroyAllIndependantObjects(). Together with the merge method, it gives a complete control for large and complex contexts.
automatic Undo/Redo stack functionnalities with Undo(), Redo(), SetMaximumNumberOfUndoableEvents(). This undoes affect the modification of any editable object members in the context. (BETA: currently,undo stack is flushed when an element is destroyed in a list.)
Thread management withAddOneLockForThreadUse(),RemoveOneLockForThreadUse().

To use a context object, you first init a context by registering possible extended classes or packages, derived from BaseObject, with RegisterClassList(). In editable mode, you can create new BaseObjects using the BaseContext::NewObject(), and destroy them with BaseContext::DestroyObject(). Then you can initialize each objects using BaseObject::Create(), and close them with BaseObject::Close(). See BaseObject for more informations on Object Creation.
After the context is created, you can provide a VirtualMachine with SetMachine(), it stands for the hardware-abstracted machine its objects will use.

More...

      /\/\        4         N         k         !         N         D
                      _______  _ __ ___  _____            ___ _ _  ____
     ___________  __//___   /________  |/    / ___________\_______/    \
    /   _   _   \/   _     /    _   /      _/_/____/    _       __     /
   /    /   /       /     /    /    \      \/     /    /    \   \     /
  \\___/___/___/    ¯    _____/_____/       ______\___/_____/\________\\
               \________/_ ___ __ l____\      /elD!  
                 http://www.m4nkind.com \____/


Modules
	BaseContext Init Methods
	Init Methods for BaseContext.
	BaseContext Object Edition Methods
	The methods that allows to create Objects in a BaseContext. Then to edit objects, use the objects methods.
	BaseContext Input & Output Methods
	Serialization methods. Also note BaseType::WriteFile() and BaseType::ReadFile() are valid for BaseContext.
	BaseContext Event Management Methods
	You can be notified of any change in the context with these Methods. This makes possible to build a complete user interface to edit the context.
	BaseContext Undo & Redo Methods
	BaseContext provides an automatic management for all editable object members in the context. Active it with BaseContext::SetMaximumNumberOfUndoableEvents(). Note: its is currently beta, because re-creation of destroyed objects or list elements by undo is not managed at the moment, So any deletion on a list will flush the undo stack.
Classes
class	BaseContext
	You may also browse the BaseContext Related Documentations page sorted by theme. Class that manages a whole database as a set of Objects inheriting class BaseObject. BaseContext::Serialize_Out() and BaseContext::Serialize_In() will provide a quick and full persistent serialization of all features of a whole azurveda Context. When reading the context, the objects references will be resolved. In editable compilation mode you can use: Hook notifications for all events, useful for Graphical Interfaces: see AddGUIUpdateFunction() Merge serialization: simply melt as many context objects you want with MergeSerialize_In() Hability to destroy all objects that are useless to a given object with DestroyAllIndependantObjects(). Together with the merge method, it gives a complete control for large and complex contexts. automatic Undo/Redo stack functionnalities with Undo(), Redo(), SetMaximumNumberOfUndoableEvents(). This undoes affect the modification of any editable object members in the context. (BETA: currently,undo stack is flushed when an element is destroyed in a list.) Thread management withAddOneLockForThreadUse(),RemoveOneLockForThreadUse(). To use a context object, you first init a context by registering possible extended classes or packages, derived from BaseObject, with RegisterClassList(). In editable mode, you can create new BaseObjects using the BaseContext::NewObject(), and destroy them with BaseContext::DestroyObject(). Then you can initialize each objects using BaseObject::Create(), and close them with BaseObject::Close(). See BaseObject for more informations on Object Creation. After the context is created, you can provide a VirtualMachine with SetMachine(), it stands for the hardware-abstracted machine its objects will use. More...