I second that approach. I made a label maker that plugged into a python backend and then on to their printer workflow. I only sent string data of the text they entered, plus font choice, color, position, and what background imagery they chose. If you could 'free draw' your own illustration then I guess we would have sent that as an array, but maybe there is a better way to send it, I'm not sure. The python turned the data into an SVG format for printing. Hope that helps.
> Date: Thu, 5 Aug 2010 01:20:13 +0100 > Subject: Re: [Flashcoders] Create your own t-shirt > From: mike.dug...@gmail.com > To: flashcoders@chattyfig.figleaf.com > > > And you need to find out how to send a ByteArray back to a backend service > > to save said "t-shirt" as an image file. > > > > With that and Jack's TransformManager, those are the two main building > > blocks. > > > > > Having created quite a few online designers / product customisation tools, > I'd add that for print resolution imagery involving bitmaps you certainly > -don't- want to be transferring large amounts of pixel data back to the > server, compression or not (unless you don't mind long waits or low > resolution output affecting your customer abandonment rates). Better to keep > all high resolution processing (and files) on the server and to essentially > only transfer user interaction data back to the server to render out the > print ready, high resolution final format there, while keeping the whole > process snappy. > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
