Aperture -> Gallery ?

Anyone know if there is (or will be) a way to export images directly from Apple's Aperture application to a Gallery site? I know Aperture has it's own templates and whatnot but I already have put quite a bit of work into customizing my Gallery install and would rather not start over again with Aperture.

Aperture does have a plugins folder with several applescripts and a program.
Don't know what you can do with it though. If you want the scripts, I can give you a link.

There is no real development info or SDK AFAIK.

Aperture export api available in version 1.5:
http://www.apple.com/aperture/resources/exportapi.html

The Aperture SDK just got released.

I'd like to write a plugin to export images from Aperture into Gallery2.

Can somebody point me to some documentation / example source code perhaps that describes the protocol for uploading images Gallery2?

I found this - http://zwily.com/iphoto/ - but I think it was written with Gallery1 in mind.

I'm looking to build one from scratch that takes advantages of all the features of Gallery2.

thanks!

Any luck? A Aperture export would be great. It's the only thing holding me back from moving to Aperture.
And if someone had done it, THANK YOU!

I just wrote an ApertureToGallery plugin for Aperture (works with both gallery v1 and v2).

Email me offline at khans at ubermind dot com if you're interested in trying it out.

thanks.

thanks ckdake

I'm in the process of setting up www.apertureplugins.com and I'll have the plugin available there shortly. For now it's available at

http://www.uberkhans.com/~khans/ApertureToGallery-0.98.1.zip

Still toying with the idea of releasing it as open source, shareware, or full on commercial with support (really depends on how much time I have to devote to it).

I'd take the plunge and pick up a copy of aperture. Combination of Aperture <-> Gallery is a killer combination.

eye1marie: What Ebby wrote isn't true anymore, Aperture has and export API since 1.5 (as Makea wrote).

Hi,

Khans, wonderful plugin, thanks a ton, really saves me a lot of time exporting everything, uploading to my site, creating album, adding pictures, ...

I have a little request though. When you have to select the albums / subalbums to which you want to add your Photo's, it's nearly impossible to see what album you have selected. Expecially if you have album names like I do ( Langs Vlaamse Wegen 001, Langs Vlaamse Wegen 004 ) where the album number is added to the end of the name.

Otherwise, I love it

Regards,

Annunaki

-------------
Langs Vlaamse Wegen Video Podcast voor den Wandelfanaat.

Hi,

I actually tried the plugin again this weekend, but this time it only imported 2 pictures into my Gallery2 gallery. It didn't give any errors at all though, it just imported 2 of the 35 Pictures. I tried it again, and then it didn't import any pictures at all

Regards,

Annunaki

-------------
Langs Vlaamse Wegen Video Podcast voor den Wandelfanaat.

Hi,

I'm trying to connect to a Gallery 2 installation, embedded in XOOPS, and does not have any success.
Console outputs:
2006-11-23 20:59:58.450 Aperture[8147] - (void)observeValueForKeyPath: selection ofObject: <NSArrayController: 0x1112650>[object class: ATGGallery, number of selected objects: 0] change:context:
2006-11-23 20:59:58.451 Aperture[8147] - (void)observeValueForKeyPath: selection ofObject: <NSTreeController: 0x1bcccd00>[object class: ATGAlbum] change:context:

Edit: After opgrading the xg2 installation to 2.1, it now connects and I can see and create albums. The uploading does not seem to work, though...

Gallery 1.5.2, Aperture 1.5.1, ApertureToGallery 0.98.2 (UPDATE, upgraded to Gallery 1.5.5pl1 and still no love).

I keep getting the following error when adding the gallery:

2006-11-26 13:45:57.259 Aperture[640] - (void)observeValueForKeyPath: selection ofObject: <NSArrayController: 0x1e984130>[object class: ATGGallery, number of selected objects: 1] change:context:
2006-11-26 13:45:57.259 Aperture[640] - (void)observeValueForKeyPath: selection ofObject: <NSTreeController: 0x1e98dfb0>[object class: ATGAlbum] change:context:
2006-11-26 13:45:57.260 Aperture[640] - (void)observeValueForKeyPath: selection ofObject: <NSTreeController: 0x1e98dfb0>[object class: ATGAlbum] change:context:
2006-11-26 13:45:57.822 Aperture[640] - (NSDictionary *)_parseResponseDataNSData *)value - responseString <HTML>
<HEAD>
<TITLE>500 Internal Server Error</TITLE>
</HEAD><BODY>
<H1>Internal Server Error</H1>
The server encountered an internal error or
misconfiguration and was unable to complete
your request.<P>
Please contact the server administrator,
and inform them of the time the error occurred
and anything you might have done that may have
caused the error.<P>
More information about this error may be available
in the server error log.<P>
<HR>
<ADDRESS>
Apache Server at skivvies.com
</ADDRESS>
</BODY>
</HTML>

Any ideas? Man, I will PAY for this plugin... i can't wait to get it working. I've been wanting this for a long time!

I have been testing this a few days, but had a series of different problems. It works now, since I isolated the issues, so this is a summary of what i did, and a few suggestions/questions on how to improve the plug-in.

It worked for one or a few images in one selection, but not if I selected a lot of images. I also had to select a lower quality for the export, or else it would fail.

So I ended up on a guess that I somehow ran into the 2 MB limit for file uploads through PHP.

Then I tried again using a lower quality setting where I knew that my images each would be smaller than 2 MB, but again it failed if I selected too many images.

