Download the PHP package digitalstate/platform-widget-bundle without Composer
On this page you can find all versions of the php package digitalstate/platform-widget-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download digitalstate/platform-widget-bundle
More information about digitalstate/platform-widget-bundle
Files in digitalstate/platform-widget-bundle
Package platform-widget-bundle
Short Description DigitalState Widget Bundle
License MIT
Homepage https://github.com/DigitalState/Platform-Widget-Bundle.git
FAQ
Example:
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 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.
Informations about the package platform-widget-bundle
Platform-Widget-Bundle
The Widget bundle provides the developers a way to define widgets in the user interface.
Table of Contents
- Widget Entity
- Creating a Widget
- Context Filter
- Todo
Widget Entity
A widget consists of a title and content meant to be displayed in a template in a specific position. Essentially, it allows the developer to customise templates without directly modifying the template files. Widgets are comparable to ORO Placeholders with two additional features: the capability of adding a title and the context filter.
Note: Eventually, if possible, we will merge the concept of widgets to ORO Placeholders with our additional features.
Creating a Widget
Widgets can be created in any bundle. They are defined the same way as any other services in Symfony using the Service Container. The developer will need to tag the service with the ds.widget tag in order for the system to pick it up as a widget. Finally, the developer will need to define a position in a template file, where the widget should be displayed.
The widget class src/Gov/Bundle/BlogBundle/Widget/LatestPostsWidget.php:
The widget service src/Acme/Bundle/TestBundle/Resources/config/services.yml:
The template position:
Context Filter
The context filter is an optional parameter allowing the developer to define when a Widget should be rendered.
Let's use a real world example to explain the concept:
The DigitalState-Platform introduces the concept of Government Services through the DsServiceBundle. This bundle provides, at its core, the base actions for creating, editing, and deleting Generic Services. The editing action uses of the Widget concept for displaying the core form fields for the Generic Service.
The DigitalState-Platform also introduces the concept of BPM Services through the DsServiceBpmBundle. This bundle grafts itself on top of the DsServiceBundle to provide additional BPM-related functionality for when a business user wishes to create a BPM-based Service. A BPM Service is the same as a Generic Service, with additional fields to map the BPM process definition id and other BPM specific configurations. The DsServiceBpmBundle defines an additional Widget for the additional form fields and flags the context of the widget as bpm, meaning this Widget should only be displayed the specific context of BPM.
The template position with context defined:
Todo
Introduce custom twig tag for widget positions.
Example 1:
Example 2:
Enable widgets to be defined as template or callbacks, instead of classes.
