Your "issue" is mostly a rant. You will get better results posting "I can't figure out how to do X, I have Tried Y, but it return Z. Please help"
The Image API is meant to be light weight, and be used primarily for Thumbing-scaling images, which it does really well. It also does a great job with "I'm Feeling lucky" making images look usable no-matter the source. Basically the things a Search Engine Would do, or a Content Management system, not really an image manipulation system. It can do some of those things, but you may have do several recursive CPU intensive tasks, which may not make GAE Cost Effective for those kinds of tasks. All of that said: You can watermark using http://groups.google.com/group/google-appengine-java/browse_thread/thread/0a 813aba0e383ff9/59c59f82fadde2d7?lnk=raot From: [email protected] [mailto:[email protected]] On Behalf Of Brandon Donnelson Sent: Sunday, March 20, 2011 3:56 PM To: [email protected] Subject: [google-appengine] The Image Service API needs help badly! The image service api does not work as expected when using the methods in the api. Suggestions for improvement to the image service: 1. reading bytes and transforming them does not work as expected. 2. can't push bytes back into an image and transform them. One can only transform using the blobkey. Unless I'm missing something. 3. The api is thin, and needs more of the common image transformation methods that are available in GD2 or Java.awt.image classes. 4. It does not make sense to try to read purely in java when hardware systems are optimized to do the job natively (from my perspective). 5. image api limits are small, its meant for light duty thumb nailing. Any transformations over 4k, won't work. That eliminates most new camera photography sizes, at least using high res pics online or at least working with them to mold them into needed. 6. There is no watermarking composite option, to help protect images against theft. I know this is impossible, but worth doing for honest folks. 7. Burning CPU time is really easy with the amount of steps to overcome byte reading work arounds to tranform or tile an image. 8. The api itself is confusing, and thats partly due to the expected result not happening I think, mostly due to passing around the raw image bytes to transform. 9. There is no way to push the image to the blob store natively. 10. Images are a core feature to a web page, and building a beafer image service api, would mean resource conservation with shared libraries and less code, and cpu use. 11. Overall, its very very limited for light duty. I have found work arounds that burn up more cpu and resources and create a enormous amount of steps to do the job, which allows for more work, especially for a one mand band developer. 12. Since images are a core function, I would believe it would be a win win for all if you advance this api. Especially for adoption. 13. There needs to be more documentation on hitting deadlines, that is move the transformation activity to a task. And this is happening b/c I have to read the bytes to get the image sizes(params), in able to see what I need to do to transform it. So far, I rank this image service api, very limited for light duty. It can be used for bigger stuff, but with pain! http://code.google.com/appengine/forum/java-forum.html - Documenting the things I've been running across. http://code.google.com/p/googleappengine/issues/detail?id=2990 <http://code.google.com/p/googleappengine/issues/detail?id=2990&q=image%20se rvice&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20 Priority%20Owner%20Log> &q=image%20service&colspec=ID%20Type%20Component%20Status%20Stars%20Summary% 20Language%20Priority%20Owner%20Log - I've been commenting on the issues here. Please upgrade the image service api!!! Brandon Donnelson http://gwt-examples.googlecode.com http://c.gawkat.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
