Download the PHP package jdz/adminui without Composer

On this page you can find all versions of the php package jdz/adminui. 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?

Example code of jdz/adminui

Informations about the package adminui

jdz/adminUi

Framework-agnostic admin UI rendering primitives.

Value objects that serialize (via toData()) to the JSON consumed by the JS admin bundle — no HTTP, no database, no app lifecycle. Built on jdz/htmlrenderer.

Contents

Namespace Classes
JDZ\AdminUi\List Columns, Column, Triggers, Trigger, ItemActions, Row, RowInterface
JDZ\AdminUi\Toolbar Toolbar, ToolbarButton, AdminToolbar
JDZ\AdminUi\Item Item, ItemSection, ItemField, ItemTable — read-only detail views
JDZ\AdminUi\Form FormView (wraps a jdz/form form with fieldset panel states), FormActions
JDZ\AdminUi\ValueObject ModalChrome, Filterbar
JDZ\AdminUi\Controller MediasControllerTrait, PsrUploadedFileBridge — the shared /nimda media manager (opt-in, see below)
JDZ\AdminUi IconPrefix — which icon vocabulary the toolbars and triggers paint (see below)

Scope

This package is the rendering layer only. Data access (queries, repositories) and the app lifecycle stay in the consuming framework. A list query builder, for example, is not part of this package.

The one exception is JDZ\AdminUi\Controller\ — shared admin behaviour, for the screens where six back offices would otherwise grow six copies of the same file. It is opt-in: nothing else in the package touches HTTP, and the extra dependencies are suggested rather than required.

Icons

Toolbar buttons and row triggers take a bare icon name ('plus', 'edit') and render it as a CSS class. Which class is the admin's business, not the package's:

The default is glyphicons glyphicons-, which is what every consumer painted before this was configurable — so an admin that says nothing keeps exactly the markup it had. Set it once at bootstrap, before the first toolbar is built.

The media manager

MediasControllerTrait is the whole /nimda media manager: browse, create / rename / move / delete folders and files, upload, watermark, and the image picker a form field opens. The filesystem work is jdz/mediamanager; the browser is mediamanager.js from the admin bundle; this is the adapter between them, and it emits exactly the JSON that JS already expects.

A consuming controller supplies the per-site parts and nothing else:

Routes (the paths JiZy.makeUrl() builds — override mediaTaskUrl() to move them): json/mediamanager/{init,fs,upload}, json/mediamanager/folder/{create,rename,move,delete}, json/mediamanager/file/{infos,rename,move,delete,protect,unprotect}, json/medias/selector, plus medias and medias/download. The create, rename and move folder/file paths answer a GET with the dialog and a POST with the operation.

The picker

json/medias/selector renders the modal JiZy.Admin.mediaPicker opens — on a form's image field, and on the rich-text editor's image button. It always ships the folder list alongside the tree, so the picker can switch folders without going through the media manager screen, and json/mediamanager/folder/create accepts a posted parent for the same reason: the picker creates a folder where it is looking, not where the session last left the media screen. The created folder comes back in folder so the caller can reload straight into it.

?mode=editor adds the caption / alt / anchoring fieldset the editor needs to build its <figure>. Re-opening the picker on an existing figure passes src, alt, caption and align back in and they arrive prefilled — align is whitelisted against MEDIA_ALIGNMENTS rather than echoed, since it is query string on its way into a view.

PsrUploadedFileBridge turns a PSR-7 upload into the HttpFoundation one the uploader takes. It hands over the mime detected from the bytes, not the one the browser declared, and the trait additionally checks the stored extension against the configured whitelist — an upload endpoint inside the web root gets both.

Install

All versions of adminui with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2
jdz/htmlrenderer Version ^1.0
jdz/data Version ^2.0
jdz/form Version ^1.0
jdz/ui Version ^1.0
psr/http-message Version ^1.1 || ^2.0
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 jdz/adminui contains the following files

Loading the files please wait ...