Collection of breaking change ideas for next major version

[olivervogel]

Collection of ideas that would be nice to have but would introduce a BC and would therefore only be possible in the next major version.

Please note that this is an initial collection of ideas that may or may not be adopted.

[olivervogel]

Standardization and simplification of offset parameters

To specify parameters for offsets, offset_x and offset_y are used in v3. The names could be catchier and simpler.

For example, just x or left instead of offset_x and y or top instead of offset_y.

[olivervogel]

More universal ColorInterface::create() method

Currently only string values of the colors are processed. It would also be nice if the values of the color channels could be specified directly.

use Intervention\Image\Colors\Rgb\Color;

// currently
$color = Color::create('rgb(255, 255, 255)');

// more universal
$color = Color::create('rgb(255, 255, 255)');
$color = Color::create(255, 255, 255);

[olivervogel]

Change from scale (int) 0 - 100 to (float) 0 - 1, for more precise input options.

Many functions use 0 - 100 integers as the standard for inputs. For a more precise definition of values, you could consider switching to float values from 0 - 1.

• 0 becomes 0
• 25 becomes 0.25
• 50 becomes 0.5
• 75 becomes 0.75
• 100 becomes 1

[olivervogel]

Switch to dedicated methods for reading

The universal method for reading images ImageManager::read() is convenient and has many advantages. However, it also has disadvantages compared to a group of specialised methods for each type of input. A change can be discussed.

// before
ImageManager::read();

// after
ImageManager::readFromFile();
ImageManager::readFromBinary();
ImageManager::readFromBase64();
ImageManager::readFromDataUri();
ImageManager::readFromStream();
ImageManager::readFromSplFileInfo();
ImageManager::readFromNative();