I agree with you and was discussing this with a user the other day. Btw. did you try to add the facebook "like" button from the developer page you mention?
My guess is that you may need to A) Make sure you use WMODE=transparent for the flash so that the HTML layer with the "like" button displays above the SWF instead of being hidden behind. B) Make sure the iframe displays ina correct location. I am not quite sure why facebook need to use an iframe for this function, but ok ... If you want, I may be able to help you with this ...
Ferrà¡s wrote:Is there a possibility to integrate the button to every picture? Or are you planning on something related to that?
Yes, we certainly see the need of embedding buttons for sharing on social media, at least facebook and twitter. We will be adding some integrated "share" buttons in the next release of Imagevue. However, when it comes to the Facebook "LIKE" button, this is slightly different because you are not really referring a LINK to SHARE, but instead referring to a Facebook FAN page or GROUP page ... Not quite sure how this could be integrated, especially since they are using an IFRAME for the code, but I will look into it ...
Ferrà¡s wrote:There is another thing according to facebook: thankfully you can link to a specific picture although Imagevue is a flash gallery. But if you share a picture via Facebook, FB can not extract a preview-image from the Meta. That's a problem too.
Yes you are right, and we were considering this a few weeks ago. First of all, we need to add a default preview image to the gallery document, so that it at least finds a single default image for your gallery. This is simple, and can already be done manually (msg me if you need help with this). The technical challenge, is to get Facebook to load a preview-image from the specific link. Unfortunately, because we use #SWFaddress javascript to refer links to flash, this does not work with facebook which strictly looks into the document source code(HTML) for any preview images. We hope to figure out some workaround for this for next release!
Thanks for reporting!