Uses of Package
org.praxislive.core
Packages that use org.praxislive.core
Package
Description
-
Classes in org.praxislive.core used by org.praxislive.audio
-
Classes in org.praxislive.core used by org.praxislive.audio.codeClassDescriptionAn optional context available from the
Rootlookup providing the ability to query and listen for changes in root state or clock time. -
Classes in org.praxislive.core used by org.praxislive.baseClassDescriptionComponents are the main building blocks (actors) within Praxis CORE.Address of a Component.Information about the controls, ports, protocols and properties of a Component.A type representing a connection between two ports.Extension to the Component interface for components that can contain other components as children.Information on the type, inputs, outputs and properties of a
Control.An optional context available from theRootlookup providing the ability to query and listen for changes in root state or clock time.Listener called on clock time updates.Possible states of a Root.Listener called on state changes.A general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Interface to be implemented by all types that provide access to a Lookup.Superclass of Call.Interface for an object that can route Calls to their required destination.Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.An interface used by the RootHub to control the lifecycle of, and communicate with, the Root.RootHub implementations act as a container for Roots, providing a way for Roots to communicate with each other and access other hub-wide services.Interface for writing the configuration and state of a Component, or tree of components, into a data structure.Abstract base class of all types used in messaging inside PraxisCORE. -
Classes in org.praxislive.core used by org.praxislive.codeClassDescriptionInfo object used to define the valid input and output arguments of a Control.Components are the main building blocks (actors) within Praxis CORE.Address of a Component.Information about the controls, ports, protocols and properties of a Component.Extension to the Component interface for components that can contain other components as children.Information on the type, inputs, outputs and properties of a
Control.An optional context available from theRootlookup providing the ability to query and listen for changes in root state or clock time.ComponentInfoBuilder classA general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Interface to be implemented by all types that provide access to a Lookup.Interface for an object that can route Calls to their required destination.Information on the type, direction and properties for aPort.A Protocol defines known controls and behaviours that a component can provide.Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.An interface used by the RootHub to control the lifecycle of, and communicate with, the Root.RootHub implementations act as a container for Roots, providing a way for Roots to communicate with each other and access other hub-wide services.Interface for writing the configuration and state of a Component, or tree of components, into a data structure.Abstract base class of all types used in messaging inside PraxisCORE. -
Classes in org.praxislive.core used by org.praxislive.code.userapiClassDescriptionInterface to be implemented by all types that provide access to a Lookup.Abstract base class of all types used in messaging inside PraxisCORE.
-
Classes in org.praxislive.core used by org.praxislive.coreClassDescriptionInfo object used to define the valid input and output arguments of a Control.High-precision nanosecond time source.Components are the main building blocks (actors) within Praxis CORE.Address of a Component.Information about the controls, ports, protocols and properties of a Component.Component results to be returned from
ComponentRegistry.query().A type representing a connection between two ports.Extension to the Component interface for components that can contain other components as children.Information on the type, inputs, outputs and properties of aControl.The types of a control.An optional context available from theRootlookup providing the ability to query and listen for changes in root state or clock time.Listener called on clock time updates.Possible states of a Root.Listener called on state changes.Builder for ControlInfo of action controls.Abstract base class for ArgumentInfoBuilders.Helper class for choosing an ArgumentInfoBuilder type.ComponentInfoBuilder classAbstract base class for ControlInfo builders.Helper class for choosing a ControlInfoBuilder type.Builder for ControlInfo for function controls.Builder for ArgumentInfo of PNumber.PortInfoBuilderHelper class to choose a PortInfoBuilder type.Builder for ControlInfo of property controls.Builder for ControlInfo of read-only properties.Builder for ArgumentInfo of PString.Builder for ArgumentInfo of any Value type.A general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Interface to be implemented by all types that provide access to a Lookup.AMapwith consistent order of entries.ASetwith consistent order of entries.Superclass of Call.Interface for an object that can route Calls to their required destination.Information on the type, direction and properties for aPort.Port direction.A Protocol defines known controls and behaviours that a component can provide.A protocol type registration, allowing protocols to be discovered by class or name.Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.An interface used by the RootHub to control the lifecycle of, and communicate with, the Root.RootHub implementations act as a container for Roots, providing a way for Roots to communicate with each other and access other hub-wide services.Interface for writing the configuration and state of a Component, or tree of components, into a data structure.Abstract base class of all types used in messaging inside PraxisCORE.The type of a Value.Exception thrown if a String is not a valid representation of the required Value subclass.ValueMappers translate values of type Value to another Java type. -
Classes in org.praxislive.core used by org.praxislive.core.protocolsClassDescriptionInformation about the controls, ports, protocols and properties of a Component.Information on the type, inputs, outputs and properties of a
Control.A Protocol defines known controls and behaviours that a component can provide. -
Classes in org.praxislive.core used by org.praxislive.core.servicesClassDescriptionComponents are the main building blocks (actors) within Praxis CORE.Address of a Component.Information about the controls, ports, protocols and properties of a Component.Information on the type, inputs, outputs and properties of a
Control.A general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).A Protocol defines known controls and behaviours that a component can provide.Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.Abstract base class of all types used in messaging inside PraxisCORE. -
Classes in org.praxislive.core used by org.praxislive.core.typesClassDescriptionInfo object used to define the valid input and output arguments of a Control.A general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).A
Mapwith consistent order of entries.Abstract base class of all types used in messaging inside PraxisCORE.Exception thrown if a String is not a valid representation of the required Value subclass. -
Classes in org.praxislive.core used by org.praxislive.hubClassDescriptionAddress of a Component.A general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Interface to be implemented by all types that provide access to a Lookup.Interface for an object that can route Calls to their required destination.Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.An interface used by the RootHub to control the lifecycle of, and communicate with, the Root.RootHub implementations act as a container for Roots, providing a way for Roots to communicate with each other and access other hub-wide services.
-
Classes in org.praxislive.core used by org.praxislive.hub.netClassDescriptionA general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.
-
Classes in org.praxislive.core used by org.praxislive.launcherClassDescriptionA general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.
-
Classes in org.praxislive.core used by org.praxislive.projectClassDescriptionAbstract base class of all types used in messaging inside PraxisCORE.
-
Classes in org.praxislive.core used by org.praxislive.scriptClassDescriptionA general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Interface to be implemented by all types that provide access to a Lookup.Interface for an object that can route Calls to their required destination.Root provides the companion part of the actor-model to Component within PraxisCORE's forest-of-actors model.An interface for RootHub extensions (see
RootHub.ExtensionProvider) to advertise the services they provide.Abstract base class of all types used in messaging inside PraxisCORE. -
Classes in org.praxislive.core used by org.praxislive.videoClassDescriptionHigh-precision nanosecond time source.A general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).Information on the type, direction and properties for a
Port. -
Classes in org.praxislive.core used by org.praxislive.video.codeClassDescriptionAn optional context available from the
Rootlookup providing the ability to query and listen for changes in root state or clock time. -
Classes in org.praxislive.core used by org.praxislive.video.pglClassDescriptionA general type-safe registry by which clients can access implementations of various services (eg. implementations of a specific interface).
-
Classes in org.praxislive.core used by org.praxislive.video.pgl.codeClassDescriptionAn optional context available from the
Rootlookup providing the ability to query and listen for changes in root state or clock time. -
Classes in org.praxislive.core used by org.praxislive.video.pgl.code.userapi