Download the PHP package simbiat/ddcicons without Composer

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

Informations about the package ddcicons

This is a collection of icons/logos for operating systems and various applications detected by Matomo's Device Detector except AFNetworking apps (need specific names). Expected use case: an audit page showing data on past user logins or current sessions.
General logic of selecting an icon is like this:

  1. Use the latest official one, if exists
  2. Use the highest possible resolution, but no more than 1200x1200 pixels (unless SVG).
  3. Regardless of resolution, the icon should be without obvious blur or artefacts, where possible. This includes blur, pixelation, deformities and the like caused by resizing of the image (original was 200x200px, and was resized to 1000x1000px).
  4. If latest official one is of poor quality or of low resolution, but an older icon exists with better quality - prefer that one.
  5. If it is unclear what is the latest official icon (for example 2 different icons are used by the brand in multiple places), the one that is used most often based on search results or the one that is more recognizable (often same thing) should be used.
  6. Icon should have transparent background, unless it's part of a brand or the background is used in official application icon on application stores.
  7. Icon should not have text on it, unless it's integrated into an image, brand does not have a logo that's not just text (stylized or not) or lack of text will result in no differentiation from other distinct icons.
  8. If there is no official icon at all, unofficial one can be used, as long as it is distinct enough and follows other principles as well.
  9. In case of open source project with no official and no unofficial icons, avatar of original creator can be used. In case there is none, or it's not distinct enough, icon for the main programming language can be used or just name of the project.
  10. Regardless of the icon selected, it should be modified, if needed to have square ratio, but at the same as little whitespace around the actual elements of the icon as needed to maintain the square ratio.

The above rules should be followed for new contributions as well. If they cannot be followed, this should be justified in PR description.

For consistency’s sake all icons were converted to lossless WebP (and minimized with TinyPNG) format except for device/type, client/type, bot/category, which are in SVG (all taken from svgrepo) to allow adjusting their colors through CSS to suit the website's style, if needed. Format is not enforced for contributions, due to included PHP class, but use of WebP and TinyPNG is still recommended, when possible.

In addition, names of the files some items were changes as follows due to special symbols:

If new contributions have special symbols as well, PHP class should be updated in same PR as well.

If desired, you can see all the icons from the collection on one page here.

Collection also comes with a custom class \Simbiat\DDCIcons that can help get respective icon with support of variable images formats (with prioritization) and a fallback icon.
Functions available:

Names of the functions should be self-explanatory, and all of them require at least the name of the respective entity. with getClient also requiring the type of the client. Some of the functions also support optional arguments that allow alternative fallback icons, if found.

Class has the following settings:

Note: while release versions are meant to match the current release of DeviceDetector (with added datestamps to identify local changes between them), they may lag behind a little bit or not change, if new DeviceDetector release did not have new entities.

Below bots are missing an icon, since it was not found or there are multiple entities that may be using respective bot without clear way to link them:

All versions of ddcicons with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
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 simbiat/ddcicons contains the following files

Loading the files please wait ...