I'd like to see a Lazarus package with only the base features (loading images, manipulating image data).
The visual features/LCL integration should go in another package that depends of the base package.
What is the advantage of this schema?
- Allowing other graphical toolkits like fpgui (http://opensoft.homeip.net/fpgui/) use imaging
- Allowing LCL components that uses only image loading features to be used in currently unsupported widgetsets like Qt and Carbon
I developed an LCL component that uses Imaging to load the images but don't use Imaging functions for the display. Since visual functions of Imaging does not compiles with Qt i created such "base" package and already uses it, but i'd like to see in the Imaging distribution.
Attached is the base and the visual packages. The only difference to users is that is needed to load the vampyreimaging_base package before installing vampyreimagingpackage.
The visual features/LCL integration should go in another package that depends of the base package.
What is the advantage of this schema?
- Allowing other graphical toolkits like fpgui (http://opensoft.homeip.net/fpgui/) use imaging
- Allowing LCL components that uses only image loading features to be used in currently unsupported widgetsets like Qt and Carbon
I developed an LCL component that uses Imaging to load the images but don't use Imaging functions for the display. Since visual functions of Imaging does not compiles with Qt i created such "base" package and already uses it, but i'd like to see in the Imaging distribution.
Attached is the base and the visual packages. The only difference to users is that is needed to load the vampyreimaging_base package before installing vampyreimagingpackage.