You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.

Layouts

This module of the Graph-Browser can be used to start the fruchterman-reingold, the forceAtlas2 or the dagre layout algorithm implemented in linkurious.js.

The dagre needs the dagre.js library wich can be found here

Functions

Name Parameters Descriptions
doLayout(layout, config) {string} layout the name of the layout [“fruchtermanReingold”, “forceAtlas2”, “dagre”]

{object} config Optional the configuration of the algorithm (see the linkurious.js documentation for more details)
Runs the given layout algorithm with the optional given configuration
startForceAtlas2(config) {object} config Optional the configuration of the algorithm (see the linkurious.js documentation for more details) Alternative way to start the forceAtlas2 algorithm
stopForceAtlas2() Stops the forceAtlas2 algorithm if it was started

Search results for "Layouts"

Layouts

This is simply a visual helper to bring order to the types on the canvas - it has no effect other than that.

Updating and Deleting Configurations is only allowed for saved layouts the current user owns or for those without an owner. Applying and downloading works for all saved layouts to enable sharing between users.

Layouts contain the current settings for relationship rendering, zoom, relationship labels, type placement and type visibility.

To help you focus on different aspects of you schema (i.e. different subgraphs of you application) Structr provides so-called schema layouts. The layouts can be managed, via the layouts tab in the Schema Tools. They can be applied via the Apply Layout button (Apply Layout) as shown below.

The layout tools allow the creating (Create Layout), updating (Update Layout), applying (Apply Layout), downloading (Download Layout) and deleting (Delete Layout) of schema layouts. This enables the user to create different layouts for different perspectives on the data model.

Deployment Format

folder / filedescription
componentsContains the shared components of the pages editor of Structr.
filesContains all files out of Sturctr’s virtual filesystem. Folders and files in the virtual filesystem are not being exported by default. If you want to include a folder or file into the export you have to set the flag includeInFrontendExport on each file or folder. Each file or folder will inherit this flag from its parent folder.
mail-templatesContains the mail-templates.
modulesContains the application configuration and definition of additional modules of Structr e.g. the flow engine.
pagesContains the created pages in the pages editor of Structr.
schemaContains the schema definition and code entered in the schema and code section of the Structr UI.
securityContains the resource access grants defined in the security section of the Structr UI.
templatesContains all template elements of the pages editor of Structr.
application-configuration-data.jsonContains the configured schema layouts of Structr’s schema editor.
components.jsonContains the settings e.g. visiblity flags, contentType or uuid for each file in the components folder of the export.
deploy.confContains information about the Structr system that created the export of the application.
files.jsonContains the settings e.g. visiblity flags, contentType or uuid for each file in the files folder of the export.
localizations.jsonContains the localizations that where created in the localizations section of the Structr UI and that can be used in server side scripting with the localize() function of Structr.
mail-templates.jsonContains the settings e.g. visiblity flags, locale or uuid for each file in the mail-templates folder of the export.
pages.jsonContains the settings e.g. visiblity flags, contentType or uuid for each file in the pages folder of the export.
pre-deploy.confScript that is run before deployment import. Use this to create users who are granted access to nodes in the export files.
post-deploy.confScript that is run after deployment import. Can be used to start any tasks which are necessary after import.
sites.jsonContains sites that are configured in the pages section of the Structr UI.
templates.jsonContains the settings e.g. visiblity flags, contentType or uuid for each file in the templates folder of the export.
widget.jsonContains the widgets that were created in the pages section of the Structr UI.

Visibility

Note: Depending on the previous layouts and the size of you browser window, the schema types may be rendered outside of the visible canvas. By scrolling horizontally or vertically you can see the nodes.

Admin