I'm currently investigating using image combining within my application, specifically the b64 encoded type.
I have setup a test config that contains a couple of images and have successfully built and run this. My application uses parts and I notice that the encoded images are written both to the .b64.json file that I specified in the image.json config file and into the part files. I find that encoded data for the same images are written into more than one part file which means that I am downloading the encoded image data multiple times. I've been trying to work out what causes a specific image to be written to multiple part files, but have not yet been able to understand the relationship between the encoded image data and the part files. Can anyone point me in the right direction here. Regards, Chris -- View this message in context: http://qooxdoo.678.n2.nabble.com/Image-combining-using-b64-encoding-tp7042588p7042588.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
