Download the PHP package skyline/settings without Composer

On this page you can find all versions of the php package skyline/settings. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package settings

Skyline Settings

This package extends your Skyline Application by a setting tool that provides a persistent settings storage.

Installation

`

Usage

Compiling with Skyline, this package adds a service.



### The Settings
The settings are designed as key value pair, where the key is the setting name and the value its value.  

The settings mechanism knows three locations, where a setting can be defined:
1. The default settings scope.  
    Once declared, the setting is valid in the whole application (like the example above)
1. The grouped settings scope.  
    The setting is part of a group (ex. VIEW.width or EDITOR.width)
1.  The user settings scope.  
    Any grouped or default setting can be associated with a user so then the setting VIEW.width for user A is different than VIEW.width for user B.

If the scope is not selected or the setting does not exist in it, the setting manager will try to find it in parent scope.  
Example: I'm looking for setting ``itemsPerPage`` in group ``DASHBOARD`` of ``USER_A``  
The setting manager will return the first existing setting:
-   Setting DASHBOARD.itemsPerPage for USER_A
-   Setting DASHBOARD.itemsPerPage
-   Setting itemsPerPage for USER_A
-   Setting itemsPerPage
-   NULL

Example: I'm looking for setting ``itemsPerPage`` of ``USER_A`` (without group)
-   Setting itemsPerPage for USER_A
-   Setting itemsPerPage
-   NULL

Please note that setting groups and user groups is not the same.

The manager also allows to declare settings:

In the same way you can remove settings:

All versions of settings with dependencies

PHP Build Version
Package Version
Requires php Version >=7.2
skyline/pdo Version ^0.9
skyline/kernel Version ^0.8
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package skyline/settings contains the following files

Loading the files please wait ....