Libraries tagged by element search

PHP HTML Builder - A Lightweight Alternative to LaravelCollective/HTML and Spatie/Laravel-HTML With the release of Laravel 11, support for laravelcollective/html has been discontinued, leaving many developers searching for a modern, simple solution to generate HTML and form elements. PHP HTML Builder is here to fill that gap — offering a streamlined, intuitive alternative compatible with Laravel 9, 10, and 11. This package provides an easy-to-use, fluent API that replicates the functionality of laravelcollective/html and spatie/laravel-html, enabling developers to effortlessly create HTML components, forms, inputs, checkboxes, radio buttons, dropdowns, links, images, and more. Built with simplicity and flexibility in mind, PHP HTML Builder is a lightweight, PHP-first solution for building and managing dynamic user interfaces in Laravel applications.

Go to Download

The jQuery plugin that brings select elements into the 21st century with intuitive multiselection, searching, and much more.

Go to Download

One search to search them all

Go to Download

Retrieve additional context for Element searches

Go to Download

A small JS Function to make Html Select Elements searchable

Go to Download

Mapbender search element

Go to Download

Search element for Bear CMS

Go to Download

Vanilla JS classes for managing search fields, as well as searching DOM elements and JSON sources.

Go to Download

Vanilla JS classes for managing search fields, as well as searching DOM elements and JSON sources.

Go to Download

Global Search view (Search API index on BO elements + content types).

Go to Download

Basic site search for the SilverStripe Elemental module

Go to Download

ke_search Indexer for shortcut elements

Go to Download

A bundle to index Open Orchestra elements with Elastica Search

Go to Download

This project lazy loads the videos and images present in html to speed up the loading of web pages. It also parses an html containing search for images or YouTube videos. If you find them, modify those tags and replace them with quick-to-load elements.

Go to Download

The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.

Go to Download