Found 13 packages
The codeboxes responding library offers you the possibility to add targeted callbacks. The distributing and the storing libraries of the codeboxes framework are using responder of this library, so please see the documentation of these for some example code. Mostly the interfaces are used, so you can implement them as you like and create your own solution. But the ones provided by this library are multifunctional easy to use and ... ehm ... and ... well, a gift.
The codeboxes ticking library gives you the possibility to get the running time of your application and a ticker, that informs you every second. Addintioanlly you can get the ntp internet time as a Now DateTime.
The mvc lib allows you to manage your project by using the mvc pattern. It uses most of the other codeboxes libraries.
This library gives you the option to build conditions that decide by their own, if they are met by given information. The other codeboxes libraries are only working with the IConditions interface. The rest is a given extra, which you can use.
The codeboxes storing library offers you the possibility to cache and watch data objects. I created that library to never ever communicate data changings in a project again. That will be done by the library.
The codeboxes caching library gives you the option to simple cache objects.
This is the core package of the Codeboxes framework used by each other Codeboxes library. The work on this framework is still in progress.
This library gives you the option to process work sequentially and/or timed/repetitive.
The codeboxes distributing library offers you the possibility to call unknown and distant objects. All you have to do is adding an implemented Cable to your Distributor of choice and then add some devices to a(nother) Distributor under the same name like the Cable. Your Cable and the devices should implement the same interface(s). When you then get the Cable from the Distributor and are calling a function or property on it, all devices (under the same name) will be called, too. If you added a device as class instead of an object, then on each call a new object of that class will be created.
The codeboxes interpreting library gives you some tools to interpret string values into usable Objects. You can get usable Objects for formulars and cron expressions. But you have to take care of your given strings by yourself, to be well formed.
The stating library enables you to use states in an easy or complex way - whatever you like. I decided to separate the transitions between the states from the states themselves, because I thought they should not be part of them. You can extend these StateTransition and have therefore full control over which IState should appear after the deactivated one, but you don't need to. If you have simple one-after-one-transitions, then you just need to specify that at adding the IState object to the StateMachine and that's it. The StateMachine will do the rest for you.
The Codeboxes Assets library gives you the possibility to organize your assets in a comfortable way, so that they are available locally on disk. The AssetManager will only download them at startup, when a new version of an asset is available, commited by a json config file.
The Surveillance library shows you in a special view what each of the other used Codeboxes libraries are doing and holding. And if you use it well, it will show you, what your stuff is doing, too.