Insights into what moves us. Contributions from the Structr team and guests. The Structr Blog

Axel Morgner
29. April 2016

Announcement: Structr 2.0.0

Back from this year's GraphConnect in London, the Structr team and I are happy to finally announce the availability of the long-awaited 2.0 GA release of Structr.

Download

You can download the binary distribution from https://structr.org/download and also the Debian package from Maven Central:

https://oss.sonatype.org/content/repositories/releases/org/structr/structr-ui/2.0.0/structr-ui-2.0.0-dist.zip
https://oss.sonatype.org/content/repositories/releases/org/structr/structr-ui/2.0.0/structr-ui-2.0.0.deb

Documentation

The documentation has been completely reworked and can be found here: https://support.structr.com/.

Changes

The most important changes and new features in 2.0 are:

General
  • Parallel Use of Neo4j Server
  • Database abstraction layer
  • Support for Java 8
  • Performance and stability improvements
  • Concurrent object instantiation
Improved Schema Support
  • Export schema defintion to JSON Schema files
  • Drag groups of schema nodes
  • Custom schema methods
  • Read/write code for Function property
Server-side JavaScript/StructrScript
  • Many built-in functions
  • Code completion
Security
  • Domain-based access rights resolution
  • Hide security-relevant attributes in any output
  • Automatic removal of unused resource access grants
CMS Features
  • Support for sites (virtual hosts)
  • CORS support
  • Improved HTML rendering performance
  • Support for XMPP, Data and Web feeds (Atom/RSS)
ECM Features (new)
  • Support for CMIS, SSH/SCP, FTP
  • Fulltext indexing and text extraction
  • Server-side audio/video conversion
Admin UI
  • Improved pagers
  • Rework of CRUD data editor
  • Improved graph-based visualiation
  • Reworked filesystem UI
  • Right-click context menu to insert page elements
  • Removed usage of localStorage

There are 2,280 commits with so many additions and improvements between 1.0.0 and 2.0.0. If you are curious, just use the git command git log --pretty=oneline 1.0.0..2.0.0 and see what happened in detail.