Oops correction,
Two images on the server.
The original image ( for actual printing) and the created image (for
proofing).
And maybe a postscript file for the text. Make it easy to transfer
right into production at the shop.
Karl
On Aug 5, 2010, at 4:20 AM, Karl DeSaulniers wrote:
Thanks Dave,
That is an interesting approach, but I am all thumbs when it comes
to python.
I was going to use php and have the user upload their image,
I would store the image on the server, reference/load a thumb of
that image,
then let them place it add text etc, then take the text they add
and the image they uploaded
and merge them with php image manipulations. I can also let them
use transparent PNGs and give it a more realistic feel.
Then I can make a final output file that is full size. All i am
having to size up is added text and if the user wants to print it
out they can.
Plus, we will have a proportionate sample to go by and only one
image on the server.
That way my flash program or javascript, whichever I finally go
with, just receives the thumbnail data
and it wont be bogged down and it should be easy to manipulate in
either case.
But this is still in theory mode. :)
Karl
On Aug 5, 2010, at 4:01 AM, David Hunter wrote:
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: [email protected]
To: [email protected]
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
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Karl DeSaulniers
Design Drumm
http://designdrumm.com
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Karl DeSaulniers
Design Drumm
http://designdrumm.com
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
