Chronos Plugins 5.9.0
This documentation covers the plugin interfaces definitions and an example implementation.
Loading...
Searching...
No Matches
Class List
Here are the classes, structs, unions and interfaces with brief descriptions:
[detail level 123456]
 NAxelSemrauThings provided by an AxelSemrau program or library. Do not put your own code into this namespace, as there could be naming collisions in future versions of Chronos
 NChronosThings provided by AxelSemrau Chronos - do not put your own code into this namespace
 NPluginClasses and interfaces that are meant for plugins. The classes and interfaces below this namespace are meant to be upwards compatible across Chronos versions. If you notice any incompatibilities, please let us know
 CCoreAccess to some parts of the core of the Chronos program
 CICoreUtilsChronos core utility functions
 CIJobInfoBasic information about a job (= diagram row) within a task planer
 CIPlannerInfoSome hopefully useful information about a queued planner
 CIScheduleQueueAccess to the schedule execution list
 NMockPluginAn example Chronos plugin. This plugin demonstrates how to write plugins for Chronos. It should give you a rough idea how different things can be done, and which interfaces are needed to provide funtionality
 NAcquisitionServiceEnables you to add support for a Chromatography Data System (or similar) to Chronos. An acquisition service added this way will behave like the builtin services and can be used with the Acquisition task
 CConfigDialogInteraktionslogik für ConfigDialog.xaml
 CDynamicAcqParsParameter class for an acquisition service that has a variable number of properties
 CMockCommandAndParametersExample definition of a command and its parameters that can be called for an AxelSemrau.Chronos.Plugin.ICommandUsingAcquisitionService
 CMockDynamicParAcquisitionServiceAcquisition service for a parameter class that has a variable number of properties
 CMockSimpleAcquisitionServiceAn example acquisition service using a fixed list of parameters
 CSimpleParametersExample parameter set for an acquisition service
 NConsumables
 CCoffeeConsumableManagerKeeps track of all consumables that are associated to our mock coffee machine
 CCoffeeConsumableManagerUIToolbox for all coffee machine related consumables. Currently just a display of the consumable levels
 CCoffeeConsumableViewModelViel model for coffee machine related consumables
 CCoffeeIngredientBase class for all used mock coffee ingredients
 CIngredientsForDevice
 NDeviceA fake device. This namespace contains the fake device driver and auxiliary classes for settings, toolbox and other infrastructure
 CCoffeeMakerParamsUISimple user interfrace for the fake coffee maker's parameters
 CCoffeMakerParamsWe have a fancy coffee machine that can regulate the warmer temperature for the pot and has lamps for ambient light
 CConnectionEditorJust a primitive UI Type Editor to demonstrate how you can add an editor of your own for connection strings
 CConnectionStringEditorJust a form with a TextBox. Nothing to see here
 CDeviceSurveillanceShows how you can directly interact with all configured devices
 CEditMachineParamsInteraction logic for EditMachineParams.xaml
 CMockDeviceA chronos plugin implementation for a fake device. We pretend we are controlling a mixture of coffee machine and waiter robot
 CMockDeviceToolboxExample implementation for a WinForms toolbox for our Mock Device
 CTrainFor lack of a better idea, the demonstration for the multipart device is a train consisting of a locomotive and some different cars
 CTrainPartThe device part (well, train part) can't do much, just send status messages when the doors are opened/closed
 NMiscContains things that do not fit into the other categories
 CFakeStatusViewModel
 CLargeDeviceStatusViewInteraction logic for LargeDeviceStatusView.xaml
 CMockLicenseCheckAttribute
 CNoLicenseNeededExplanationInteraction logic for NoLicenseNeededExplanation.xaml
 CStatusViewControlThis control is used to show the status for our MockDevice
 NRemoteAccessTesterInteraction with Chronos crossing the process barrier. A normal Chronos plugin is a class library loaded into Chronos. If you want to interact with Chronos from a different application, you can use the techniques demonstrated here to communicate with another process and remotely control Chronos
 CEndpointDefTo avoid duplicating the endpoint definition in server and client
 CIMockPluginVery basic service, only to show that you can trigger some action from outside and get a response
 CMessageTesterFormShows how to communicate from an external program with a Plugin in order to trigger actions in Chronos
 NSampleListThe classes in this namespace demonstrate how to interact with the Chronos sample list
 CMockSampleListWorkerProvides an endless supply of nonsense sample lists
 CRemotePluginServiceExample for communication with external programs
 CShowPluginIsInChargeInteraction logic for ShowPluginIsInCharge.xaml
 NSampleListColumnsThe classes in this namespace demonstrate how to define your own sample list column types
 CCoffeeTypeColumnJust an example for freshly updated combobox entries
 CColumnHeaderMenuJust a general purpose column header menu
 CCreamTypeColumnSimple case: Enum based column. Possible values are given in the StandardItems, custom editor is not used
 CCreamTypeConverterJust provide a TypeConverter, and Chronos is happy
 CDateColumnExample column type that allows to pick a date and time from a graphical editor
 CMyDateSimple wrapper around DateTime that makes sure to always use the invariant culture
 CMyDateConverterJust like the default converter, but always use the invariant culture and wraps/unwraps the "MyDate"
 CMyDateEditorJust unwrap and edit the inner DateTime
 NTasksExample task implementations. Since there are lots of things that can be done from a task, the demo was split into many different examples each showing only few facets of what's possible. If you still think this is confusing, please let us know where we could simplify these examples
 CBrewCoffeeCalls a method of the device class with one if its task parameters
 CBrewFrappuccinoA task working on a complex parameter set
 CCoffeeCategoryCustom category in the method editor for coffee making related tasks
 CCoffeeMachineBaseTaskBase class for our example, just contains some empty default implementations and a check for the right device type
 CCoffeeMachineDoesNotWorkProperlyIn contrast to PretendCoffeeMachineIsBroken, this simulates an error that an autosampler could have while it is used by a task
 CDumpConfigInfoThis tasks uses the config helper to access some information about the instrument configuration and just dumps it to the runlog
 CFlexibleArgumentsThis task demonstrates how to use a custom type descriptor to implement a dynamic list of properties. The number of properties can be changed by setting the PropCount property
 CFrappuccinoCompositionEditorProvides an editor for the BrewFrappuccino-Task's "Composition" information
 CJobInspectionDemoShows how to get information about other tasks in the schedule
 CMockDynamicPropsDependingOnDeviceThis task demonstrates how to make the property list depend on the picked autosampler
 CMockMethodEditorSnoopingTaskThis task just shows how you can react on the method editor contents and provide context sensitive property standard values
 CMockUseMultipleDevicesTaskFor some special cases it can be necessary to have a single task communicate with two different devices
 CPretendCoffeeMachineIsBrokenThis task will trigger a timer in our device which will make it complain about an error situation, even if at that time no task is trying to use it
 CShowSomeGreetingA task which does not need access to the custom device
 CTaskListAttributeThis attribute uses the task to which it is applied to query for other tasks in the method editor. The list of returned values is just a list of the tasks currently in the method editor
 CUseTrainJust show that some kind of operation can be done with our "Train" device parts
 NRemoteAccessTesterA minimal example program that shows how you could remotely control Chronos. The program does not interface with Chronos directly, but through a service provided by the MockPlugin
 CProgramClass containing the entry point