From f9d1c00e0b0004b1570f76fa785772bb26d8356a Mon Sep 17 00:00:00 2001 From: Robert von Burg Date: Sat, 9 Apr 2016 18:03:52 +0200 Subject: [PATCH] [New] Added new blog entry --- li.strolch.website/www.strolch.li/blog.html | 94 ++++++++++++++++++--- 1 file changed, 82 insertions(+), 12 deletions(-) diff --git a/li.strolch.website/www.strolch.li/blog.html b/li.strolch.website/www.strolch.li/blog.html index 72654b81e..390a59109 100644 --- a/li.strolch.website/www.strolch.li/blog.html +++ b/li.strolch.website/www.strolch.li/blog.html @@ -59,6 +59,76 @@
+ +
+

Strolch Update

+ +

April 9, 2016 by Robert

+ +

Long due update on Strolch development.

+
+

Although we have been rather quiet in the last couple of months, anyone viewing Strolch's commit log, + will see that we certainly didn't halt Strolch development.

+

We have been hard at work, using Strolch in projects, which required many new features and fixes. The + commit log shows as of today over 180 commits since the release tag 1.0.0.

+

Some of the most exciting changes are:

+
    +
  • REST API to query model, incl. privilege management.
    • +
  • JSON marshalling of all elements.
    • +
  • Added Policies
    • +
  • Added persisting of user sessions.
    • +
  • New JavaScript based UI to view Strolch's model. This is an initial version and more UI elements + and functions will follow. +
    • +
  • Basic planning engine functionality.
    • +
+ +

Further new features and changes are:

+
    +
  • Implemented a REST API to the privilege management - Now users can be added, changed, etc. via + call to the appropriate URL under ../strolch/privilege/*. +
    • +
  • Implemented a REST API to query the user sessions. Incl. invalidating sessions to forcefully + logout users. +
    • +
  • Implemented a REST API to query Audits.
    • +
  • Implemented REST API to query Orders, Resources and + Activities/Actions
    • +
  • Implemented REST API to update Resources and Orders from XML
    • +
  • REST API to authenticate now adds a cookie, so authorization is much simpler.
    • +
  • Added convenience methods in Service and Command to easily perform + system user actions. +
    • +
  • Added audits for login/logout of users.
    • +
  • Added audits for changes to privilege management.
    • +
  • PostgreSQL persistence layer now uses HikariCP + for connection pooling. +
    • +
  • Implemented a performance test project
    • +
  • Added new Parameters of type IntegerList, FloatList and + LongList. +
    • +
  • Added feature to ignore a realm on DB init.
    • +
  • Implemented core planning functionality.
    • +
  • Added strolch_minimal and strolch_minimal_rest projects to easily get + started. +
    • +
  • Query API now has built in ordering.
    • +
  • Added Policy to all root elements.
    • +
  • Added new planning web app project. This is a test application for demoing the planning engine + functionality of Strolch. +
    • +
  • Adding the persisting and reloading of user sessions, so that a new start of Strolch does not + logout users. +
    • +
  • Implemented to JSON visitors for all root elements.
    • +
+ +

So, although we've been rather quiet on the blog and on social media, we have not been quiet in + Strolch's development. We are planning to release version 1.1.0 soon, so stay tuned!

+ +
+

Activities: Beginning of the planning engine

@@ -72,23 +142,23 @@ Resource objects representing machines, human resources, etc., and Activity/Action hierarchies defining a workflow.

-

With the latest couple of commits to Strolch we have now added Activities and a basic - planning of Actions onto Resources. Activities have an +

With the latest couple of commits to Strolch we have now added Activities and a basic + planning of Actions onto Resources. Activities have an ordered list of IActivityElement which allows creating an arbitrary deep tree structure - of Activity and Action elements.

+ of Activity and Action elements.

-

Action objects have a list of IValueChange objects which define the start, - end and further value changes over time on a referenced Resource. Thus planning an - Activity is done by iterating the Activity hierarchy and for every Action - selecting a relevant Resource and then then applying the changes of the - Action on to the referenced TimeState on the Resource.

+

Action objects have a list of IValueChange objects which define the start, + end and further value changes over time on a referenced Resource. Thus planning an + Activity is done by iterating the Activity hierarchy and for every Action + selecting a relevant Resource and then then applying the changes of the + Action on to the referenced TimeState on the Resource.

This implementation is currently very simple as it ignores all constraints which a - Resource might have. In further development we shall implement a Violation - model so that UIs can be built to visualize the over-use of Resources.

+ Resource might have. In further development we shall implement a Violation + model so that UIs can be built to visualize the over-use of Resources.

In even further steps we would then start implementing algorithms to not just apply the changes onto - a Resource, but to actually search the Resource for time slots when the + a Resource, but to actually search the Resource for time slots when the value changes would not violate any constraints applied to the resource.

We are very much looking forward to these new features. Stay tuned for your updates - even though @@ -161,7 +231,7 @@

  • And many more...
    • -

    Strolch 1.1.0 is already in development and can also be downloaded from the download page Here you +

    Strolch 1.1.0 is already in development and can also be downloaded from the download page. Here you can see the current change list on GitHub. For instance heavy work has been done to implement privilege management by adding a REST API. Looking forward to