Picnik API feature requests

Want Picnik to be a part of your next-generation web 2.0 (3.0? 4.0?) application, but need some crucial piece of new functionality?  Got an idea for the Picnik API?  Just feel like brainstorming?  This is the place to do it!

A parameter for language selection is an good way to ensure the use of the correct language.
Especially for non-english projects and communities.

Great idea!  And, in fact, we are currently testing a feature just like this.  You can try it out as well: the parameter is called "_locale" and you should set the value to one of en_US, es_ES, de_DE, fr_FR, pt_BR, it_IT, zh_HK, or ko_KR.

This feature is still under development, so it might change a bit before it is "officially" released, but in the meantime give it a try and let us know what you think.

It would be interessting to have a way to use another image format like TIFF or PDF.
And both for import to picnik and export from picnik.

Very interessting in the print business, like poster printing.

A bigger image size than 2800x2800 can also be helpful.
Also sometimes needed in the printing sector.

Possibly only for premium users to keep your server clean from
zillons of fat images...

The 2800x2800 restriction is imposed by Flash, so it's very tricky to work around, but we've got a few ideas...

Thanks for the great suggestions; we've added them to our product planning list.  Keep 'em coming!

Hi Steve,
When do you think this feature will go live? I tried adding &_locale=fr_FR to the URL we're passing to Picnik and it doesn't work.

Wes

Great idea!  And, in fact, we are currently testing a feature just like this.  You can try it out as well: the parameter is called "_locale" and you should set the value to one of en_US, es_ES, de_DE, fr_FR, pt_BR, it_IT, zh_HK, or ko_KR.

This feature is still under development, so it might change a bit before it is "officially" released, but in the meantime give it a try and let us know what you think.

The feature is live now, but it doesn't work quite the way people expect.  We're making some changes to fix that and they'll be up next week.

Hi!

Do you think that sometime will exist the option to send _original_thumb pictures with sizes other than 240 x 240 and have them displayed correctly?

Our site already has 160x160 thumbs of every pic, but when resized to 240 x 240 it appears ugly (of course).

I know the solution right now is to generate 240 x 240 thumbs specially for picnik, but it will increase process on our server and also we will require more HD.

Thanks, and as this is our first message I wan't to thank to all the picnik team for the great job they are doing!!

Best regards
Pablo

Hi Pablo!  Thanks for supporting Picnik.

The feature you're asking is something that's been bugging me as well, and so it's already on my work list (under "create scaleable image thingy"). It's a low priority item at the moment, so I can't say for sure when it'll be available.  I'll put another vote beside it and hopefully we'll get to it soon. 

Steve

Hi Steve

I'm happy to know that at least it is on your work list

Until you get the time to have it done, I will manage to do the 240x240 when needed.

I have noticed the thumbnail gets loaded only when you click on the Export button.
Don't you think it can help to the user experience to load the thumbnail on the background after all picnik info has been loaded?
Maybe it can be downloaded as soon as all the app has been loaded and the user is starting to edit his image. So when he clicks on Export there is no delay (usually is not much delay since it a small image, but sometimes it took 1 or 2 seconds to appear).

Thanks for your support! We are still integrating Picnik on out service and is being really easy thanks the good documentation of the api. Its pretty clear and easy to use

Best regards

I would love a way to send some parameters to turn off or on cretin options/tabs in Picnik. This could be used to make a Picnik lite for more simple editing.

The features I would want:
Photo: Get from PC and Web cam
Edit: Crop, Resize
Create: Text, Shapes(basic)
Save: Save to PC and Email

Thanks for all you have done this looks amazing.

Hi Mike,

I'm not sure what it is you're asking for.  You can already turn off tab using the _exclude parameter.  Can you be more specific?

thanks for the quick answer Steve. I am looking for a way to have only the few tools I want shown. I have seen the _exclude which is great but I want only a few subtabs in each tab section to be shown.

Ah, I see.  That kind of fine-tuned control of the UI isn't currently on our roadmap, but I'll add your request to the list.

Hi steve,

Can we customize the UI such that just the user edited image should be resized to a fixed dimension wxh. And this has to happen just before exporting the user image to our targeted website, a way to resize.

This size needed for generating images for fixed size printing card. It will be help full for us if this resizing can be done at ur picnick editor itself, this saves lot of time and memory for resizing the image at our wesite.
 

Hi Prashant,

This is definitely something I'm interested in supporting, although I can't give you a firm date as to when it will be available. 

To help clarify what you're looking for:

- would you like us to resize the image to the given WxH without any input from the user? 

- How would you propose to handle cropping or scaling if the image's aspect ration doesn't match what you're requesting? Is maintaining a certain aspect ratio important?

- Do you want us to scale up to your target size if the user's image is too small, or only ensure that the image is no larger than a certain size in width or height?

Thanks for your input!
Steve

Hello,

I'm currently developing a Picnik integration for the Java webframework Wicket (wicket.apache.org).

It would be helpful to specify in what field "_imageid" is sent back during export, just like it is possible for the data with "_export_field".

Wicket is managing all form element names dynamically to prevent conflicts. I was able to find a workaround, but it is a bit hackish.


Greetings from Berlin,

.rue

Hi,

I have two proposals:

1. Possibility to translate the application into languages other than the ones you are supporting. As there is a way to translate the application  then I guess this could be done. For example - why not support an external XML file with translated texts that the application is able to load from 3rd party servers? I'm interested in translating the application to a not-so-common language.

2. I'm using the "Picnik in a box" solution and currently it takes a long time to close the application. Could there be a new parameter for the application to refresh the page after export/close? Currently I had to change the close.html to call window.location.reload();. Another solution would be for the application to open the _redirect in top window and not in the <iframe>.


Best regards,
Janek

At Photosleeve we preserve the original photo data from the camera, and that's what we send to Picnik for editing. We may have determined the correct photo orientation from EXIF (or the user may have manually rotated to the correct orientation in the case of a missing/incorrect camera orientation sensor), but that transformation isn't applied to the original, and so it doesn't show up in Picnik.

It would be sweet if there was a way for us to include a "rotation" operation as part of the /service query string that would automatically be performed when the photo was loaded, so that the orientation within Picnik would already match the orientation that the user had selected. Something along these lines:

   _rotation : Specifies a rotation operation which is automatically performed after import. Valid values are 90, 180, or 270, and refer to clockwise rotation in degrees.