| Author |
 Topic  |
|
|
ChanTerra
France
3 Posts |
 Posted - Oct 25 2011 : 02:05:00
|
Hi,
is ImageEn VCL (or some parts of it) usable with with Delphi XE2 Firemonkey ?
If not, is there a plan in this way ?
Thanks |
|
|
xequte
38940 Posts |
Posted - Oct 25 2011 : 02:56:07
|
Hi
At this time FireMoneky is not supported by ImageEn. We have not yet decided how and when we will support it.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
 |
|
|
ofiben
Spain
4 Posts |
Posted - Jan 12 2012 : 12:56:54
|
| Any news about firemonkey support on windows, mac & ios |
|
|
|
Patrick Quinn
United Kingdom
81 Posts |
|
|
ofiben
Spain
4 Posts |
Posted - Jan 13 2012 : 03:02:34
|
This last month I start transferring code from vcl to fmx from ImageEn, this was not really so complex except for dependencies from TBitmap encapsulation, windows messages process on visual components and some dependencies of the compiler version and platform.
I have been developing software for the photographic market from the last 10 years, and from the point of view of my experience 99% of the develop time it’s used to manipulate pictures, that’s it, no visual operations with very low dependencies from the OS (Data Exchange and Initialization, Image Arithmetic and Logical, Color Conversion, Threshold and Compare, Morphological, Filtering, Linear Transforms, Image Statistics, Geometric Transforms, Wavelet Transforms, Computer Vision, Image Compression, Video Coding, I/O).
Visual components like TImageEnView, TImageEnVect, TImageEnMView, etc. are used only for user interaction, and also this can be easy moved to firemonkey development.
Dialogs like OpenImage, SaveImage, Previews, etc. need more more to use firemonkey components, styles, and translations.
If TBitmap, TImage, TPicture and TCanvas support it’s removed from the library and this classes are limited to be used with a few functions on TIEBitmap to copy (from and to TBitmap) and render (from and to TBitmap and to TCanvas), this would help to migrate visual components and library functions, so TIEBitmap can be focused to improve performance and features on memory usage (fragmented, mapped memory, awe, etc.), more color spaces in planar format (PixelFormat) like YcBcR, more bit depth like 16 bit signed and unsigned, 32 bit signed and unsigned, 32 bit float, etc.), progress to migrate functions from ImageEnProc and hyieutils to TIEBitmap, make more consistent TIEBitmap removing everything that’s not really part of it like undo/redro info, probably DefaultDitherMethod, Contrast, BlackValue and WhiteValue, and any refereed to TBitmap support like fEncapsulatedFromTBitmap, fBitmap, fBitmapScanlines, and so.
I think also that functions should be re arranged by domain, there are duplicated types, data types for IO in Image processing units, custom version of functions included on Math unit that sould be on a ImageEn version of Math unit (ImageEn.Math)
I also have been working on this starting migrating functions and types from current units to domain functions units like (System.ImageEn.Types, System.ImageEn.Classes, System.ImageEn.Utils, fmx.ImageEn.View, etc.)
This it’s a very hard work for just me, my hope was that xecute would make some advances to migrate library o make a new version for use on firemonkey to next versions can be easy integrate on my code but for your answer it’s seems this’s it’s not going to be happen so I think this would be the last version of this library I would upgrade because starting at this version integrate upgrades to my version of the library would be impossible.
Regards
Alexander Brazda
|
|
|
| |
Topic |
|
|
|
Search
Firemonkey
