GitLab

It appears this whole change is unnecessary when a simple contract
is kept: Whenever you define a lens, the write lens should never yield
Nothing while there is a reducer for the lens.

Tweaked the utility functions for creating startable tasks to reduce the need to pass default parameters in the common cases.

Also tweaked the API a bit based on the examples in the documentation.

It now possible to do the same with `doTasks`

directly creating task instances when an application is started.
This was already possible internally, but was not yet exposed in the API.

This reverts commit 76d6217a.

trees

This commit enables:
- Asynchronous reading from any kind of SDS
- Asynchronous writing from any kind of SDS
- Asynchronous modifying of SDSLens, SDSSelect, SDSRemoteSource,
SDSSource. For all other SDS definition the modify is implemented as
read --> write.

- Add new share types denoting a share is a remote (SDSRemote)
- Change read/write/modify signatures to be able to return that a
respective operation is queued.
- Change get/set/upd to use and wait for asyn operations
- Change part of the task rewriting to account for waiting for async
operations

An operation on a SDS can now yield either:
    Queued connectionId: An async operation is queued, the task will be
    notified when it is done. The connectionId should be used to
    retrieve the result from the connection states in the world.

    This is only returned when:
	- The operation is done on a RemoteSDS
	- The operation is done in the context of a task

    Result a: Synchronous operation was done, return the result directly

For this I had to change all functions depending on the iworld timestamp
directly. Tasks using the share will still work.

Changed task output queue to allow server-side exception information to be sent properly to the client framework.

because the pings keep active clients alive

- Created an engine option for enabling/disabling autolayouting. This makes debugging easier.
- Added a layout for creating a toolbar and moving selected actions to it.

Centralized itasks engine options in an EngineOptions record that you can customize using startEngineWithOptions

Completely changed the way the store works. It is now fully built on top of the core SDS sources and combinators. Before the store existed as part of the engine although you could access it using some SDS's.
To make this possible I added a generic caching combinator for SDS's such that caching is no longer limited to files in the store, but can be applied to any shared source.

This change removes *a lot* of unnecessary I/O and makes iTask apps feel more responsive.

Moved everything from iTasks.API.Core.* except for some leftover types and derives in iTasks.API.Core.Types that should be distributed over other modules once everything has been moved.

It now includes checking the buildID of the application and the creation time of the task instance.

Added setting return codes when the itasks main loop stops. It is used when running the test as cli application

Added the possibility to run an iTasks event loop with a list of tasks that are immediately created and evaluated