Now I changed the upload limit on the server to 127 MB, as described here: http://loudblog.de/forum/viewtopic.php?pid=188

So now it works. BTW I got permission errors in the console, so if others is having these it might be a limitation in the upload.

------
So now I have a few questions and sugegstions:

Does the plug-in upload all the exportet images in one "post" or does it make a "post" for each image? It seems to do the first thing, but I think the correct thing would be to do the latter, in order to avoid the upload limit as much as possible.

It would be nice if the plug-in could remember the last selected Export Name Format, instead of it always selecting the first in the list.

This is defenately a great plug-in!

Thanks,

Søren

skivvie:

If you're getting that error when entering in a new gallery, it might be related to the url you are using.

What url are you using for your gallery?

(make sure it doesn't have main.php in it - i.e. http://www.example.com/gallery or http://www.example.com/gallery2 instead of http://www.example.com/gallery2/main.php etc.).

Hello. First, thanks for this BRILLIANT plugin. Significantly streamlines my workflow. One small problem I'm having is that the g_title field of the item table in the DB is not getting populated. It doesn't in the iPhoto plugin either, if I recall, so if you're basing off that, that might be the root of the problem.

In the Windows world from where I recently migrated, the XP uploader thingie gave me the option of populating this field with either the full filename, or with the filename minus the extension. When I first used your plugin, I thought that fancy renaming stuff at the bottom was going to offer even MORE functionality, but after uploading some photos, I don't see where any of this information is actually entered into the DB.

It would be great if we could get that g_title field populated. My theme (a slider derivitive) uses that to display the title.

Thanks again for the great plugin!

Nothing wonky, just http://www.skivvies.com/photos

skivvie:

Thanks khans; I'm really looking forward to seeing how you develop this. Keep up the good work, and keep us all posted on your progress!

Brilliant, thanks! How do we get to the preference for the logging system? I've looked around but can see nothing obvious. Am I missing something?

It seems to be working a lot more solidly - I had a problem before where it appeared not to upload photos above a certain size (fairly small) but that seems to be working now (could have been my imagination though).

Have you had further thoughts about eventual distribution of this plugin? I would be happy to pay (something reasonable) for a fully-featured and fully-functioning version (not that the current version isn't fully-functioning in what it does). But of course I'd be even more happy if I didn't have to!

Should we be checking this thread or the apertureplugins.com site for future updates?

Richard

I'm very much in favor of this plugin, having a few galleries myself. I also own the superb FlickrExport for Aperture plugin by Fraser Speirs. I would pay a similar amount for this plugin if it did the following things and did them well:

• Allowed permission setting BEFORE uploading, so that permissions are already set once uploaded (for instance, I want everyone to see an album, but only people in the Friends group to view the full resolution, others see only the allowed downsampled resolutions, etc).
• Allowed the replacement of already existing images intelligently a la FlickrExport for Aperture
• Figured out if you were going to exceed your quota during the transfer and illustrated this graphically (quota versus usages versus upload total size) and warned you on upload if this would occur (with the option to cancel early, of course)
• Supported the transfer of existing tags as keywords
• Supported renaming each image individually during upload
• Was bulletproof with uploading and all possible error conditions on the gallery side, and allowed rollbacks or picked up where it left off once the condition was fixed.

To me, that's worth $20 plus a nominal fee for each significant upgrade. If you could get just the permission bit added I'd pay $10 plus a small fee for each additional feature, summing up to about $20. But that's me. Take a good look at Fraser's plugin and of course without ripping off his design, see if you can incorporate the positive functionality into your app, and there's money in your pocket.

Anyone know if the image's keywords are exported to gallery when the plug in is used?

Wow! I forgot about this thread. I just found the plugin on the main page and it is AWESOME!
This is so cool. Thanks guys.

Hi schmenzer,

Can you turn on logging and send me a trace please.

The process for enabling logging is described in the thread above and/or on the AperturePlugins.com blog.

Please email it to support at apertureplugins dot com and I'll take a look.

thanks!

cruax,

what happens if you try to manually hit the url that the plugin logged

http://myserver/gallery2/main.php?g2_controller=remote:GalleryRemote&g2_form[cmd]=login

from a web browser.

How about just

http://myserver/gallery2/main.php

I'm wondering if you have some sort of url re-writing enabled that is causing the plugin to trip up.

Yet another possibility is that you have your gallery protected with something like an .htaccess file. That would require security authentication to get to the page. If that's the case, then the plugin won't work because 0.98.3 doesn't have the ability to login to a gallery that's protected with that type of authentication - you'll most likely see that functionality in a future release.

thanks.

ps. re-installing the plugin won't fix it - it's either a bug in the plugin, a server side configuration error, or user error ;-).

cruax,

Can you temporarily move your .htaccess file aside and try to access the gallery from the plugin. That would help to isolate the problem.

thanks!

I'm getting a bad request 400 error when trying to attach to my gallery. I'll get the error when going here:

http://myserver/gallery2/main.php?g2_controller=remote:GalleryRemote&g2_form[cmd]=login

I can access /gallery2/main.php fine.

I think it may be related to the brackets. If I put parenthesis instead of the brackets it appears to give me something similar to this:

#__GR2PROTO__
server_version=2.8
status=202
status_text=Login parameters not found.
debug_user=******
debug_time=0s

I've read some web hosts do recognize brackets.