WideImageCurrent Version: 11.02.19 Community Rating: WideImage is an object-oriented library for image manipulation. |
Hosting Service Optimized for WideImage
WideImage is an object-oriented library for image manipulation.
The library provides a simple way to loading, manipulating and saving images in the most common image formats.
Cloud VDS WideImage Solution
Get WideImage Hosting Now $ 49.95 /mo- WideImage Installation
- 20GB Disk Space
- Unlimited Monthly Transfer
- Root SSH Access
- Managed Firewall
Dedicated
WideImage Solution
Get WideImage Hosting Now
$ 129 /mo
- WideImage Installation
- 32GB RAM
- cPanel Included
- 480GB SSD + 1TB HDD
- Choice of Datacenter
Just a few features WideImage offers:
Supported formats
WideImage supports all formats that are natively supported by the GD extension on the server
(this currently includes GIF, PNG, JPG, GD, GD2, WBMP, XBM, XPM). It also supports BMP (read/write) and TGA (read only).
Loading images
Loading an image is easy — you only have to call the WideImage::load() static method and specify the image source.
WideImage tries to detect whether the source is a file, url, upload, a binary string or a valid GD image resource (image handle). WideImage supports the most common image formats.
Saving images
WideImage supports saving images to files, outputting the image directly to the browser, and retrieving them as a string. With string output, you can easily capture image data and write it for example to a database.
Manipulating images
In WideImage, you manipulate the images by calling the appropriate operation method on the image object. Every operation returns a new Image object (for the nerds: this is basically a value object).
Smart coordinates
Smart coordinates were implemented to make operations that involve coordinates, dimensions, and positioning easier. They can be useful with any operation that requires coordinates as parameters, like resize, crop, etc.
Resource handling
WideImage takes care of image resources for you; you don't have to destroy the images explicitly, they're automatically destroyed when an image object is no longer used. You can change that at runtime by releasing the handle of an image via releaseHandle() method.